I have an Exchange 2010 DAG (2 Local Nodes and 1 at a remote site) The remote server is a passive node for all five DB's Exchange is AFAIK all functioning perfectly, we see no issues. We use SCOM 2007SP2 with the Exchange 2010 Management Pack to monitor this infrastructure. Currently every 10(ish) minutes I get an alert from SCOM which says the following: Alert: Monitoring failed to run the Test-MRSHealth cmdlet. Source: Mailbox Replication Service - BDC-WDS-EXC1 (Client Access) - BDC Path: BDC-WDS-EXC1.ad.localnet;BDC-WDS-EXC1 (Client Access) - BDC Last modified by: System Last modified time: 16/07/2010 13:55:11 Alert description: Provisioning layer initialization failed: 'Could not find any available Domain Controller.' Diagnostic command: "Test-MRSHealth -MonitoringContext:$true" EventSourceName: MSExchange Monitoring MRSHealth Knowledge: http://go.microsoft.com/fwlink/?LinkID=67336&id=80d898e6-58fe-45e1-9c04-0ba31357b532 Computer: BDC-WDS-EXC1.ad.localnet Impacted Entities (0): If I run the test-mrs-health command on the remote server I do not see any errors. The remote Exchange server was originally built within the local AD Site but then later it was moved to a different site (and consequently renumbered) however the remote site also has a DC and can access it. Any help in getting rid of this annoying error message is very much appreciated. Brett

Is BDC-WDS-EXC1 the node in the remote site? CAS role is also installed on this node, right? Please check if there’s any error event in the application log Please run ExBPA against the server for health checkJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Yes BDC-WDS-EXC1 is the node at the remote site: Strangely following a reboot yesterday (for a different reason) the alarms have stopped in SCOM However I am still seeing the following in the application event logs constantly: Log Name: Application Source: MSExchange Configuration Cmdlet - Management Console Date: 7/19/2010 1:51:17 PM Event ID: 4 Task Category: General Level: Error Keywords: Classic User: N/A Computer: bdc-wds-exc1.okna.nominet.org.uk Description: (PID 11712, Thread 123) Task Test-OutlookConnectivity writing error when processing record of index 0. Error: Microsoft.Exchange.Monitoring.MailboxNotFoundException: Failed to find the mailbox. Mailbox = 'extest_7f634e23db264@okna.nominet.org.uk'. at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.GetTestMailbox() at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.get_Identity() at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.InternalValidate() Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange Configuration Cmdlet - Management Console" /> <EventID Qualifiers="49152">4</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-07-19T12:51:17.000000000Z" /> <EventRecordID>323932</EventRecordID> <Channel>Application</Channel> <Computer>bdc-wds-exc1.okna.nominet.org.uk</Computer> <Security /> </System> <EventData> <Data>11712</Data> <Data>123</Data> <Data>Test-OutlookConnectivity</Data> <Data>0</Data> <Data>Microsoft.Exchange.Monitoring.MailboxNotFoundException: Failed to find the mailbox. Mailbox = 'extest_7f634e23db264@okna.nominet.org.uk'. at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.GetTestMailbox() at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.get_Identity() at Microsoft.Exchange.Monitoring.TestOutlookConnectivityTask.InternalValidate()</Data> <Data>{e12b3705-ec7f-4c3d-8ad2-903f59f9fd66}</Data> </EventData> </Event> And before the reboot I was seeing this: Log Name: Application Source: MSExchange Configuration Cmdlet - Management Console Date: 7/18/2010 1:35:05 AM Event ID: 5 Task Category: General Level: Error Keywords: Classic User: N/A Computer: bdc-wds-exc1.okna.nominet.org.uk Description: (PID 9276, Thread 151) Task Test-OutlookWebServices throwing terminating exception at stage Microsoft.Exchange.Provisioning.ProvisioningBrokerException: Provisioning layer initialization failed: 'Could not find any available Domain Controller.' ---> Microsoft.Exchange.Data.Directory.ADTransientException: Could not find any available Domain Controller. at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential) at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType) at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope) at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId, ADRawEntry scopeDeteriminingObject) at Microsoft.Exchange.Data.Directory.ADGenericReader.GetNextResultCollection(Type controlType, DirectoryControl& responseControl) at Microsoft.Exchange.Data.Directory.ADPagedReader`1.GetNextResultCollection() at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.GetNextPage() at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.<GetEnumerator>d__4.MoveNext() at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindCmdletExtensionAgents(Boolean enabledOnly, Boolean sortByPriority) at Microsoft.Exchange.Provisioning.ProvisioningBroker..ctor() --- End of inner exception stack trace --- at Microsoft.Exchange.Provisioning.ProvisioningBroker..ctor() at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(SessionState sessionState) at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task) at Microsoft.Exchange.Configuration.Tasks.Task.BeginProcessing(). Exception: {764e6f7c-6b7e-4460-824c-d82967141062} Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MSExchange Configuration Cmdlet - Management Console" /> <EventID Qualifiers="49152">5</EventID> <Level>2</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-07-18T00:35:05.000000000Z" /> <EventRecordID>317607</EventRecordID> <Channel>Application</Channel> <Computer>bdc-wds-exc1.okna.nominet.org.uk</Computer> <Security /> </System> <EventData> <Data>9276</Data> <Data>151</Data> <Data>Test-OutlookWebServices</Data> <Data>Microsoft.Exchange.Provisioning.ProvisioningBrokerException: Provisioning layer initialization failed: 'Could not find any available Domain Controller.' ---&gt; Microsoft.Exchange.Data.Directory.ADTransientException: Could not find any available Domain Controller. at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential) at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType) at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, String optionalBaseDN, ADObjectId&amp; rootId, ADScope scope) at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId&amp; rootId, ADRawEntry scopeDeteriminingObject) at Microsoft.Exchange.Data.Directory.ADGenericReader.GetNextResultCollection(Type controlType, DirectoryControl&amp; responseControl) at Microsoft.Exchange.Data.Directory.ADPagedReader`1.GetNextResultCollection() at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.GetNextPage() at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.&lt;GetEnumerator&gt;d__4.MoveNext() at Microsoft.Exchange.Data.Directory.SystemConfiguration.ADSystemConfigurationSession.FindCmdletExtensionAgents(Boolean enabledOnly, Boolean sortByPriority) at Microsoft.Exchange.Provisioning.ProvisioningBroker..ctor() --- End of inner exception stack trace --- at Microsoft.Exchange.Provisioning.ProvisioningBroker..ctor() at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(SessionState sessionState) at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task) at Microsoft.Exchange.Configuration.Tasks.Task.BeginProcessing()</Data> <Data>{764e6f7c-6b7e-4460-824c-d82967141062}</Data> </EventData> </Event>

extest_xxxxx@xx.xxx is the test mailbox that you created for testing outlook connectivity, and other same testing cmdlet. Can you find the mailbox via “Get-Mailbox”? If you can’t find the mailbox, please create a new one Install and Configure Exchange Server 2007 Monitoring and Data CollectionJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Hello, yes the mailbox extest_f6d112c18f534 is present, the other 2 servers (at the local site) are not suffering from this problem so I guess they are able to see this mailbox without any issues. Brett

It seems that bdc-wds-exc1 can’t find the test mailbox, you can find test mailbox via EMS on the bdc-wds-exc1, right? Please run “DCDiag /v /a” and “NetDiag /v” to check the connection to DC from the exchange serverJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

I have just noticed within SCOM that there are multiple tests failing with "The test credentials can't be used" do these credentials need configuring somewhere on a per server basis? I ran DCDIAG on the Exchange Server and it passed all tests. Brett