Knowledge Base

Error message after you try to install a new SMS 2003 management point: "The error code is 80020009"

Article ID: 918324

Article Last Modified on 11/27/2007

APPLIES TO

Microsoft Systems Management Server 2003

SYMPTOMS

After you install a hotfix for a Microsoft Systems Management Server (SMS) 2003 management point, you try to install a new management point or try to perform a site reset. After you do this, an error message that resembles the following is logged in the Mpsetup.log file:

<Date Time> [Time] @@ERR:25006
<Date Time> Setup was unable to create the Internet virtual directory CCM_System The error code is 80020009
<Date Time> MP.MSI exited with return code: 1603
<Date Time> Backing up MPMSI.log to D:\SMS\logs\MPMSI.log.LastError
<Date Time> Fatal MSI Error - MP.MSI could not be installed.

Additionally, an error message that resembles the following is logged in the Mpmsi.log file:

(UNKNOWN) [Time] CheckIfIISObjectExists(D:\SMS_CCM\ccmisapi.dll) returning FALSE
(UNKNOWN) [Time] Ignoring removal of Extension File Record "D:\SMS_CCM\ccmisapi.dll" as it does not exist

CAUSE

This problem may occur if the removal of a previous management point installation did not correctly clean up all the Web service extension file names in the Metabase.xml file.

RESOLUTION

To resolve this problem, install the hotfix that is described 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

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

When the management point uninstall process tries to clean up the metabase, it first calls the ListExtensionFiles method to obtain a list of all the extension files. However, because of a known issue in the ListExtensionFiles method, this function may not list all the files. For example, the Ccmisapi.dll file may not be listed. If the file is not listed, it is not removed. Subsequent attempts to install the management point fail.

The ListExtensionFiles method reads the "WebSvcExtRestrictionList" section in the System32\Inetsrv\Metabase.xml file. However, if the "0,*.exe" and "0,*.dll" entries are not listed as the first two entries, the enumeration stops when one of these entries is encountered.

For example, if the Metabase.xml file appears as follows, some files are not returned:

WebSvcExtRestrictionList="0,C:\WINDOWS\system32\inetsrv\httpodbc.dll,0,HTTPODBC,Internet Data Connector
0,C:\WINDOWS\system32\inetsrv\ssinc.dll,0,SSINC,Server Side Includes
0,C:\WINDOWS\system32\inetsrv\asp.dll,0,ASP,Active Server Pages
1,C:\WINDOWS\system32\bitssrv.dll,0,BITSEXTS,BITS Server Extensions 0,*.exe
1,C:\WINDOWS\system32\inetsrv\httpext.dll,0,WEBDAV,WebDAV 0,*.dll
1,d:\sms_ccm\ccmisapi.dll,0,CCM_ServerFramework,CCM_ServerFramework"

In this example, only the following files are returned by a call to the ListExtensionFiles method:

C:\WINDOWS\system32\inetsrv\ssinc.dll
C:\WINDOWS\system32\inetsrv\asp.dll
C:\WINDOWS\system32\bitssrv.dll

To determine whether you are experiencing this problem, follow these steps:

Open the System32\Inetsrv\Metabase.xml file, and then confirm that one or more of these SMS files are listed in the "WebSvcExtRestrictionList" section:
- Ccmisapi.dll
- Getauth.dll
- Getpolicy.dll
- Smsccrisapi.dll
- Statusisapi.dll
Run the IIsWebService.ListExtensionFiles Visual Basic Script (.vbs) file by using the cscript ListExtensionFiles.vbs command. To run this file, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/ms525008.aspx
Examine the output of files that are listed in the "ListExtensionFiles method" section. If the list does not match the list in the Metabase.xml file, you are experiencing this problem.

Keywords: kbtshoot kbprb kbsmsmp KB918324

Microsoft KB Archive/918324

Contents