Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1005 Source: MSExchangeIS Private
|Source: MSExchangeIS Private|
Unable to start the Microsoft Exchange Information Store. Error <error>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Information Store service?
- Error: 0x3f4 - After you restore an offline backup of the information store database from a computer that is running Microsoft Windows NT 4.0 and Exchange Server 5.5 to a Microsoft Windows 2000 and Exchange Server 5.5 cluster, if you run the isinteg -patch command, it seems that the command completes successfully. However, when you start the information store, you may receive this event. See ME280770 to find out how to solve this problem.
- Error: 1011 - As per Microsoft: "This is because a new version of Mdbrest.dll was provided with SP2". See ME154032 for a workaround on this problem.
- Error: 0x7f - You may see this event while you attempt to install the Microsoft Exchange Server 5.5 from Microsoft Small Business Server (SBS) 4.5 on an SBS 2000 installation for Exchange Disaster Recovery purposes, or when it is necessary to recover a user's mailbox from an Exchange 5.5 Information Store. See ME294881 for more information about this issue.
See "EventID 1005 from source MSExchangeIS" for additional information on this event.
- Error: 0x451 - This happens if you restore a Store.exe file earlier than version 5.5.2651.32 after the information store databases have already been upgraded to version 2.45, or you restore a Store.exe file earlier than version 5.5.2652.68 after the information store databases have already been upgraded to version 2.46. See ME244976 to resolve this problem.
- Error: 0x4fc - According to Microsoft this issue can occur when you reinstall Exchange Server if you use the display name instead of the directory name that is used during a clean installation of Exchange Server. This issue can also occur if you use a different organization or site name instead of the names that were used in the original installation of Exchange Server. See ME231439 and ME264437 for more information about this event.
|Private comment: Subscribers only. See example of private comment|
|Links: ME154032, ME231439, ME244976, ME264437, ME280770, ME294881, EventID 1005 from source MSExchangeIS|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated