Failed to access the metabase, error code is .

Details
Product: Exchange
Event ID: 1009
Source: MSExchangeMU
Version: 6.5.6940.0
Component: Microsoft Exchange Metabase Update
Message: Failed to access the metabase, error code is <error code>.
   
Explanation

The metabase update agent cannot access the Internet Information Services (IIS) metabase. You will receive the following phrase in the Event Description: Failed to access the metabase, error code is [Error code number] (Error text.).

One possible cause is that IIS Admin Service is not started or is disabled. There could also be a problem with IIS, such as a corrupted metabase.bin file. Commonly, this event indicates that the metabase has become corrupt.

Root causes for MSExchangeMU Event ID 1009 are many and are associated with specific error codes. The most common error codes are listed as follows:

  • Cause 1 – Failed to access the metabase, error code is 80004002 (Invalid Signature.).
  • Cause 2 – Failed to access the metabase, error code is 80090006 (Invalid Signature.).
  • Cause 3 – Failed to access the metabase, error code is 80040154 (Class not registered.).
  • Cause 4 – Failed to access the metabase, error code is 8009000f (Object already exists.).
  • Cause 5 – Failed to access the metabase, error code is 80070422 (The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.).
   
User Action

Verify that the IIS Admin Service is running correctly. Specific resolutions associated with the listed causes are as follows:

  • Resolution 1 – Remove the existing installation of the IIS computer that runs Exchange Server. Make sure that the metabase.bin file is gone. If it is not, manually remove it. Reinstall IIS on the computer. Reinstall the same operating system service pack and any operating system hotfixes. Reinstall Exchange Server over its existing installation. (Do NOT uninstall Exchange Server — simply perform a reinstall.) Reinstall any Exchange service packs and hotfixes. Another alternative is to restore the metabase.
  • Resolution 2 – Same as Resolution 1.
  • Resolution 3 – Restore from the metabase from last good online backup. If you do not have a backup, perform the steps in Resolution 1. If you still get the same error, you may need to reinstall the operating system and Exchange server.
  • Resolution 4 – Remove IIS and delete all the files in the MachineKeys directory except the newest one (and not the backups). Restart the computer. Install IIS (by using Add/Remove Programs in Control Panel). For further information, see Microsoft Knowledge Base article PRB: Error Message “0x8009000F = Object Already Exists” 271865.KB.EN-US.
  • Resolution 5 – This error rarely occurs. If you receive this error, follow the steps in Resolution 1.

Related:

Leave a Reply