Re: Http verification .sms_aut (port 80) failed
- From: Cristiano <Cristiano@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Jun 2007 07:46:00 -0700
Hi Jon,
I resolved a problem like this changing the Security settings on SMS_MP
Virtual Directory:
- Remove Integrated Windows Authentication
- Set Anonymous Access
I run also MPTroubleshooter confirms that it is ok.
I hope this can help you.
Bye.
Cristiano
"Jon" wrote:
I'm still checking to be sure... I think I was able to get this fixed today!.
I had to go into SQL Server Configuration Manager / SQL Server 2005 Network
Configuration / Protocols for MSSQLSERVER / TCP/IP and "Enable."
This was the "fix" for me.
I am SO glad to have this one figured out!
Thanks!
Jon
"Jon" wrote:
Thank you, Nick, I'm working through that document now that you suggested it.
(Don't know what else to do. :-)
"nick" wrote:
On 31 May, 23:50, Jon <J...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Greetings,
A couple of days ago, I noticed I couldn't get SMS reports to work....
(later I found I couldn't deploy software via SMS). I'm running SMS 2003 SP3
on Windows 2003 SP1 with advanced security and the AD schema has been
extended using the SMS 2003 SP3 extension. Please take a look at the
information I have collected so far and see if you can help me get to the
root of my SMS problem.
*******************************************************
************** Error message I received: *************
*******************************************************
An error occurred when the report was run. The details are as follows:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.
Error Number: -2147467259
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 17
*******************************************************
I started looking into the problem and found the MP is not talking to the
database.
*******************************************************
Event Type: Error
Event Source: SMS Server
Event Category: SMS_MP_FILE_DISPATCH_MANAGER
Event ID: 5436
Date: 5/30/2007
Time: 1:30:36 PM
User: N/A
Computer: SMS
Description:
On 05/30/07 13:30:36, component SMS_MP_CONTROL_MANAGER on computer SMS
reported: 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.
*******************************************************
********* ...and another one... ************
*******************************************************
SMS Management Point encountered an error when connecting to its Database
SMS_SPU on SQL Server SMS. The OLEDB error code was 0x80004005.
Possible cause: The SQL server site system is turned off, not connected to
the network, or not functioning properly.
Solution: Verify that the SQL server site system is turned on, connected to
the network, and functioning properly.
Possible cause: SMS Management Point does not have sufficient access rights
to the SQL server site system.
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: Network problems are preventing SMS Management Point from
properly accessing the SQL server.
Solution: Investigate and correct any problems with your network.
Possible cause: The Management Point having problems is at a secondary site,
and SQL access account being used was recently reset by the parent site.
Solution: This can automatically repair itself after one hour , as long as
the account in use is not locked out. Check that the account in use is not
locked out. Instead of waiting an hour, you can stop and start the
SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration.
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.
Http verification .sms_aut (port 80) succeeded with status code 200, OK
5/29/2007 2:43:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) succeeded with status code 200, OK
5/29/2007 2:53:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) succeeded with status code 200, OK
5/29/2007 3:03:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) succeeded with status code 200, OK
5/29/2007 3:13:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
*******************************************************
****** It looks like this is when the problem happened! ********
*******************************************************
------ MPNotifyThreadRoutine(): Got a change Notification! -------
5/29/2007 3:13:40 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
------ RegisterForNotification(): Registering again! -------
5/29/2007 3:13:40 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned 0x0 5/29/2007
3:13:40 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error 5/29/2007 3:23:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
------ MPNotifyThreadRoutine(): Got a change Notification! -------
5/29/2007 3:23:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
------ RegisterForNotification(): Registering again! -------
5/29/2007 3:23:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
MPNotifyThreadRoutine(): HandleMPRegistryChanges() returned 0x0 5/29/2007
3:23:38 PM 10684 (0x29BC) SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error 5/29/2007 3:33:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server"
COMP="SMS_MP_CONTROL_MANAGER" SYS=SMS SITE=SPU PID=14040 TID=10684
GMTDATE=Tue May 29 22:33:38.527 2007 ISTR0="Internal Server Error" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 5/29/2007 3:33:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error 5/29/2007 3:43:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error 5/29/2007 3:53:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error 5/29/2007 4:03:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
Http verification .sms_aut (port 80) failed with status code 500, Internal
Server Error 5/29/2007 4:13:38 PM 10684 (0x29BC)
SMS_MP_CONTROL_MANAGER
*******************************************************
*******************************************************
I know the database is OK. (Just can't connect to it)
I've verified the SQL services are running.
I cannot think of anything that has changed. (obviously SOMETHING has
changed)
I've run the MP troubleshooter and the tests pass in the Pre-Install tab but
I cannot access the database on the Post-Install tab. I get an error message
that says "SQL Server does not exist or access denied."
I have also successfully run the "SMS Site Repair Wizard" and chosen a time
prior to May 29 to roll back to. I ran the wizard twice, once I repaired the
site without touching the database. The second time I ran it and had it
repair the database too. Both resulted in "Site repair completed
successfully."
I've been looking at this problem non-stop and now my eyes are about to pop!
Your help would be VERY much appreciated.
Thanks!
Jon
this document may be of some use
http://www.microsoft.com/technet/sms/2003/library/managepoint/default.mspx
- References:
- Prev by Date: Re: New Secondary Site clients not communicating
- Next by Date: Re: All the existing addresses to destination site C00 are closed
- Previous by thread: Re: Http verification .sms_aut (port 80) failed
- Next by thread: Re: Querying machines missing win32_LocalAdmins class
- Index(es):
Relevant Pages
|
