Muhammad Asif
asked on
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.loc
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_Troubleshooti
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?
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.loc
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_Troubleshooti
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?
ASKER
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?
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?
did you review the event logs, you should find the reason for why the services are not starting..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i have found a solution.
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.