I have 1 primary site and 1 secondary site. I am recieving the same error on both ever since setup and I believe it is my problem why I can not deploy attacthed is the sms MPTRoubleshooter results The test was Testing MPCERT HTTP request functionality, Failed, Object Refernce not set to an instance of an object. Can anyone help? <?xml version="1.0" encoding="utf-8" standalone="yes" ?> - <!-- Post Installation Test Results --> - <Tests> - <Test> - <Name xmlns="Verify that the Distributed Transaction Coordinator Service is running."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Verify that the Task Scheduler is running."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Verify that the Windows Management Instrumentation service is running."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Verify that the World Wide Web Publishing Service is running."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Verify that the SMS Agent Host Service is running."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Verify the Default Website is running."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Verify the MPs Machine$ account is a Member of the SQL servers SMS_SiteSystemToSQLConnection_<site_code> group"> - <Result xmlns="Skipped"> <Comment xmlns="Not Applicable MP is local to the SQL Server" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Testing MPLIST HTTP request functionality"> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Testing MPCERT HTTP request functionality"> - <Result xmlns="Failed"> <Comment xmlns="Object reference not set to an instance of an object." /> </Result> </Name> </Test> - <Test> - <Name xmlns="If the MP is W2k3: Verify that the BITS Web Extensions are enabled."> - <Result xmlns="Passed"> <Comment xmlns="" /> </Result> </Name> </Test> - <Test> - <Name xmlns="Does the SMS Service account have administrative rights on the MP"> - <Result xmlns="Skipped"> <Comment xmlns="Not Applicable-Advanced Security mode detected" /> </Result> </Name> </Test> </Tests>

I have this error also. Not sure the solution though. Think we're in the wrong place in the technet tree though. "Exchange" - <Name xmlns="Testing MPCERT HTTP request functionality"> - <Result xmlns="Failed"> <Comment xmlns="The server is not operational" />

I am not sure if this has ever been resolved, but I was able to find a fix for this issue after many hours of troubleshooting. We have a forest where I have one primary site SMS 2003 SP2 Server, running Server 2000, and three secondary sites. The secondary sites are all in child domains, and we run in a mixed mode 2003/2000 environment. Did I also mention that these secondary servers are domain controllers? Inthe process of weeding out the old 2000 boxes I replaced the secondary SMS 2003 sites (Server 2000) with new hardware and OS's (Server 2003 SP2). I was able to successfully install the secondary sites on all of the servers, and ontwo of three of these secondary sites the MP successfully installed.... but one MPwould just not connect with the primary site. I would get the following errors on the secondary SMSserver: (SMS\Logs) MPCONTROL.LOG: Http verification .sms_aut (port 80) failed with status code 500, Internal Server Error (Windows\System32\CCM) MP_GetAuth.LOG: MPDB ERROR - CONNECTION PARAMETERSSQL Server Name : SMS1SQL Database Name : SMS_S00Integrated Auth : True MPDB ERROR - EXTENDED INFORMATIONMPDB Method : Init()MPDB Method HRESULT : 0x80040E4DError Description : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.OLEDB IID (Windows\System32\CCM) MP_Retry.LOG MPDB ERROR - CONNECTION PARAMETERSSQL Server Name : SMS1SQL Database Name : SMS_S00Integrated Auth : True MPDB ERROR - EXTENDED INFORMATIONMPDB Method : Init()MPDB Method HRESULT : 0x80040E4DError Description : Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.OLEDB IID Here is what I did totry andresolve this issue: 1. Confirmed my Secondary Server was in the correct local groups on the Primary Server. 2. Ran MP Troubleshooter (SMS 2003 Toolkit 2). 3. Added Service Principal Name using ADSIEDIT (2003 Support Tools) http://support.microsoft.com/kb/829868/en-us, I then prompty removed them, as it did not resolve the issue and caused the follow error on my other DC's: Date: 1/9/2008 12:52:17 PMAlarm Name: All ErrorsLog Type: SystemSource: KDCType Of Event: ErrorCategory: NoneEventID: 11Account: NONEComputer: ServerName Description: There are multiple accounts with name MSSQLSvc/SMS1.mydomain.com:1433 of type DS_SERVICE_PRINCIPAL_NAME. 4. On the Primary Site SMS Console, under the Secondary Sites>Site Systems>Server Name> Management Point Tab- I selected "Use a different database". To connect to the SMSDB I chose a domain admin account from the primary's local domain, which has every right you can think of on the Primary SMS Server, and on the domain. 5. In Active Directory Users and Computer I confirmed that the "SYSTEM MANAGEMENT" folder had the correct permissions. 6. I changing the Security settings in IISon SMS_MP Virtual Directory from Anonymous (using the IUSR_ServerName account) to integrated. 7. I uninstalled the MP on the Secondary, uninstalled IIS, rebooted, deleted the InetPub directory, reinstalled IIS and the MP. 8. Verified that the Schema had been extended (dcdiag) on the Secondary Site. 9. Rancliconfg.exe to confirm that Named Pipes was enabled on the Secondary Site. 10. Finally the discovery!!! When looking at the "MPDB ERROR - CONNECTION PARAMETERS" I ran across an article recommending I run DCDIAG and NetDiag (Server 2003 Support Tools). After running both of these I noticed some WINS incosistencies. The error I got ([WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.), and iteventually pointed me towards DNS- sort of. In DNS there is a parameter under properties where you can check "Use WINS forward lookup", and add IP addresses to forward DNS to WINS to resolve names. On the problematic server I noticed this was checked, and IP addresses pointing to other DC's were assigned. I then looked at my other two secondaries and discovered WINS forward lookup was not enabled. So instead of unchecking the WINS forward lookup on the problem server (DUH!)I enabled it on one of my working secondaries.... LOW AND BEHOLD, the working server's MP stopped talking to the primary; and began spewing out our favorite: Http verification .sms_aut (port 80) failed with status code 500, Internal Server Error. Hmmmmmm. I went back, unchecked WINS forward lookup on the formerly working secondary site, and then unchecked it on the problematic secondary site. Sadly it was quitting time, so I could not stick around for immediate gratification, but when I arrived the next morning the secondary MP's were all authenticating: Http verification .sms_aut (port 80) succeeded with status code 200, OK. As it turns out, it was an inconsistent WINS entry for the primary SMS server. When DNS uses the forward lookupitlooks to WINS fornames not found in the DNS domain namespace by checking the NetBIOS namespace managed by WINS. http://technet2.microsoft.com/windowsserver/en/library/eaf5f158-3229-4781-8281-4566c874a5541033.mspx?mfr=true As I said, in my case there was an incosistency in the WINS database (which I corrected),and thesiteswere attempting to connect toan incorrect NetBIOSname. How this resolved my issue I am still not completely sure. The moral to my story:A) Do not use WINS fwd lookup in an AD environment (if you can get away with it), and B) if you do have to use WINS fwd lookup be darned sure you keep your WINS database as clean as possible! I really hope this helps some of you out there. It has been an ordeal for me! Best Regards, Steve Hansen

I ended up uninstalling and re-setting up sms 2003 from scratch to resolve the issue.

Add 'NT AUTHORITY\ANONYMOUS LOGON' to SMS_SiteSystemToSQLConnection_CodeSiteAnd Restart secondary server.or use registry to add user and passwordLoaded MP settings cache from reg key HKLM\Software\Microsoft\SMS\MP:Database Settings:Server:servernameDatabase: SMS_CodesiteUser: <empty>Password: <empty>Use Integrated Security: YesImpersonation Required: Nobh.BH