Re: SMS 2003 Sec. Site Management Point doesn't work
From: Travis Sweat \(MSFT\) (travsw_at_microsoft.com)
Date: 03/26/04
- Next message: Al Corsi: "Re: SMSPKGx$"
- Previous message: Mark Scott [MSFT]: "Re: Remove SMS 2"
- In reply to: Franz Schenk: "SMS 2003 Sec. Site Management Point doesn't work"
- Next in thread: Franz Schenk: "Re: SMS 2003 Sec. Site Management Point doesn't work - Part 2"
- Reply: Franz Schenk: "Re: SMS 2003 Sec. Site Management Point doesn't work - Part 2"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 26 Mar 2004 07:34:02 -0800
Here is the standard list of troubleshooting steps. Try these and let me
know if they don't work. Could you also send me the MPControl.log, the
ccmexec.log.
Thanks.
T
This was intended to be in least intrusive to most intrusive order.
1.. Run http://
1.. This returns a blank screen.
2.. Run http://
1.. This returns a long list of numbers and letters.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is running.
6.. Verify that the SMS Agent Host service is running.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Verify that the SQL Server has named pipes enabled.
10.. Update MDAC on the server.
1.. Review Q820910 for details.
2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;820910
11.. SQL boxes that are running under a user account, instead of system,
need the SPN updated in AD.
1.. Review Q829868 for additional details.
2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
12.. Crossing domain boundaries between MP and SQL may also need the SPN
updated in AD.
1.. Review Q829868 for additional details.
2.. http://support.microsoft.com/default.aspx?scid=kb;en-us;829868
13.. IIS Lockdown Tool
1.. If you are using the IIS lockdown tool on your IIS 5 servers be sure
to apply the SMS server template from the SMS 2003 toolkit.
2.. http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp
14.. Deinstall the MP and IIS, then reinstall IIS and the MP.
1.. Remove the MP role on the server.
2.. Disable IIS. Remove completely. Reboot the server.
3.. Verify that the DTS Service is enabled.
4.. Verify that the Task Scheduler is enabled.
5.. Verify that the Windows Management Instrumentation service is
running.
6.. Enable BITS, enable WEBDEV and install IIS.
7.. Verify that the World Wide Web Publishing Service is running.
8.. Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
9.. Enable MP role on the server.
--
Travis Sweat [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
"Franz Schenk" <franz.schenkNOSPAM@fititNO-_SPAM.ch> wrote in message
news:u4whaKoEEHA.3404@TK2MSFTNGP10.phx.gbl...
> On a customers remote location is a SMS 2003 secondary site server where
> we
> have configured a proxy management point. The server has two IP adresses
> and
> IIS (the default Web Site) is bound to a specific IP adress. IIS is
> running
> without any problem.
>
> But the SMS proxy management point doesn't work: every hour, we get an
> error
> status message of SMS_MP Control Manager with Event ID 5436: "MP Control
> manager Detected MP is not responding to HTTP requests. The http error is
> Object Not Found".
>
> We restarted IIS, MP Service, The whole server. We also cleared the
> checkbox
> "This is a management point" on the secondary site server, waited an hour,
> re-enabled the same checkbox, but no success. Event 5436 appears every
> hour.
>
> Thank you all in advance for any advice
> Franz
>
>
Relevant Pages
... Verify that the Task Scheduler is enabled. ... Verify that the SMS Agent Host service is running. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ...
(microsoft.public.sms.admin)
... Verify that the Task Scheduler is enabled. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ... I've successfully turned up> a Management Point on the Central Site server. ...
(microsoft.public.sms.admin)
... and the secondary site server is W2K3/ running IIS 6.0, ... Start IIS Admin ... If there was a problem with the IWAM account, ... Verify that the Task Scheduler is enabled. ...
(microsoft.public.sms.admin)
... you want to remove is the site role called "management Point Role". ... It depends where SMS was originally installed. ... which the server would use when it's a client (of SMS or other ... things that use BITS), not the "IIS BITS Server Extensions", which would not ...
(microsoft.public.sms.installer)
... Verify that the Task Scheduler is enabled. ... Verify that the SQL Server has named pipes enabled. ... If you are using the IIS lockdown tool on your IIS 5 servers be sure ...
(microsoft.public.sms.admin)