Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 111 Source: EXOLEDB
Microsoft Exchange OLEDB was unable to do Schema propagation on MDB startup HRESULT = <value>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is an HRESULT?
Re-generate the Public Folder "schema-root". Open Exchange System Manager and expand folders. Right-click Public Folders -> View system folders. Right-click the schema-root folder and rename it. Restart MS Exchange System Attendant, Exchange will create a new (working) schema-root folder.
As per Microsoft: "This event is caused by a failure to copy schema files from the Exchsrvr\Schema directory to the non_ipm_subtree\schema folder". See MSEX2K3DB for more details.
From a newsgroup post: "This event is caused by a failure to copy schema files from the Exchsrvr\Schema directory to the non_ipm_subtree\schema folder.
Make sure the Exchsrvr\Schema directory is available, and verify that the non_ipm_subtree\schema folder has been created.
Restart the Microsoft Exchange Information Store service to attempt to populate the schema again".
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated