Re: SMS_MP_Control_Manager Errors
- From: RobM <RobM@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 28 Jun 2006 06:04:02 -0700
.... could be you need to use Named Pipes instead of TCP\IP in Data Sources
(ODBC)?
--
Rob - Windows Management User Group
www.wmug.co.uk
"JCL2005" wrote:
Be more expecific, i'm not sure how verify if WMI is configured, not too.
experienced with SMS. This is our first phase of our pilot and it has become
quite challenging to resolve this type of issues.
"abnascimento@xxxxxxxxx" wrote:
Did you try to do that is recommended?
Like restart IIS.
MP are connect to Database throught the IIS. Verify if WMI is
configured to permit this.
use dcomcnfg.exe.
JCL2005 wrote:
I have been trying to find a solution for this, two days and can't figure it
out. So here it is, I have tried several of the articles offered by MS.
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone AR1 6/27/2006 8:30:01
AM ARBUENMEYSDTST SMS_MP_CONTROL_MANAGER 5436 MP Control Manager detected MP
is not responding to HTTP requests. The http error is Unauthorized.
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.
- Follow-Ups:
- Re: SMS_MP_Control_Manager Errors
- From: JCL2005
- Re: SMS_MP_Control_Manager Errors
- References:
- Re: SMS_MP_Control_Manager Errors
- From: abnascimento@xxxxxxxxx
- Re: SMS_MP_Control_Manager Errors
- Prev by Date: RE: Automatic Site Code Discovery was unsuccessful
- Next by Date: Unable to Create Collection/Query On Custom Created Data (WMI/MOF)
- Previous by thread: Re: SMS_MP_Control_Manager Errors
- Next by thread: Re: SMS_MP_Control_Manager Errors
- Index(es):
Relevant Pages
|
