Error Updating Props : -2147221163 Interface not registered

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

New Event Binding created:
Event: onsave;ondelete
Sink:  MyEventSink.ExchEventSink
FullBindingUrl: file://./backofficestorage/

Error Updating Props : -2147221163 Interface not registered

Press any key to continue . . .


Trying to get an Exchange Event Sink working on our server.

Can anyone help me with this error?
Tom KnowltonWeb developerAsked:
Who is Participating?
vascovConnect With a Mentor Commented:
Hi knowlton,

It's a long shot, but have you GACed your assembly ? It might be failing because it can't find your assembly.


glsacConnect With a Mentor Commented:
Tom KnowltonWeb developerAuthor Commented:

You wrote:

Also...this will probably interest you as well...even more as it is c#:


What a is this exact tutorial that I am following......

It has worked fin all the way up to the part where I bind the component to the Exchange Server Store.......hence the error I am getting.
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tom KnowltonWeb developerAuthor Commented:
I have created a web page which explains what I have done so far to troubleshoot this.
Tom KnowltonWeb developerAuthor Commented:
From the web page I posted it should be apparent that I have indeed GAC'ed my Assembly.  :)
Tom KnowltonWeb developerAuthor Commented:
Turns out RegEvent.vbs is not needed.

Exchange Explorer  (found with Exchange 2003 SDK Tools) does the exact same thing.

Go here for details:
Tom KnowltonWeb developerAuthor Commented:
The tutorial at this link:

is very very good......................but it does have some flaws.

1)  You do NOT need to run RegEvent.vbs AT ALL......ignore this suggestion in the tutorial.  Instead, download and install the SDK Tools and run Exchange Explorer instead to register the Event and hook it into the EventSink code.

2)  I recommend using regsvcs /appname:YourAppName <full path to your DLL including extension>      from the command line, instead of using the Component Services GUI to register the COM DLL.  I have to do some further testing to see if the GUI works...but I know for sure the command line route using REGSVCS works well.

3)  After you have registered the COM DLL (your event sink) in Component Services......then go and register the Exchange Store Event using Exchange Explorer.   THEN go back to Component Services....right-click on your App Name and click on START.   This is what actually starts the EventSink (your C# DLL) talking to the Exchange Store.  Until you do this nothing will happen.   This was left out of the tutorial.  A small thing, but an important thing to mention.
Tom KnowltonWeb developerAuthor Commented:

Well, guess what?

I finally had a major breakthrough on this @!#$^% problem that has been driving me crazy for the last few weeks!!!!!!!

It is a very small change.

Apparently the method   MoveFirst(   ) does not work so well with Exchange.

This was the cause of my COMException:   "Interface not registered" error message this entire time.

The solution is to use    Move(1,0)     instead of MoveFirst(  ).

That's it.   Simple.

This answer came courtesy of Tom Rizzo, an author who was kind enough to correspond with me and help me figure-out finally what the problem was.:

Looking for a good book on programming Exchange, Outlook, ADSI and
SharePoint?  Check out

My I also reommend:

.NET and COM: The Complete Interoperability Guide  ISBN:067232170X
Tom KnowltonWeb developerAuthor Commented:
More on the MoveFirst problem I described:;en-us;273791

If you are getting into Event Sinks....I recommend the following tutorial:

Make sure and read the article questions and follow-ups at the bottom!

There are a few caveats.  E-mail me at my Profile e-mail address and we can talk about them.  :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.