Share via

Determine the requestor that changed Server component state

  • Applies to: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019

Original KB number:   2958835

Symptoms

In Microsoft Exchange Server 2013 or later versions, you're trying to change state of server component to Active by using the Set-ServerComponentState command. The command completes without any error, however, component remains Inactive.

It mostly happens because the Requestor name provided in Set-ServerComponentState isn't matching the Requestor that changed the state originally.

Resolution

In such scenario, use the following command to find the Requestor that has changed component state:

(Get-ServerComponentState -Identity <ServerName> -Component <Component>).LocalStates

For example, in the following example, Monitoring and RecoveryActionsEnabled components are inactive.

Screenshot of Monitoring and RecoveryActionsEnabled components.

Use the following command to find Requestor that change state of the Monitoring component to Inactive:

(Get-ServerComponentState -Identity Exch1 -Component Monitoring).LocalStates

Screenshot of finding Requestor that changed state.

Now that you know the Requestor, use the following command to change the state of the Monitoring component to Active:

Set-ServerComponentState -Identity Exch1 -Component Monitoring -State Active -Requester Functional

Verify the component is active by using the following command:

Get-ServerComponentState -Identity exch1 -Component Monitoring).LocalStates

Screenshot of showing that the component is active.

References

For in depth understanding of Server component states in Exchange Server 2013, see Server Component States in Exchange 2013.