Microsoft Knowledge Base Email Alertz

You may receive an error message and the installation may stop responding when you try to start the IIS Admin service in IIS

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

You may receive an error message and the installation may stop responding when you try to start the IIS Admin service in IIS

Article ID: 903072 - View products that this article applies to.

On This Page

SYMPTOMS

When you try to start the IIS Admin service in Microsoft Internet Information Services, you may receive an error message that is similar to one of the following:
IIS Admin Service failed with error 126
Error 126: The IIS Admin Service terminated with the following error: the specified module cannot be found.
You may also receive an error message in Event Viewer that is similar to one or more of the following:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Description: The IIS Admin Service service terminated with the following error: The specified module could not be found.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Description: The IIS Admin Service service terminated with service-specific error 2149647636 (0x80210514).
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Description: The server {A9E69610-B80D-11D0-B9B9-00A0C922E750} did not register with DCOM within the required timeout.

CAUSE

This problem may occur if the Msxml3.dll file is not correctly registered.

RESOLUTION

To resolve this problem, you must correctly register the Msxml3.dll file. To register the Msxml3.dll file, click Start, click Run, type regsvr32 Msxml3.dll, and then click OK.

MORE INFORMATION

If you are installing IIS and the installation process stops responding, follow these methods. After each method, check to see if the problem still occurs.

Method 1: Verify the permissions on the MachineKeys folders

The following settings are the default permissions for the MachineKeys folder on Microsoft Windows Server 2003-based computers:
  • Administrators (Full Control): This folder only
  • Everyone (Special): This folder only
To verify the special permissions for the Everyone group, follow these steps:
  1. Right-click the MachineKeys folder, and then click Properties.
  2. Click the Security tab, and then click Advanced.
  3. Click View/Edit.
The special permissions include the following permissions:
  • List Folder/Read Data
  • Read Attributes
  • Read Extended Attributes
  • Create Files/Write Data
  • Create Folders/Append Data
  • Write Attributes
  • Write Extended Attributes
  • Read Permissions
For more information about how to verify the permissions on the MachineKeys folder in Windows 2000 and Windows NT 4.0, click the following article number to view the article in the Microsoft Knowledge Base:
278381 Default permissions for the MachineKeys folders

Method 2: Verify the permissions on the Inetsrv folder

The following settings are the default permissions for the Inetsrv folder on Windows Server 2003-based computers and Windows 2000-based computers:
  • Administrators (Full Control): This folder, subfolders, and files
  • CREATOR OWNERS (Full Control): Subfolders and files only
  • Power Users (Modify): This folder, subfolders, and files
  • SYSTEM (Full Control): This folder, subfolders, and files
  • Users (Read & Execute): This folder, subfolders, and files

Method 3: Delete the IIS Out-of-Process Pooled Applications package and delete all the files in the Inetsrv folder

To delete the IIS Out-of-Process Pooled Applications package and delete all the files in the Inetsrv folder, follow these steps:
  1. Click Start, click Run, type %Systemroot%\system32\com\comexp.msc, and then click OK.
  2. Expand Component Services, expand Computers, expand My Computer, and then expand COM+ Applications.
  3. Right-click IIS Out-of-Process Pooled Applications, and then click Delete.

    Note To delete the IIS Out-of-Process Pooled Applications package, open the IIS Out-of-Process Pooled Applications Properties dialog box, click the Advanced tab, and then click to clear the Disable Deletion check box.
  4. Close Component Services.
  5. Click Start, click Run, type %SystemRoot%\system32\Inetsrv, and then click OK.
  6. On the Edit menu, click Select All, press Delete, and then click Yes.

Method 4: Stop all services that are not required by the operating system

To stop a service, click Start, click Run, type services.msc, right-click the service you want to stop, and then click Stop.

Method 5: Remove IIS and delete the files in the MachineKeys folder

For more information about how to remove IIS and delete the files in the MachineKeys , click the following article number to view the article in the Microsoft Knowledge Base:
271865 PRB: Error message "0x8009000F = Object already exists"

Method 6: Register the Wamreg.dll file

To register the Wamreg.dll file, click Start, click Run, type regsvr32 %systemroot%\system32\inetsrv\wamreg.dll, and then click OK.

Method 7: Reinstall IIS

To remove and then reinstall IIS, use Add/Remove Programs in Control Panel.

Properties

Article ID: 903072 - Last Review: February 8, 2012 - Revision: 6.0
APPLIES TO
  • Microsoft Internet Information Services 6.0
Keywords: 
kbtshoot kbprb KB903072
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User Report As Irrelevant  
Written: 2/17/2007 12:33 PM
This worked flawlessly. After an hour and a half of searching the web reregistering msxml3 did the trick.

Anonymous User Report As Irrelevant  
Written: 10/14/2008 2:28 AM
The solution on registering DLL worked excellently. Great !!!