During the installation process, all appeared good. However, the Exchange Management Console and Exchange Management Shell were unable to connect locally on the new server. They tried to connect locally, timed out, and then connected to another Exchange 2010 server.
The following errors were in the event logs:
Event ID 5139
A listener channel for protocol 'http' in worker process '1028' serving application pool 'MSExchangePowerShellAppPool' reported a listener channel failure. The data field contains the error number.
Event ID 2280The source of this error turned out to be a line in the Windows\System32\inetsrv\config\applicationHost.config file. This line contains the path D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll when in fact is should have been C:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll. After further investigation, it appeared that the original install of Exchange was done to the D: drive rather than the C: drive and that the change on the second install cause the error.
The Module DLL D:\Microsoft\Exchange Server\V14\Bin\kerbauth.dll failed to load. The data is the error.
The line that needed to be modified was:
<add name="kerbauth" image="D:\Exchange Server\V14\Bin\kerbauth.dll" />
After the change to the C: path, all was good.
Thank you for sharing this information. I recently joined an organization that places all of their exchange binaries on an unique volume. After I added two new mailbox role servers, I had exactly this issue, but instead had to modify to point to the binaries drive. I bounced all of the services and the shell and EMC came alive.
ReplyDeleteThanks this saved me a ton of time! There were a number of bad paths in my config file noted above.
ReplyDeleteThank you, thank you, thank you! This was a HUGE help. I was about to blow away my VM and start over when I happened upon this post.
ReplyDeleteYou Bloody Legend :) love you so much right now haha. this one was doing my head in.
ReplyDelete