MP woes

[malshade]

Working on this list:

this list is bad for my health!

I started having problems right away with 1-3. The webpages come up as not found, error 404. The DTS service is not avail on either the MP or the site server. The SMS log shows MP.msi not installing successfully. I've tried to do install MP.msi manually and it doesn't complete. Help?

1) Run

http://<MP

name>/sms_mp/.sms_aut?mplist
This returns a blank screen.
2) Run

http://<MP

name>/sms_mp/.sms_aut?mpcert
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.
Review Q820910 for details.

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.
Review Q829868 for additional details.

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.
Review Q829868 for additional details.

http://support.microsoft.com/default.aspx?scid=kb;en-us;829868

13) IIS Lockdown Tool
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.

http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp

14) Deinstall the MP and IIS, then reinstall IIS and the MP.
a) Remove the MP role on the server.
b) Disable IIS. Remove completely. Reboot the server.
c) Verify that the DTS Service is enabled.
d) Verify that the Task Scheduler is enabled.
e) Verify that the Windows Management Instrumentation service is
running.
f) Enable BITS, enable WEBDEV and install IIS.
g) Verify that the World Wide Web Publishing Service is running.
h) Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
i) Enable MP role on the server.

 

[tbrennans]

Take a look at Brian T's site and see if it helps:

http://www.blogcastrepository.com/

SMS 2003 Management Point Prerequisites

 

[dalv]

There are number of things that you need to look at here.

1. Make sure that the Host agent Service has started. This could stop if the SMS client is uninstalled from the server. It will not work if you just start the service manually. You will need to remove the Management Point and reinstall it. This will start the Host agent.

2. Make sure that you have installed IIS. You need IIS if you are runing SMS 2003 advance client mode

3. Look at the rights the SQL is using, If you are using advance security mode, then SQL must be set to use Windows Authentication mode only.

4. SPNs must be registered within AD.

Hope that this helps

 

[malshade]

Thanks for the link Tbre. Tucker has actually been helping me out, kinda cool. Dalv, questions about numbers 1 and 4 on your list: Make sure host service is started on what machine MP or Site Svr? How does one verify the registration of SPN's within AD? I don't even know what an SPN is...

Thanks

 

[globalstrata]

Server Principal Name (SPN)

http://support.microsoft.com/?kbid=832109

http://support.microsoft.com/?kbid=829868

Good Luck,


Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[dalv]

To answer question 1 -
Host agent should be running on both.

Question 4 has been answered by globalstrata - Thanks