[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

EXOLEDB Event log errors 114 and 108 on Exchange 2007 server restart

I have a MS Exchange 2007 server on Windows Server 2003 with all the requisite patches.  On restart I get a LOT of paired 108 and 114 Application log errors referencing failed event bindings (It's probably about 80 sets of errors).  Any thoughts on eliminating them?  They're all different binding IDs.

Event Type:      Error
Event Source:      EXOLEDB
Event Category:      Events
Event ID:      114
Date:            10/3/2011
Time:            11:47:23 PM
User:            N/A
Computer:      MAIL
Description:
Microsoft Exchange OLEDB has disabled the event binding due to the problems in the event sink. Binding ID = {99E19428-A342-45CF-910F-4FBFBB8C043A}. You may need to contact the event sink author and get a fixed or updated copy.

0
tolenmay
Asked:
tolenmay
  • 4
1 Solution
 
tolenmayAuthor Commented:
Oops - forgot to put in the 108 error.

Event Type:      Error
Event Source:      EXOLEDB
Event Category:      Events
Event ID:      108
Date:            10/4/2011
Time:            12:10:27 AM
User:            N/A
Computer:      MAIL
Description:
Microsoft Exchange OLEDB was unable to either create an event sink object or get necessary interface(s) from the sink class specified by Application_NET.Application, HRESULT = 0x80004027.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
abhijitmdpCommented:
This issue may occur when the following conditions are true:
    * In the DCOM Configuration utility (Dcomcnfg.exe), the default permissions have been modified. They have been modified in the Default Access Permissions area of the Default Security tab in the DCOM Configuration utility.
    * The system account and the Interactive special group have not been explicitly added. They must be granted Allow Access permissions

To resolve the problem, add the system account and the Interactive special group. Grant them Allow Access permissions. To do this, follow these steps:

   1. Click Start, click Run, type dcomcnfg in the Open box, and then click OK.
   2. Click the Default Security tab, and then click Edit Default under Default Access Permissions.
   3. Click Add to add SYSTEM and INTERACTIVE and to grant them Allow Access permissions.
   4. Click OK.
0
 
tolenmayAuthor Commented:
The answer sounds promising.. I'm just having a bit of trouble following the instructions - I don't work in DCOM much.  When I type dcomcnfg, component services comes up, under which DCOM Config is a folder.  When I click on DCOM Config, the pane on the right shows all the DCOM objects, but no tabs, and nothing called "Default Security".  What am I missing?  This is a Windows 2003 box.
0
 
tolenmayAuthor Commented:
I think I figured it out - looked it up online.  I went into Dcom config, which brought up Component Services.  I drilled down into Computers, right clicked My computer, Properties, COM Security, Access Permissions, Edit Default.  What was already there was Self and System, who both had Allow local access.  I added Interactive (didn't seem to matter if I clicked the local compute or the domain, it brought up the same thing). and gave it Local Access permissions.  

Does that sound right?
0
 
tolenmayAuthor Commented:
Even though I added  INTERACTIVE and gave it local access permissions, I'm still getting the errors. Any idea why?
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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