Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMS_MP_CONTROL_MANAGER Error 5436 3

Status
Not open for further replies.

0715

Technical User
Nov 5, 2004
11
I have been trying to get SMS 2003 working on my LAN

I am using Windows 2003 Server as my Primary Site, which is also the SQL server , SQL 2000 SP3

I have managed to eliminate most of the errors I was getting on my site status

I some how havent been able to take care of this

MP Control Manager detected MP is not responding to HTTP requests. The http error is 12152.

Possible cause: MP service is not started or not responding.
Solution: Manually restart the SMS Agent Host service on the MP.

Possible cause: IIS service is not responding.
Solution: Manually restart the W3SVC service on the MP.

Possible cause: MP encountered an error when connecting to SQL Server.
Solution: Verify that the SQL server is properly configured to allow Management Point access. If using a standard SQL security account, verify that the SQL Server is configured to allow standard SQL Security; or configure the Management Point to use an NT integrated security account, with appropriate access. If using integrated security, verify the account used by the MP to connect to the SQL server is a member of the SMS_SiteSystemToSQLConnection_<sitecode > group on the SQL server, that the account is not locked out, and that the account password is not expired. (In standard security, the default account is SMS_SQL_RX_<sitecode>.)

Possible cause: The SQL server Service Principal Names (SPNs) are not registered correctly in Active Directory
Solution: Ensure SQL server SPNs are correctly registered. Review Q829868.

Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate.
Solution: Verify that the Default Web Site is configured to use the same ports which SMS is configured to use.

Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning properly.

Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy.

For more information, refer to Microsoft Knowledge Base article 838891.

I have tried to resolve most of the issues but I am still repeatedly getting this error,

I am new to SMS and am not sure what I can do to solve this problem

Any Suggestions?

I have already Installed IIS and BITS and also set permissions for IUSR_Computername to the SMS CONTAINER in AD
 
make sure if your using advanced security that the MP machine account is in the SiteSystemToSQLServer connection group.

If you are in standard security, make sure that the account specified on the admin UI has rights to the SQL server (is a member of the SiteSystemToSQLserver connection group)

 
Also check the MP*.log logs in the CCM\logs folder. You might find more information here...

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact (Sales@njcomputernetworks.com)
 
thanks for your responses....Any idea what i should be looking out for in the logs....and which log in particular might have information to related to my problem....about the SiteSystemToSQLServer connection group.... what be an example of this group on a machine....i am new to SMS so i am not sure where to find it????
 
Actually, you might want to look at this article first: Error 15212
On the Primary SMS Site Server, you should go into Manage Computer (right click on MY Computer and choose MANAGE from the drop down box). You then should go into the GROUPS folder and look for the SiteSystemToSQLServer group. Add you MP computer account to this group. By doing this, you will be giving your MP computer account the rights to your SMS site. This is necessary for a management point to read the SQL database. More information:
The logs you want to look at have "MP" in the name of the logs. SMS_CCM\LOGS\MP_ddr.log, MP_framwork.log, MP_GetAuth.log, MP.Getpolicy.log, MP_Hinv.log, etc...

You should down load the SMS 2003 Toolkit. The tool kit, once installed, will give your the SMSTRACE utility. This utility make it much more easy to read log files. It will allow you to see error in RED and warnings in YELLOW. You can down load these tools here:
More information:

Testing a MP:


Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact (Sales@njcomputernetworks.com)
 
Thanks for the response....At least I seem to be moving in the right direction
I added my MP computer to the SiteSystemToSQLServer group....As far as the logs in SMS_CCM\LOGS\*.log there doesnt seem to be any errors

However I looked at the log in sms_SiteNumber\logs\mpcontrol.log and heres what I found

the same error repeated throughout

STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" SYS=ADMINB2003 SITE=123 PID=716 TID=3724 GMTDATE=Mon Feb 14 19:24:37.515 2005 ISTR0="12152" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MP_CONTROL_MANAGER 2/14/2005 2:24:37 PM 3724 (0x0E8C)

Failed to receive http response. Error 12152 SMS_MP_CONTROL_MANAGER 2/14/2005 2:34:29 PM 3724 (0x0E8C)

Http verification .sms_aut (port 80) failed with no header received SMS_MP_CONTROL_MANAGER 2/14/2005 2:34:29 PM 3724 (0x0E8C)

I checked out the myitforum links you sent me....my mdac is already version 2.8

also when i run the MPTroubleshooter

- <Name xmlns="Verify that the SMS Agent Host Service is running.">
- <Result xmlns="Failed">
<Comment xmlns="" />

- <Name xmlns="Testing MPLIST HTTP request functionality">
- <Result xmlns="Failed">
<Comment xmlns="Failed to query web site: (Exception: The underlying connection was closed: An unexpected error occurred on a receive.)" />
</Result>
- <Name xmlns="Testing MPCERT HTTP request functionality">
- <Result xmlns="Failed">
<Comment xmlns="Failed to query web site: />
</Result>
</Name>
any clues?????
 
so are you tryin to say i need to add the

NetBIOS SPN entry:

MSSQLSvc/sqlhost:1433

I have done that so lets see if that helps!
 
in any case... i tried all i could to make the configuration work.... but it didn't....what was useful though is that i learned a lot about SMS 2003....the next step was to do a fresh installation and thats exactly what i have done....everything seems to be running smooth for now....i guess mu installation was flawed from the beginning...:)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top