SMS 2003 Site Status Component Error 1

[SLMHC]

I have been recieving this error since we upgraded from 2.0 to 2003 a few months back. When unable to remedy it i unistalled everything and did a fresh install of 2003 and rebuilt the databases. After a few weeks of rebuilding i noticed the same errors poping up. I am also not able to install Advanced clients to Win2k Pro or XP Pro workstations. I also have a hard time getting XP clients to accept a push intall. Here they are:

Type: Milestone
Severity: Error
Message ID: 1016
Process ID: 2504
Thread ID: 2512
Component: SMS_MP_CONTROL_MANAGER

SMS Site Component Manager failed to install this component on this site system.

Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the installation in 60 minutes. To force SMS Site Component Manager to immediately retry the installation, stop and restart SMS Site Component Manager using the SMS Service Manager.


Type: Detail
Severity: Error
Message ID: 4951
Process ID: 2504
Thread ID: 2512
Component: SMS_MP_CONTROL_MANAGER

SMS Site Component Manager failed to install this component, because the Microsoft Installer File for this component (MP.MSI) could not install.

Refer to the MPSetup.log, the MPMSI.log, as well as the SMS documentation and the Microsoft Knowledge Base for further information.

I assume that this mean my management point is not installing correctly. Any ideas on how to fix this and get my advanced clients to push out and get my XP systems to install?

Server Details:
Win2k Server
SP 4
SMS 2003
SUS SP 1
SQL 2000


If you need anymore info plase let me know what you need and i will reply with it.

thanks,
dave

 

[Jpoandl]

You Management Point must be working properly for the Advanced Client install to work. Things to check are:

How to check a Management Point

You can check if the MP is correct from the client side by checking

http://<management

point name>/sms_mp/.sms_aut?mplist. If this page comes up blank it is okay, but if the page comes back with any information, it generally means your MP is unavailable or misconfigured.

- OR -

by using the MP Spy tool from the SMS 2003 Tool Kit 1 Guide.

If you suspect there is a problem with your management point, here are some guidelines to help you troubleshoot the problem:


Check these log files:

1) MPSetup.log <-- This is the first log file created when the MP role is added. Towards the end of this log, you should see "Installation was successful"
2) MPMSI.log <-- This is the log of the actual MP MSI installation.
3) MPControl.log <-- After the MP is installed, this log is used to capture changes in the MP. This log continues to get updated after the install




If you think you have a problem with your Management Point, here are some troubleshooting tips:



SMS 2003 Management Point troubleshooting tips

http://myitforum.techtarget.com/articles/8/view.asp?id=6838

From the Microsoft Public Newsgroups:

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.







Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[SLMHC]

Here are the MP logs:

MPSETUP.log

<10-05-2004 08:22:28> ====================================================================
<10-05-2004 08:22:28> MP Setup Started....
<10-05-2004 08:22:28> Parameters: D:\SMS\bin\i386\MPsetup.exe /install /siteserver:SLS20008
<10-05-2004 08:22:28> Installing the MP
<10-05-2004 08:22:28> Passed OS version check.
<10-05-2004 08:22:28> IIS Service is installed.
<10-05-2004 08:22:28> No versions of MP are installed. Installing new MP.
<10-05-2004 08:22:28> Enabling MSI logging. MP.MSI will log to D:\SMS\logs\MPMSI.log
<10-05-2004 08:22:28> Installing D:\SMS\bin\i386\mp.msi CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SMS" CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<10-05-2004 08:23:13> Unknown error code: 452764
<10-05-2004 08:23:13> [8:23:13] @@ERR:25006
<10-05-2004 08:23:13> Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 80020009
<10-05-2004 08:23:20> MP.MSI exited with return code: 1603
<10-05-2004 08:23:20> Backing up MPMSI.log to D:\SMS\logs\MPMSI.log.LastError
<10-05-2004 08:23:20> Fatal MSI Error - MP.MSI could not be installed.

MPMSI.log
[8:22:33] WARNING: Network service account not available, ignoring ACE.

What does that error mean???

THere is no MPCONTROL.log.

The page

http://<MP

name>/sms_mp/.sms_aut?mplist returns a page cannot be found.

The page

http://<MP

name>/sms_mp/.sms_aut?mpcert also returns a page cannot be found.

Ill work through the rest of the list and get back to you.

thanks,

Dave

 

[SLMHC]

1) Run

http://<MP

name>/sms_mp/.sms_aut?mplist
This returns a blank screen.
<b>returns a page cannot be found</b>
2) Run

http://<MP

name>/sms_mp/.sms_aut?mpcert
<b>returns a page cannot be found</b>
3) Verify that the DTS Service is enabled.
<b>Not in services list</b>
4) Verify that the Task Scheduler is enabled.
<b>OK</b>
5) Verify that the Windows Management Instrumentation service is running.
<b>OK</b>
6) Verify that the SMS Agent Host service is running.
<b>Not in services list</b>
7) Verify that the World Wide Web Publishing Service is running.
<b>OK</b>
8) Verify that the MP machine account has been added to the
SMS_SiteSystemToSQLConnection_<site_code> group.
<b>OK</b>
9) Verify that the SQL Server has named pipes enabled.
<b>OK</b>
10) Update MDAC on the server.
<b>Done</b>
11) SQL boxes that are running under a user account, instead of system, need the SPN updated in AD.
<b>OK - The computers name is in the member list, this OK?</b>
12) Crossing domain boundaries between MP and SQL may also need the SPN updated in AD.
<b>SMS & SQL are on the same server</b>
13) IIS Lockdown Tool
<b>Not using Lockdown tool</b>
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.
<b>Dont wnat to do this yet as this is a SUS server as well and it took some IIS tweaks to get it running</b>


Is my problem that i have SUS and SMS on the same server???

thanks,

Dave

 

[Jpoandl]

I don't specifically what this error means but the installation package to install the MP did not succeed. Therefore, I would do this:

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.



Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please contact

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[SLMHC]

I was afraid you were going to say that!


thanks,

Dave

 

[SLMHC]

Ok, i have reinstalled IIS on the MP server. I was able to move SUS off of that machine as well so there should be no conflicts with it. I will report back on the new installation.

Questions:
What is the DTS Service?
Where am I enabling BITS and WEBDEV? BITS is set to manual startup in services.

thanks,

Dave

 

[SLMHC]

Also should mention that

http://<MP

name>/sms_mp/.sms_aut?mpcert returns the list of numbers &

http://<MP

name>/sms_mp/.sms_aut?mplist returns a blank page.

thanks,

Dave

 

[malshade]

I've been having similar problems. How does one verify that SQL has named pipes enabled? Thanks.

 

[tbrennans]

http://support.microsoft.com/kb/68941

or just open the current SQL Server Error Log. You should see lines similar to the following:

2002 12 14 09:49:36.17 server SQL server listening on TCP, Shared Memory, Named Pipes.
2002 12 14 09:49:36.17 server SQL server listening on 192.168.1.5:1433, 127.0.0.1:1433.