I get these errors on the Primary site
and Secondary site. I completely removed SMS from both sites and reinstalled
but get the same errors. I have verified that WMI and the Agent Host services
are starting OK, and the Agent host after WMI. And restarting IIS, or
reinstalling it haven't helped. The server is Windows 2000 SP4, also running SUS
and ePolicy Orchestrator. Here are entries from MPCONTROL.LOG, and from the
Component status in the Admin Console. But for the most part, I get http error
12152 (.sms_aut failed to verify).
MPCONTROL.LOG:
------- SMS_MP_CONTROL_MANAGER
1/9/2004 11:32:31 AM 2952 (0x0B88
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned
0x0 SMS_MP_CONTROL_MANAGER 1/9/2004 11:32:31 AM 2952 (0x0B88)
Failed to receive http response. Error
12152 SMS_MP_CONTROL_MANAGER 1/9/2004 11:40:33 AM 2952 (0x0B88)
Http verification .sms_aut failed with no header
recieved SMS_MP_CONTROL_MANAGER 1/9/2004 11:40:33 AM 2952 (0x0B88)
Failed to receive http response. Error
12152 SMS_MP_CONTROL_MANAGER 1/9/2004 11:50:33 AM 2952 (0x0B88)
Http verification .sms_aut failed with no header
recieved SMS_MP_CONTROL_MANAGER 1/9/2004 11:50:33 AM 2952 (0x0B88)
STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server"
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned
0x0 SMS_MP_CONTROL_MANAGER 1/9/2004 11:32:31 AM 2952 (0x0B88)
Failed to receive http response. Error
12152 SMS_MP_CONTROL_MANAGER 1/9/2004 11:40:33 AM 2952 (0x0B88)
Http verification .sms_aut failed with no header
recieved SMS_MP_CONTROL_MANAGER 1/9/2004 11:40:33 AM 2952 (0x0B88)
Failed to receive http response. Error
12152 SMS_MP_CONTROL_MANAGER
Admin Console:
Severity Type Site code Date / Time System Component Message
ID Description
Information Milestone 101 1/9/2004 12:38:19
PM NTSERV7 SMS_MP_CONTROL_MANAGER 500 This component started.
Information Milestone 101 1/9/2004 12:38:14
PM NTSERV7 SMS_MP_CONTROL_MANAGER 502 This component stopped.
Information Milestone 101 1/9/2004 12:38:11
PM NTSERV7 SMS_MP_CONTROL_MANAGER 501 This component was signalled to
stop by an administrator or the operating system. The component will
complete any processing it is doing and stop at a safe point in time.
If the component or this computer is very busy, it may take several
minutes for the component to stop.
Error Milestone 101 1/9/2004 11:50:33
AM NTSERV7 SMS_MP_CONTROL_MANAGER 5436 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
MP can connect to the SQL server and has sufficient access rights to
the SQL server site system. Possible cause: The Default Web Site
is disabled in IIS. Solution: Verify that the Default Web Site is
enabled, and functioning properly.
Contributed By: Eric Holtz [MSFT]
You may be having MP -> SQL connection errors. This causes
MP_Control_Manager errors.
You'll need to figure out why the MP cannot connect to SQL.
- If Advanced Security, and this is a
secondary site - verify that the Proxy MP's SQL account is the SQL Connection
Group on the Primary SQL server.
- If Advanced Security, verify SQL is SQL 2K
SP3.
Else, check these:
Update MDAC on the server.
Review
Q820910 for details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
SQL boxes that are running under a user account, instead of system, need the
SPN updated in AD.
Review
Q829868 for additional details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
Crossing domain boundaries between MP and SQL may also need the SPN updated in
AD.
Review
Q829868 for additional details.
http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
Contributed By:
Richard Threlkeld [MVP SMS]
There was also a
recently found solution where these errors can occur and the resolution is to
install MDAC 2.8. If Eric's suggestions do not work try that as well.
|
 |
To see other SMS
2003 Troubleshooting FAQs click here. |
|
