Managed OnSave Event Sink Errors Exchange 2k7 and x64

Managed OnSave Event Sink Errors Exchange 2k7 and x64

Post by Don » Sat, 10 Feb 2007 22:45:57


Getting errors after following the MSDN article on using VB.NET (and VS2005)
for "Implementing a Managed OnSave Event Sink" for Exchange Server 2007. Not
sure, but part of the problem may be that it's the 64-bit version of
Exchange 2007 installed on Windows Server 2003 Enterprise x64, while the
Exchange 2007 SDK samples seem mostly geared toward 32-bit. Even at that, I
was able to build the TLB and install it into COM+ Component Services, then
use Exchange Explorer to register the event in a Public Folder. The event
fired when I saved a message to the Folder, but the following two errors
were logged. Permissions seem to be okay in Component Services, DCOM Config,
and on the Folder. I even tried installing VS2005 on the Server, but no
change in results. I also made sure that I followed the steps in the
prerequisite article "Building Managed Event Sink DLLs". Has anyone been
able to get the OnSave example to work on an all-64-bit setup?


Event Type: Error
Event Source: EXOLEDB
Event Category: Events
Event ID: 108
Date: 2/8/2007
Time: 7:46:21 AM
User: N/A
Computer: ENGNT3
Description:
Microsoft Exchange OLEDB was unable to either create
an event sink object or get necessary interface(s)
from the sink class specified by
SampleEvtSinkVB.AsyncEvents, HRESULT = 0x80004002.

Event Type: Error
Event Source: EXOLEDB
Event Category: Events
Event ID: 114
Date: 2/8/2007
Time: 7:46:21 AM
User: N/A
Computer: ENGNT3
Description:
Microsoft Exchange OLEDB has disabled the event binding
due to the problems in the event sink.
Binding ID = {D180271E-0F75-48AD-A402-FDDE9156398E}.
You may need to contact the event sink author and get a
fixed or updated copy.
 
 
 

1. Managed OnSave Event Sink Errors on x64

2. Now Working - Managed OnSave Event Sink Errors on x64


Finally got the MSDN "Implementing a Managed OnSave Event Sink" working for
Exchange Server 2007 x64 on Windows Server 2003 Enerprise x64 Edition. Could
be because of one or all of the following reasons (Note: these items were
just the result of my own tests, so may or may not work for you):

1. clean up some of the items in the VB.NET code: change "Imports
ExevtsnkLib = SignedExevtsnk" to "Imports ExevtsnkLib = Interop.Exevtsnk",
and avoid warnings by setting the objects = Nothing when Dim'ing rec and
conn.

2. For Component Services, use the "Install new component(s)" button instead
of "Import component(s)". This will permit you to review the interfaces and
methods to make sure you've got IExStoreAsyncEvents on the list.

3. For Component Services select the DLL file, not the TLB file, when
installing the component. Using the TLB file appears to work, but the
Exchange Explorer Registration Wizard may believe that your component is not
properly registered. It also seems that in one of my attempts, using the TLB
file resulted in IExStoreAsyncEvents missing from the component's list of
interfaces.

4. COM Security: For Default Access and Default Launch and Activation: Be
sure that the list includes SYSTEM, INTERACTIVE, and the "run under" account
you selected on the Identity Tab of the Component Properties.

3. Running Exchange MAnaged Events sinks without Visual Studio Instal

4. Running Exchange MAnaged Events sinks without Visual Studio In

5. Managed Exchange Event Sinks: COM Registration

6. Managed Exchange Event Sink broken by DST CDO Patch

7. Managed Event Sink on Exchange 2003

8. Cannot change email header with vbscript onsave event sink.

9. Followup - ADODB Reference for the OnSave Event Sink

10. OnSave Store Event Sink: Strange lFlags value

11. Updating fields through OnSave event sink

12. Event Sink OnSave Doesn't Fire for Each Message

13. Managed event source, unmanaged event sink

14. Protocol Event Sink Issue Using Manged .NET event sink.

15. Categorizer event sink / routing event sink