When trying to run the Exchange powershell command Set-WebServicesVirtualDirectory the following error is returned:
Unable to access the configuration system on the remote server
The fix is to re-register the application pool using the aspnet_regiis command (http://msdn.microsoft.com/en-us/library/k6h9cz8h(v=vs.140).aspx)
Identify if the application pool uses 32 bit or 64 bit by opening Task Manager, the w3wp.exe will show *32 next to the image name if the w3wp is running in 32-bit mode, if no *32 is shown next to the image name, then the worker process is running in 64-bit mode.
- From the command prompt,
- If its V2.0 32 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework\v2.0.50727
- If its V2.0 64 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework64\v2.0.50727
- If its V4.0 32 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework64\v4.0.30319
- If its V4.0 64 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework64\v4.0.30319
- Then run the command aspnet_regiis -config+
So why was it necessary to run this command at all? The Exchange Server was upgraded from 2008 R2 to 2012 R2. For several months Exchange ran fine post upgrade without any issue. The issue was only noticed when I tried to run the set-webservicesvirtualdirectory command.