Applications Systems
AppInsight for Exchange: PowerShell Exchange web site testing failed with the following error:Connecting to remote server failed with the following error message : Access Denied
When configuring AppInsight for Exchange in SAM, the following error message displays: Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error: Connecting to remote server failed with the following error message: [ClientAccessServer=(IP_ADDRESS),BackEndServer=,RequestId=,TimeStamp=] Access Denied" For more information, see the about_Remote_Troubleshooting Help topic.
First published date
Last published date
Overview
When configuring AppInsight for Exchange in SAM, the following error message displays.
Remote configuration was unsuccessful due to the following: "WinRM test was successful. PowerShell Exchange web site testing failed with the following error: Connecting to remote server failed with the following error message: [ClientAccessServer=(),BackEndServer=,RequestId=,TimeStamp=] Access Denied" For more information, see the about_Remote_Troubleshooting Help topic.
The error persists even after verifying the requirements and permissions for AppInsight for Exchange.
Product section
Cause
Resolution
Check the certificates in use under Default Website of the Exchange Server
- Open IIS Manager in the Exchange server
- Navigate to Exchange Server > Sites > Default Web Site
- Right-click > 'Edit Bindings...'
- Highlight and 'Edit..' the HTTPS listener
- 'View...' the certificate
In here, ensure the certificate is valid and check who the certificate is issued to. If it's a signed against FQDN, such as Mail.ComanyName.com then this will require the use of this URL in the AppInsight for Exchange configuration
The following steps should be used in the following situations:
- A Wildcard Certificate is configured on Exchange and there's no DNS entry for the PowerShell Endpoint
- Exchange Websites sit behind a Load Balancer
In the event of the above situations, another HTTPS binding on some random port can be assigned to the Exchange server with a Self-Signed Certificate or the Microsoft Exchange Certificate.
With the above binding created, the configuration in AppInsight for Exchange would look like the following.
Resolution 2:
1, Do an IISRESET from the CLI admin to restart the Application Pools withing IIS
2. Use the CONFIGURE SERVER tab.