Both the Exchange Management Console (EMC) and Exchange Management Shell (EMS) are making a connection to Powershell using a remote session. During the session a connection will me made to the virtual directory Powershell which can be found in the IIS Management Console. This virtual directory can only be accessed by using port 80 by default.
To authenticate users Kerberos is used. During the Exchange setup a seperate dll has been installed.
In case of a remove and re-install of Exchange on another volume this may lead to problems. Of course this is a scenarion which you won’t see a lot.
After Exchange is completely re-installed on the new location you won’t be able to start the EMC anymore. In the event log you will see a lot of errors just like the one above.
Because IIS is used some configuration settings are stored in. These files can be found on the following location c:\windows\system32\inetsrv\config_ for example the _applicationhost.config.
In the section globalmodules several modules such as the authentication methods, redirection and the other modules are listed here. This is done by refering to the dll which is required.
Because the kerbauth.dll is a native module this dll is also listed and the location specified is the Exchange installation directory. In some cases this rule is not deleted or updated and keeps pointing to the old location. The result: the DLL can’t be found.
The problem can be solved very easily by correcting the path and ensure that it points to the correct location. This can be done by using the variable ExchangeInstallPath (Exchange 2007 only).
For more troubleshooting tips you can visit the page below. Here you will find several issues and the solution for these issues.
Technet: Powershell Virtual Directory issue causes problems with EMS open