MP is not responding to HTTP requests

I am having the following error on my SMS status viewer. The box is Win2k
server SP4, SMS SP1. I've tried to restart the SMS agent host service, w3svc
serivce, and also checked to make sure the server name was in the group
SMS_SiteSystemToSQLConnection_<sitecode > on the local box. I have yet to try
anything else as SMS is fairly new to us. Any help would be greatly
appreciated. I also tried the MP troubleshooter (post installation) and it
fails on Testing MPLIST HTTP request functionality, and Testing MPCERT HTTP
request functionality.

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

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.

.

Relevant Pages

  • Re: Does anyone know how to fix this??
    ... > Inside the Active Directory Users and Computers in the folder of SYSTEM I ... Give the site's SMS Service account full control rights to the ... MP encountered an error when connecting to SQL Server. ...
    (microsoft.public.sms.setup)
  • Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Failed to get a SQL Server connection
    ... remote SQL Server device. ... check that you have installed the SMS SQL database on the default ... Use the output to verify that the account is enabled, ... SMS Site Component Manager failed to reinstall this component on this site ...
    (microsoft.public.sms.setup)
  • Re: Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ... SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. ...
    (microsoft.public.sms.admin)
  • Re: SMS Component errors after installing SP2
    ... MVP Windows Server System - SMS ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ... is used to publish fully qualified host names in Active Directory. ...
    (microsoft.public.sms.setup)