Microsoft KB Archive/917675

= How to troubleshoot an SMS 2003 management point installation that does not create the required virtual directory =

Article ID: 917675

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-





INTRODUCTION
This article contains information to help you troubleshoot a Microsoft Systems Management Server (SMS) 2003 management point installation that does not create the required virtual directory. When this problem occurs, management point installation fails. Additionally, one or more of the following errors are logged in the MPSetup.log file or in the MPMsi.log file:

< > Unknown error code: 456012

< > [ ] @@ERR:25006

< > Setup was unable to create the Internet virtual directory CCM_Incoming The error code is 80020009

< > MP.MSI exited with return code: 1603

< > Fatal MSI Error - MP.MSI could not be installed.

Setup was unable to create the Internet virtual directory CCM_System The error code is 80020009

The following causes are discussed:
 * The COM+ catalog is corrupted
 * Microsoft Internet Information Services (IIS) DCOM components are missing
 * COM+ service issues
 * Microsoft Distributed Transaction Coordinator (MS DTC) service issues
 * IIS metabase issues
 * A Task Scheduler error



MORE INFORMATION
When the SMS management point is not installed, the following log files may help you troubleshoot the problem:
 * The following site server log files:
 * :\SMS\Logs\Mpcontrol.log
 * :\SMS\Logs\MPSetup.log
 * :\SMS\Logs\MPmsi.log
 * The management point server System event log

The COM+ catalog is corrupted
To determine whether the COM+ catalog is corrupted, follow these steps:  On the management point server, click Start, click Run, type dcomcnfg.exe, and then click OK. Click Component Services, expand Computers, expand My Computer, and then click COM+ Applications. If you receive the following error message, the COM+ catalog is damaged:

An error occurred while processing the last operation. Error Code 8007007E - The specified module could not be found.



Resolution
To resolve this problem, follow the steps that are discussed in the following Microsoft Knowledge base article:

315296 How to clean up a damaged COM+ catalog

IIS DCOM components are missing
To determine whether IIS DCOM components are missing, open Component Services, and then verify that the following COM+ packages are in COM+ Applications:
 * IIS In-Process Applications
 * IIS Out-of-Process Pooled Applications
 * IIS Utilities

Resolution
If any one of these COM+ packages are missing, you must re-create the packages. To re-create the packages, follow these steps:  Click Component Services, and then delete the following packages:  IIS In-Process Applications IIS Out-of-Process Pooled Applications IIS Utilities</li></ul>

Note To delete these packages, open the properties of the package, click the Advanced tab, and then click to clear the Disable Deletion check box.</li> At a command prompt, type the following commands, and then press ENTER:

cd %windir%\system32\inetsrv

rundll32 wamreg.dll, CreateIISPackage

Note &quot;CreateIISPackage&quot; is case sensitive and must be typed exactly as shown.</li> Type regsvr32 asptxn.dll, and then press ENTER.

Note This is an additional step that may be necessary. However, the packages are created successfully in step 2.</li> Close and then open Component Services. All three IIS COM+ applications should be re-created.</li> At the command prompt, type IISRESET, and then press ENTER.</li> Type exit, and then close Component Services.</li></ol>

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

309051 How to troubleshoot ASP in IIS 5.0

COM+ service issues
Make sure that the COM+ service is started and running in the Component Services Microsoft Management Console (MMC). If the COM+ service is not running, an error that resembles the following may appear in the System event log:

Event Type: Error

Event Source: DCOM

Event Category: None

Event ID: 10005

Date:

Time:

User: S-1-5-21-2064384965-2096656022-2110791508-7284

Computer:

Description:

DCOM got error &quot;The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. &quot; attempting to start the service COMSysApp with arguments &quot;&quot; in order to run the server:{182C40F0-32E4-11D0-818B-00A0C9231C29}

Resolution
For more information about how to clean up a COM+ catalog if the COM+ catalog becomes damaged, click the following article number to view the article in the Microsoft Knowledge Base:

315296 How to clean up a damaged COM+ catalog

MS DTC service issues
To verify that you are using the correct logon account for the MS DTC service, follow these steps:
 * 1) On the management point server, open Services, and then verify that the MS DTC service (Msdtc.exe) is started.
 * 2) Right-click Distributed Transaction Coordinator, click Properties, and then click the Logon tab.
 * 3) In the This Account box, verify that the correct account is being used for the service account logon.

Note In Microsoft Windows Server 2003, MS DTC runs under the NT AUTHORITY \Network Service account. However, if an older security template is still being applied, the service may be running under the NT AUTHORITY\SYSTEM account.

Resolution
To resolve this problem, remove and then reinstall MS DTC so that the MS DTC service runs under the Network Service account. To remove and then reinstall MS DTC, follow these steps:
 * 1) Exit all open applications.
 * 2) At the command prompt, type msdtc –uninstall, and then press ENTER.
 * 3) Restart the server.
 * 4) At the command prompt, type msdtc –install, and then press ENTER.
 * 5) Open Services, and then verify that the MS DTC service is set to start automatically. Start the service if it is not running.

IIS metabase issues
An error message that resembles the following is logged in the MPMsi.log file:

(UNKNOWN) [ ] CheckIfIISObjectExists( :\SMS_CCM\ccmisapi.dll) returning FALSE

(UNKNOWN) [ ] Ignoring removal of Extension File Record &quot; :\SMS_CCM\ccmisapi.dll&quot; as it does not exist

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

918324 Error message after you try to install a new SMS 2003 management point: &quot;The error code is 80020009&quot;

Resolution
To resolve this problem, install the hotfix that is discussed in the following Microsoft Knowledge Base article:

913441 FIX: The list of extension files that the IisWebService.ListExtensionFiles method returns may be incomplete in IIS 6.0

Task Scheduler error
An error message that resembles the following may be logged in the Mpmsi.log file:

< > Unknown error code: 452765

< > [ ] @@ERR:25006

< > Setup was unable to create the Internet virtual directory CCM_Incoming The error code is 80041313

This error maps to SCHED_E_UNKNOWN_OBJECT_VERSION “The task object version is either unsupported or invalid.”

Resolution
This problem may occur when the Tasks folder contains a corrupted task. (By default, the Tasks folder is C:\Windows\Tasks.) To resolve this problem, locate and then remove the corrupted task. For more information about how to remove a corrupted task, click the following article number to view the article in the Microsoft Knowledge Base:

834853 &quot;The task object version is either unsupported or invalid&quot; error message when you use Schtasks

<div class="references_section">