MP Control Manager Issue

• Previous message: Jeff Harbaugh [MSFT]: "Re: SMS Servers fighting!!"
• Next in thread: Travis Sweat \(MSFT\): "Re: MP Control Manager Issue"
• Reply: Travis Sweat \(MSFT\): "Re: MP Control Manager Issue"
• Messages sorted by: [ date ] [ thread ]

Date: Mon, 6 Dec 2004 13:13:03 -0800

My System:
Windows 2003 Standard Server
SMS 2003 SP1
SQL 2003 SP3
IIS 6.0
--------------------------------------------------------------------------------------------
I have installed SMS 2003 on the domain and trying to finish the setup and
getting
an error dealling with MP Controller Manager.
Ran the MPTroubershooter and getting a message that the mplist and mpcert
attempt is unauthorized. verified all passwords and user accounts.
after a iisreset then I can access the mplist and mpcert pages but few hours
later
will end up with the error message again. Have reviewed and verified all
issues listed below in the error message. This is error is preventing me from
doing the final setup of installing Advance Clients on my Windows XP systems.
 I did an independent of the main network test lab and ironed out any issues
and had it running. Now I am installing it on live network and have run into
this MP Control Manager Issue which I did not have in the test lab setup. I
compared all settings between the test server and the sms server have same
settings. Any other suggestions?

--------------------------------------------------------------------------------------------
The Error Message I am getting:

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.

For more information, refer to Microsoft Knowledge Base article 838891.

• Previous message: Jeff Harbaugh [MSFT]: "Re: SMS Servers fighting!!"
• Next in thread: Travis Sweat \(MSFT\): "Re: MP Control Manager Issue"
• Reply: Travis Sweat \(MSFT\): "Re: MP Control Manager Issue"
• Messages sorted by: [ date ] [ thread ]