Exchange 2013 servercomponent status Exception Handling

Exchange 2013 servercomponent status Exception Handling

Today, the customer said that the internal printer could not send an email. The printer email was set to point to the CAS Server Load balancer address (two cas nlb servers). The test directed to the physical address, and the result would be one, if one server does not work, check for the other server and find that the SMTP 25 listener is normal, but the connection reports an error.

650) This. width = 650; "Title =" clip_image002 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image002 "src =" http://img1.51cto.com/attachment/201410/29/9437529_1414562480n6cT.jpg "" 557 "Height =" 58 "/>

So I checked the application log and found an evend ID 7012 suspicious:

650) This. width = 650; "Title =" clip_image003 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image003 "src =" http://img1.51cto.com/attachment/201410/29/9437529_1414562480sJ36.png "" 541 "Height =" 81 "/>

The original exchange 2013 has a new change, and Service Startup does not mean it is completely OK. They still have a status that must be active. You can use get-servercomponentstate-identity <serverid> to view it: normally, for example, my viewing is all inactive, so there is a problem.

650) This. width = 650; "Title =" clip_image005 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image005 "src =" http://img1.51cto.com/attachment/201410/29/9437529_14145624800CeN.jpg "" 558 "Height =" 291 "/>

The following two components must at least be active so that the MA component can be monitored and restored. These two components are also inactive, and the system cannot perform the recovery operation.

650) This. width = 650; "Title =" clip_image006 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image006 "src =" http://img1.51cto.com/attachment/201410/29/9437529_1414562484ZMFZ.png "" 209 "Height =" 33 "/>

There are two solutions: restart the server and check the status. If the server cannot be restarted, run the following command to manually change the status:

Set-servercomponentstate ptmailcas01-component serverwideoffline-state Active-requester functional

Set-servercomponentstate ptmailcas01-component monitoring-state Active-requester functional

Set-servercomponentstate ptmailcas01-component recoveryactionsenabled-state Active-requester functional

The serverwideoffline above covers all components (except monitoring/recoveryactionsenabled)

After I run the command, I find that some components are still not active, even if I execute the command separately. This only happens when the server is restarted after work, but the basic functions are normal.

650) This. width = 650; "Title =" clip_image008 "style =" border-top: 0px; border-Right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image008 "src =" http://img1.51cto.com/attachment/201410/29/9437529_141456248455Sz.jpg "" 558 "Height =" 287 "/>

To prevent this problem, we recommend that you run the following command after restarting the server:

Get-servercomponentstate-identity <serverid>

Exchange 2013 servercomponent status Exception Handling