Exchange Services (Frontend Transport, Transport and Information Store) are not starting after reboot of server

We have configured the NIC Teaming ( LACP/Dynamic Mode) on Exchange server and everything was working fine. However as we restart the server, the Exchange services  (Frontend Transport, Transport and Information Store) are not getting start.  

Frontend transport is in starting and stoping mode. It is seems that it is trying to start itself continuously. The Microsot Exchange transport service is showing status as stoping and it seems that it is not able to stop it self.

Moreover, the ECP and Powershell is also not connecting. We are getting following error while opening PowerShell.

New-PSSession : [main-ex02.domain-name.local] Connecting to remote server main-ex02.domain-name.local failed with the following
error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response
from the destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ..
Is it due to NIC Teaming or is there any other issue?  

Can any one help us?
LVL 2
Muhammad AsifSenior Solutions ArchitectAsked:
Who is Participating?
 
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Hi Sunil,

We have managed to resolve this case. The issue was comming to due to an invalid registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

The internet registry making all the issues under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc.  We have deleted the internet registy from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc, rebooted the server and everything is working again.  
This was debugged by Microsoft Team for another person and fortunitly he has posted the solution. For reference please refer to this link: https://social.technet.microsoft.com/Forums/en-US/ad245133-e538-4da7-9dcd-5cb329dbbf40/sbs-2011-transport-error?forum=exchangesvrsecuremessaginglegacy
0
 
Sunil ChauhanExpertise in Exchange Server, Office 365 & Powershell ScriptingCommented:
make sure your DNS settings are correct on the NIC, and you can reach the DC from the Exchange Server.

furthermore, go through the event logs for more visibility on the issue.

to make sure it's not due to teaming I would suggest trying disabling the same to see if all the services come back up after that.
0
 
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Hi Sunil,

The Exchange server and DC are properly communicating with eachother. We have also undo the NIC teaming but issue still persist.

Can you please provide us any other suggestion?
0
 
Sunil ChauhanExpertise in Exchange Server, Office 365 & Powershell ScriptingCommented:
did you review the event logs, you should find the reason for why the services are not starting..
0
 
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
i have found a solution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.