SMS 2003 - Troubleshooting - MP Control Manager Related Issues (IIS)

I had spent some time yesterday researching and correcting an IIS-related issue with my MP on a particular Site Server. Another issue was present on which I had found some information, but had not found a resolution. Again, within the Application Event log on the Site Server, the following errors were showing:

Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\mssindex\Performance\Library, error code: 0x80041009

Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\MSSGTHRSVC\Performance\Library, error code: 0x80041009


Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\MSSGatherer\Performance\Library, error code: 0x80041009


Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\MSSEARCH\Performance\Library, error code: 0x80041009


Event_ID: 47

WMI ADAP was unable to retrieve data from the PerfLib subkey: SYSTEM\CurrentControlSet\Services\Autocat\Performance\Library, error code: 0x80041009


The research I performed indicated there were some additional permissions which needed to be made - and these were already present when I checked the various areas listed. But, to my surprise, these errors disappeared after my re-installation of IIS yesterday. All Event Logs were clear of the problems reported yesterday.

I will still research this, but for the time being, I'm going to attribute yesterday's problems to a corrupt IIS installation. If anyone has had these issues and found an alternate solution, please post a comment.

SMS 2003 - Troubleshooting - MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory

This morning greeted me with an error message I had not seen in quite a while. As I was going through my normal "morning check" of our various SMS sites, I noticed one particular site was lit up like a Christmas tree. Both the OS Application Event log and the SMS_MP_CONTROL_MANAGER had multiple errors displaying:

SMS_MP_CONTROL_MANAGER:

Message ID: 1020

SMS Site Component Manager failed to reinstall 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 reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager.

Message ID: 4963

MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

Possible cause: The IIS IWAM account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IWAM account. (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use “net user” to modify the account properties.

Possible cause: The IIS IUSR account has expired, been disabled, or has invalid or too restrictive logon hours. You may verify this information by running the net user command line for the IUSR account. (i.e.: “net user IWAMMachineName)
Solution: Use the output to verify that the account is enabled, and logon is possible during the time of installation. Note: You can use “net user” to modify the account properties.

Possible cause: The Default Web Site is disabled in IIS.
Solution: Verify that the Default Web Site is enabled, and functioning properly.


Application Event Log:

Event_ID: 10005

Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_System
The error code is 80020009


MPSetup.log: (at the tail end of the MP installation log)

<05-02-2007 09:57:45> Setup was unable to create the Internet virtual directory CCM_System
The error code is 80020009
<05-02-2007 09:58:00> MP.MSI exited with return code: 1603
<05-02-2007 09:58:00> Backing up MPMSI.log to E:\SMS\logs\MPMSI.log.LastError
<05-02-2007 09:58:00> Fatal MSI Error - MP.MSI could not be installed.


I've had this error before, generally after a site reset required after an upgrade. In the past I've tried recommended fixes of starting and stopping services, rebooting, etc., etc. But, none of these methods ever worked consistently from one time to the next. Following is how I solve this problem and it has worked for me 100% of the time:

- Remove the MP role from the Site Server. Watch the MPSetup.log to ensure that the removal is complete.
- Uninstall the IIS component from the OS of the Site Server.
- Reboot the Site Server.
- Run ccmdelcert.exe from the SMS Toolkit.
- Reinstall the IIS component (with BITS) on the OS of the Site Server.
- Go into the IIS manager and allow WebDav.
- Add the MP role to the Site Server. Watch the MPSetup.log to ensure that the installation completes correctly.

Again, in my experience, I've never had this method fail, nor hork up any other process on the Site Server. Other experiences may vary, but I can only speak to my own. I hope this helps someone out there.

SMS 2003 - Updates - SP3 is LIVE

I'm not sure about the rest of you, but for me, this is a very exciting day. I've had SP3 in the test lab for a while now, and I do like the extra features it offers. Here is the Microsoft summary and the link.

<<>>
Overview
Microsoft Systems Management Server (SMS) 2003 with Service Pack 3 (SP3) brings full Vista support to your organization beyond just OS Deployment, which is already available through the OS Deployment Feature Pack. Now, full lifecycle support of Microsoft’s latest platform including software distribution, update services as well as inventory are available to the Vista Client. In addition, SP3 introduces X64 architecture support for your high performance platforms. SMS 2003 SP3 provides an option to augment existing SMS inventory capabilities with deeper asset intelligence, bringing knowledge driven management with over 400,000 software titles in the library.

Install the “SMS 2003 Device Management Feature Pack” to correct the device file collection issue after applying SMS 2003 SP3. Please reference KB 934206 for more details (http://support.microsoft.com/kb/934206/ )
<<>>


SMS 2003 Service Pack 3 Home Page

SMS 2003 - Troubleshooting - 4918 Errors in SMS_SITE_COMPONENT_MANAGER

If you've recently upgraded your SMS infrastructure to SP2, you may have encountered repeating 4918 errors within the SMS_SITE_COMPONENT_MANAGER component. Here is a brief of how the error would read:

<<>>
Message ID: 4918

Systems Management Server cannot update the dNSHostName property for the existing object "cn=SMS-MP-Z13-LWSMSLWPRIM" in Active Directory. This property is used to publish fully qualified host names in Active Directory.

Possible cause: The Active Directory schema has not been extended with latest version of the SMS Active Directory classes and attributes.
Solution: Ensure the schema has been extended with the latest version of the SMS Active Directory classes and attributes. The schema can be extended with the tool "extadsch.exe" from the SMS directory on the SMS Site server that reported this message.
<<>>

The resolution presented is correct in this situation. SP2 for SMS 2003 has an added feature of utilizing the Site Server FQDN's within Active Directory. To use this function, you must extend the Active Directory Schema. The tools you need are provided with the SP2 upgrade files. You can extend the schema using extadsh.exe or with the provided LDIF file using ldifde.exe. I've provided links to explanations for both methods, but I prefer using extadsh.exe.

*** It should be noted that it is NOT necessary to extend the schema for SP2 if you do not plan on taking advantaged of the extended features. These errors are not malicious and will not affect the operation of your site.

Blogcast For EXTADSH.EXE

Technical Document for Using LDIFDE.EXE