Error Proxy Management Proxy

I am with a problem of MP in one secondary site, I verified all the steps
that the SMS ask, and pparently is all certainty. If somebody knows what it
is generating this error?

MP Control Manager detected MP is not responding to HTTP requests. The http
error is Internal Server Error.

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.


------ MPNotifyThreadRoutine(): Got a change Notification!
------- SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
------ RegisterForNotification(): Registering again!
------- SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned
0x0 SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
------ MPNotifyThreadRoutine(): Got a change Notification!
------- SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
------ RegisterForNotification(): Registering again!
------- SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned
0x0 SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
------ MPNotifyThreadRoutine(): Got a change Notification!
------- SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
------ RegisterForNotification(): Registering again!
------- SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned
0x0 SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server"
COMP="SMS_MP_CONTROL_MANAGER" SYS=BRGRUAS01 SITE=GRU PID=1088 TID=3668
GMTDATE=Tue Sep 05 13:11:12.212 2006 ISTR0="Internal Server Error" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server"
COMP="SMS_MP_CONTROL_MANAGER" SYS=BRGRUAS01 SITE=GRU PID=1088 TID=3668
GMTDATE=Tue Sep 05 14:11:12.188 2006 ISTR0="Internal Server Error" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54)
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error SMS_MP_CONTROL_MANAGER 01/01/1601 00:00:00 3668 (0x0E54

.

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: 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)
  • 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)