Microsoft KB Archive/234429

= How to manually restore the metabase when no proper backup exists or when the MMC does not start =

Article ID: 234429

Article Last Modified on 8/8/2006

-

APPLIES TO


 * Microsoft Internet Information Services 5.0
 * Microsoft Internet Information Server 4.0

-



This article was previously published under Q234429



We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:

http://www.microsoft.com/technet/security/prodtech/IIS.mspx



SUMMARY
To restore the metabase, it is recommended that you use the Restore action in the Microsoft Management Console (MMC). However, if no backup of the metabase was ever created by the MMC, or if the MMC cannot be started because the metabase has been corrupted too badly, you can attempt to manually restore the metabase by using one of the methods described in the "More Information" section.



MORE INFORMATION
Note You should back up the metabase regularly by using the Backup action in the MMC.

IIS 5.0
For more information about Microsoft Internet Information Services (IIS) 5.0, click the following article number to view the article in the Microsoft Knowledge Base:

300672 How to create a metabase backup in IIS 5

If a backup file created by the MMC is available
If the Backup action in the MMC was used to create a backup file ( .md ), but the MMC cannot be opened because the current metabase is corrupted, perform the following steps to manually restore the metabase from the .md  file.  Stop all IIS services and other services that rely on IIS, such as third-party applications or Microsoft Site Server.

Note To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

236166 Using NET STOP and NET START commands to force IIS services to re-read the registry

 Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder. Copy the MMC backup metabase file, .md, which is located in the %SystemRoot%\System32\Inetsrv\Metaback folder, to the %SystemRoot%\System32\Inetsrv folder. Rename it to Metabase.bin. Restart the computer.

If an older copy of the Metabase.bin file exists
If no backup file that was created by the MMC is available, but an older copy of the Metabase.bin file exists elsewhere (typically on a system tape backup), perform the following steps:  Stop all IIS services and other services that rely on IIS, such as third-party applications or Microsoft Site Server.

Note To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

236166 Using NET STOP and NET START commands to force IIS services to re-read the registry

</li> Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.</li> Copy the older copy of the Metabase.bin file to the %SystemRoot%\System32\Inetsrv folder.</li> Restart the computer.</li></ol>

If no MMC backup file or older copy of the Metabase.bin file exists
If no backup file that was created by the MMC is available, and no older copy of the Metabase.bin file exists, a temporary backup of the metabase may still exist.

When the metabase is updated through the MMC or another process, a temporary backup of the metabase may be created. If the update was interrupted (which is possibly the cause of the corruption in the first place), there is a chance that this temporary file may still exist.

This temporary file is named either Metabase.bak or Metabase.bin.bak, and is located in the %SystemRoot%\System32\Inetsrv folder. If this temporary file exists, perform the following steps to attempt to restore the metabase:  Stop all IIS services and other services that rely on IIS, such as third-party applications or Microsoft Site Server.

Note To stop IIS and its dependent services, use the NET STOP IISADMIN /Y command. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

236166 Using NET STOP and NET START commands to force IIS services to re-read the registry

</li> Rename the corrupted metabase file, Metabase.bin, to a new name such as Metabase.bad. The Metabase.bin file is located in the %SystemRoot%\System32\Inetsrv folder.</li> Rename the temporary backup file (Metabase.bak or Metabase.bin.bak) to Metabase.bin.</li> Restart the computer.</li></ol>

If no metabase backup file exists
If no backup files of the metabase are available, the only way to restore IIS functionality is to do the following.

Note All IIS settings that are stored in the metabase will be lost.

IIS 4.0
 Uninstall the Microsoft Windows NT 4.0 Option Pack. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

187870 How to remove and reinstall the Windows NT 4.0 Option Pack

</li> Uninstall Microsoft Internet Explorer.</li> Delete the Metabase.bin file from the %SystemRoot\System32\Inetsrv\ folder.</li> Install Internet Explorer.</li> Install the Windows NT 4.0 Option Pack.</li></ol>

IIS 5.0
Uninstall and then reinstall IIS 5.0.

(c) Microsoft Corporation 2000, All Rights Reserved. Contributions by Kevin Zollman, Microsoft Corporation.

Additional query words: meta base back up registry corruption hose hosed hung hangs freezes frozen Internet Service Manager ISM akz

Keywords: kbhowto kbpending KB234429

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.