Hi all, We have onsave event sink that we have tested on our development environment (single Exchange 2007 computer with all roles) which works good. However, when we try to deploy it on the test environment (multiple servers, event sink installed on the mailboxserver) we have some problems. The following errors appear in the application log: Event Type: Error Event Source: EXOLEDB Event Category: Events Event ID: 108 Date: 2007-12-19 Time: 12:39:13 User: N/A Computer: (removed) Description: Microsoft Exchange OLEDB was unable to either create an event sink object or get necessary interface(s) from the sink class specified by ExOnSaveEventSink.ExOnSave, HRESULT = 0x80004002. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Error Event Source: EXOLEDB Event Category: Events Event ID: 114 Date: 2007-12-19 Time: 12:39:13 User: N/A Computer: (removed) Description: Microsoft Exchange OLEDB has disabled the event binding due to the problems in the event sink. Binding ID = {1FBD2D83-9FEC-413B-9FF3-E123C1476044}. You may need to contact the event sink author and get a fixed or updated copy. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Can anyone explain why these errors appear? I do think I remember there was a warning when we registered the COM+ application using RegSvcs.exe -fc <EventsinkName>.dll. Can't at the moment remember this error, but will try to get it ASAP. Unfortunately I don't have much access to the server, so any suggestions are highly appreciated.
I should mention that some search on the Internet gave me some indication that it could be the exact ADODB library that I use. As I said it works on the dev environment, so I don't understand why though. Should I be using Interop.msado28.dll found in C:\Program Files\Microsoft\Exchange Server\Bin ? -Knut
OK, I have a theory to why the logs came. I've discovered now that I probably used the 32bit version of the RegSvcs.exe tool to register the event sink. This causes an error, but the installation don't fail. I tried it out on the development environment and it looks something like this: Microsoft (R) .NET Framework Services Installation Utility Version 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. Type library exporter warning: Referenced type is defined in managed component, which is imported from a type library that could not be loaded because it was no t registered (type: 'Interop.Exoledb.IExStoreAsyncEvents'; component: 'C:\event sink\Interop.Exoledb.dll'). Installed Assembly: Assembly: C:\event sink\ExOnSaveEventSink.dll Application: ExOnSaveEventSink TypeLib: C:\event sink\ExOnSaveEventSink.tlb I'll have a second try at installing it tomorrow with the 64bit version, hopefully that will fix my problems.
