| Event Id | 1047 |
| Source | MSExchangeMU |
| Description | Metabase Update failed to properly initialize its context. It will retry initialization every number seconds until succeeds or shutdown is requested. |
| Event Information | CAUSE: This Error event may be logged for a variety of reasons. The associated symptoms may include the following: 1. Information Store service may not start. 2. Databases may not mount. 3. POP3 service may not start. 4. IMAP4 service may not start. Exchange resources running on a cluster may not come online. This event may also be logged when a domain controller that was running Exchange Server 2003 is demoted to a member server. During this demotion, the ASPNET security account is removed. This prevents the Metabase Update process from initializing. Additionally, this event may also be logged if there are underlying network connectivity and DNS issues, or if there is data that is not valid or unexpected in the Windows registry under the following registry key: HKLM\SOFTWARE\Microsoft\ASP.NET For example, when the .NET Framework 1.1 is installed, the name of the key under ASP.NET should be 1.1.4322.0. If the name of this key is changed, the Metabase Update process can no longer access the correct registry path and this event is logged. Finally, this event message may also be logged if there are permissions problems in the Exchange Server environment. You may notice one or more of the following events in the Application log. These additional events may give you more information about the cause of this error. RESOLUTION: To resolve this error, try one or more of the following: 1. If this event is caused by the demotion of a domain controller running Exchange Server 2003 to a member server, you must reinstall Exchange Server 2003 to resolve this issue. 2. If this event is logged because of a suspected permissions issue, you can run the setup /domainprep command to resolve the issue. 3. If this event is caused by a key name in the registry that is not valid, change the value to 1.1.4322.0. Note: If these user actions do not resolve this issue, turn up diagnostic logging f |
| Reference Links | Microsoft product: Exchange Version: 6.5.7638.0 Event Source: MSExchangeMU Event ID: 1047 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.