Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1844
  • Last Modified:

MSX 2003: EXOLEDB Event ID 112

Event Type:      Error
Event Source:      EXOLEDB
Event Category:      Events
Event ID:      112
Date:            8/10/2007
Time:            2:30:30 PM
User:            N/A
Computer:      MSX-POPPERS
Description:
Microsoft Exchange OLEDB was unable to register OnSyncSave event for Schema propagation on MDB startup HRESULT = 0x8000ffff.

For more information, click http://www.microsoft.com/contentredirect.asp.
0
howart
Asked:
howart
  • 3
1 Solution
 
patelbg2001Commented:
checkout comments from other techs who had this error
http://www.eventid.net/display.asp?eventid=112&eventno=3886&source=EXOLEDB&phase=1

cheers
B
0
 
mass2612Commented:
Hi,

I would consider calling MS Product Support about this one but has anything changed recently? Is everything mounted and working ok? I also can't find any MS info but check these but please consider carefully before doing anything.

http://forums.msexchange.org/m_1800403695/mpage_1/key_/tm.htm#1800403695
http://forums.msexchange.org/m_190069700/mpage_1/key_/tm.htm#1800418768
0
 
patelbg2001Commented:
extract from the link above

Reported error codes:
- 0x8000ffff = "Catastrophic failure error"
From a newsgroup post: "In ESM, check to see if you see two "schemaroot" system folders. To check this, right click "Public Folders" and click "View System Folders". You can safely delete the older one. This should correct the EXOLEDB event."
From a newsgroup post: "This error can get logged when the exoledb interface tries to make a call
to the store but the databases are dismounted (as will usually happen at startup). You should then see informational events for your stores mounting and no more of the 112s. If this is what you are seeing you can ignore the errors. If you, however, continue to see the events while the dbs are
mounted then you have a problem that will require further investigation."

- 0x80040e19 = "Bind failed"
From a newsgroup post: "On the exchange CD, support/utils/i386, copy the smtpreinstall.exe to the EXCHSRVR/BIN and run it."  
0
 
howartAuthor Commented:
yes I only see it after a reboot
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now