Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1009 Source: MSExchangeMU

Source
Level
Description
Failed to access the metabase, error code is <error code> (<error description).
Comments
 
I had the same problem after consolidation of the Exchange Server 2007 to VMware. The server is getting two new NIC's. The nslookup worked fine. The solution was to dedicate the internal and external DNS setting to the new vNIC in Server-Hub Transport-"servername" properties. This solved my problem.
Error code 80090006 - According to ME831393 this issue may occur if there is corruption of the Microsoft Internet Information Services (IIS) metabase on the Exchange 2000 Server computer. To resolve this issue, restore the Metabase.bin file from backup or reinstall IIS and Exchange. See the article for more details.
Error code 0x80090006 - IIS admin service would not start, and as a result a whole host of services (W3SVC, SMTP, Exchange services etc) would not start. IIS Admin threw the error 2146893818, which is also 0x80090006. I went through the whole realm of corrupt metabase issues with no success. By the way, for Windows 2003, the file is now metabase.xml and mbschema.xml, and you can find backups of these files in the history folder under %windir%\system32\inetsrv. That being said, my problem was unknowingly self-inflicted. I had recovered this server earlier in the day due to cascading drive failures, and during the recovery, based on another tech note, had moved the machine keys (%allusersprofile%\application data\microsoft\crypto\rsa) information. Apparently if you remove/replace the machine keys files, particularly the one starting c2419, IIS can no longer decrypt portions of the metabase. Before you follow the advice to reinstall IIS and Exchange, try restoring this c2419 file and see if your problem clears up.
Error code 80070570 - In our case, the "metabase.bin" file was corrupted. Running "chkdsk c: /f" forced the file to be fixed. If this had not worked, we would have tried to restore a copy of it from the metaback directory.
Error code 80004002 ="No such interface supported" - If this error occurs when you attempt to start Exchange System Attendant in Exchange 2000 Server, see ME312430 to fix the problem.

As per Microsoft: "One possible cause is that IISAdmin is not started or is disabled. There may also be some other problem with Internet Information Services (IIS), such as a corrupted metabase.bin file. Commonly, this event indicates that the metabase has become corrupt". See MSEX2K3DB for additional information about this event.


Error code 80004002 - If this error occurs when you attempt to start Exchange System Attendant in Exchange 2000 Server, see ME312430 to fix the problem.

As per Microsoft: "One possible cause is that IISAdmin is not started or is disabled. There may also be some other problem with Internet Information Services (IIS), such as a corrupted metabase.bin file. Commonly, this event indicates that the metabase has become corrupt". See MSEX2K3DB for additional information about this event.
Error code 80070005 = "Access denied" - For a generic description of these types of errors, see Error code 5.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...