Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 8206 Source: MSExchangeFBPublish
Unable to prepare message table for polling thread processing on virtual machine <computer name>. The error number is <error number>. Make sure Microsoft Exchange Store is running.
|English: Request a translation of the event description in plain English.|
- Error: 0x80004005 - This event may be logged even if the Microsoft Exchange information store service is started and Exchange Server 2003 appears to be running correctly. See ME930361 for details.
As per Microsoft: "Free/Busy Publishing was unable to get the contents table on the System Attendant mailbox. Usually results when the Information Store goes down". See MSEX2K3DB for additional information about this event.
Christophe Lubrano di Ciccone
Error: 0x80004005. This error was in fact generated due to the autonegotiate port configuration of a switch. The server network card had 100 full duplex and the switch port 100 half duplex. The switch port was changed to 100 full duplex and Autonegotiate disabled and all is workking fine after without any reboot. This event was accompanied with the 8197 MSExchangeFBPublish.
Error: 0x80040111 = MAPI_E_LOGON_FAILED - no additional info
Error: 0x80040115 = "MAPI_E_NETWORK_ERROR". May occur after you start the Exchange 2000 Server information store with new blank databases. See ME252543.
Error: 0x80004005 = "MAPI_E_CALL_FAILED". This error can occur when the information store is offline or if the data store isn't mounted. For example, I received this error during the time I was performing an isinteg check on the private data store.
|Private comment: Subscribers only. See example of private comment|
|Links: ME252543, ME305030, ME930361, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated