Blog Diyar Aqrawi

After migrating from Exchange 2003 to Exchange 2010 you may get this alert in SCOM “Transaction failures occurred during MAPI connectivity testing”

Transaction failures occurred during MAPI connectivity testing.
Some of the MAPI connectivity transactions failed. Detailed information:
Target: System mailbox for SERVER\Public Folder Database
Error: [Microsoft.Exchange.Data.Storage.ObjectNotFoundException]: The Active Directory user wasn’t found.

This alert comes from the Exchange 2010 Management Pack. The test is being done through this  powershell cmdlet “Test-MAPIConnectivity”. To further investigate this problem we log into the Exchange 2010 server and run the same command in Exchange 2010 powershell command line manually, and yes we get the same error:

to solve this issue open ADSI Edit and remove the whole old Exchange 2003 container called “Servers”. after doing this return to the Exchange 2010  server and rerun the cmdlet, you will see that it runs with no errors.

The new SCOM SharePoint 2010 Management Pack is not so easy to configure and use, you may have noticed that you had to follow some steps before you can add your SharePoint 2010 servers in SCOM.

but this is not all, The SharePoint 2010 MP have some monitors that discovers all your SharePoint 2010 sites and run some web application monitors against them. After a while you may have noticed that most of these Web Application Monitors raise alerts and they may fail:

In the alert details you see that there is a knowledge Article that may be a good start for examining the problem, http://go.microsoft.com/fwlink/?LinkID=147311. The Microsoft Article suggests that you check two things;

1- Verify that the Web application exists and is running (in my case it exists and it is running well)

2- Confirm that the Run as administrator account has sufficient permissions. (the Run-As account has sufficient permissions)

so you may begin to wonder, what is here wrong? even when browsing the site, there are no problem the IT site is available. let us examine this problem and give it more depth. Open the Health Explorer and look for some details. In the Context we see that the monitor fails and it give us some Error Code “2147954407”

After doing some Google search I found that this error code means ” 2147954407 ERROR_WINHTTP_NAME_NOT_RESOLVED”

hmmm this is interesting, it look likes that the name of the web site is not been resolved through the monitor. So I opened the properties of the website and found there is an overridable parameter that is called Url. So I made an override and put the name of my site on it itweb.contoso.com .

After applying this override, the web application monitor went good and I didn't get that alert anymore