betemtl
Posts: 31
Score: 0 Joined: 4/10/2008 Status: offline
|
Hi, I am running SCCM2007 on a Widnows 2003 sp2 32bit with SQL2005 SP2. My problems started when we upgraded SQL to SP2. I am obtainign the following errors, messages: in SCCM 2007 when trying to start the configMgr Service Manager: (Error communicating with the specified ConfigMgr Site Server. but under Site status --> component status all services are reported as ok (they are all Green) under site system status (All of them are green, except fro CinfigMgr management point and ConfigMgr PXE service point, have a warning display) But I don't see any error messages.In fact I dont have any single messages. I also tried a Import Computer Information from Computer Association and add it into a Collection called OSD Deployment, but the system never gets added into the collection. SQL 2005 SP@ seems to be communicating properly. When looknig in the event viewer i found the following:EventID 5436 On 8/6/2008 6:45:32 AM, component SMS_MP_CONTROL_MANAGER on computer TEST reported: MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error. Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. 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 designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated 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.
|