C# and COM+   Interface not registered?

Posted on 2004-04-22
Last Modified: 2012-06-27
From a C#  / .NET   /  COM+  perspective, what would it mean if I got a message saying "Interface not registered"

Here is my Class Library source code:

using System;
using System.Runtime.InteropServices;
using System.Xml;
using CDO;
using ADODB;
using System.IO;
using System.Text;
using System.EnterpriseServices;

namespace MyEventSink
      /// <summary>
      /// Summary description for Class1.
      /// </summary>

      public class ExchEventSink: ServicedComponent , IExStoreAsyncEvents
            //public string ClassID = "F92EFC3A-FDD8-4225-B005-13FD3D5D54D1";
            //public string InterfaceId = "704A413F-F8FE-476B-9206-69AB6300D752";
            //public string EventsId = "DCC71BD5-6627-4FBF-BB5A-DB8FEA1EB177";

            public string ClassID = "cf63289d-18d1-43af-ba90-9e41cac93ee6";
            public string InterfaceId = "323733b0-3c0d-47d4-86fa-fd67d651cf81";
            public string EventsId = "3721271c-65f0-441a-91d6-6a86d1c75846";

            public ExchEventSink()


            #region IExStoreAsyncEvents Members

            public void OnSave(IExStoreEventInfo pEventInfo, string bstrURLItem, int lFlags)
                  catch (Exception ex)
                        throw (ex);

            public void OnDelete(IExStoreEventInfo pEventInfo, string bstrURLItem, int lFlags)

                  catch(Exception ex)
                        throw (ex);

            private void Process_mail(string bstrURLItem)
                  CDO.Message      iMessage=new CDO.MessageClass();
                  int i;
                  int aNum;
                  string eName;
                  string fName;
                  ADODB.Stream stm;
                  CDO.IBodyPart iPrt;
                  string sFrom;
                  string sDate;

                        FileStream      fs      =      new      FileStream(@"c:\temp\MyEventSink.log",FileMode.OpenOrCreate);

                        sFrom = iMessage.From;
                        sDate = iMessage.ReceivedTime.ToString();
                        aNum = iMessage.Attachments.Count;

                              fName = iMessage.Attachments[i].FileName;
                              eName = fName.Substring(fName.Length-3,3).ToUpper();
                              if(eName == "TXT")
                                    iPrt = iMessage.Attachments[i];
                                    iPrt.ContentMediaType = "text/plain";
                                    iPrt.Charset = "windows-1250";
                                    stm = iPrt.GetDecodedContentStream();
                                    iPrt =null;
                  catch (Exception ex)
                        throw (ex);


Here is my Assembly Code:

using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;

// General Information about an assembly is controlled through the following
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyTitle("MyEventSink")]
[assembly: AssemblyDescription("My Event Sink")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("")]
[assembly: AssemblyProduct("")]
[assembly: AssemblyCopyright("")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]            

// Version information for an assembly consists of the following four values:
//      Major Version
//      Minor Version
//      Build Number
//      Revision
// You can specify all the values or you can default the Revision and Build Numbers
// by using the '*' as shown below:

[assembly: AssemblyVersion("1.0.*")]
[assembly:  Guid("2a910565-736c-48d3-a9bb-f64afcb70a83")]

// In order to sign your assembly you must specify a key to use. Refer to the
// Microsoft .NET Framework documentation for more information on assembly signing.
// Use the attributes below to control which key is used for signing.
// Notes:
//   (*) If no key is specified, the assembly is not signed.
//   (*) KeyName refers to a key that has been installed in the Crypto Service
//       Provider (CSP) on your machine. KeyFile refers to a file which contains
//       a key.
//   (*) If the KeyFile and the KeyName values are both specified, the
//       following processing occurs:
//       (1) If the KeyName can be found in the CSP, that key is used.
//       (2) If the KeyName does not exist and the KeyFile does exist, the key
//           in the KeyFile is installed into the CSP and used.
//   (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility.
//       When specifying the KeyFile, the location of the KeyFile should be
//       relative to the project output directory which is
//       %Project Directory%\obj\<configuration>. For example, if your KeyFile is
//       located in the project directory, you would specify the AssemblyKeyFile
//       attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]
//   (*) Delay Signing is an advanced option - see the Microsoft .NET Framework
//       documentation for more information on this.
[assembly: AssemblyDelaySign(false)]
[assembly: AssemblyKeyFile("..\\..\\key.snk")]
[assembly: AssemblyKeyName("")]

Question by:Tom Knowlton
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
LVL 23

Accepted Solution

rama_krishna580 earned 500 total points
ID: 10895278

Author Comment

by:Tom Knowlton
ID: 10900750

This is the exact tutorial that brought me to this point in the first place.  :)

Please read my summary of the problem here:

Author Comment

by:Tom Knowlton
ID: 10904683
I stumbled upon the answer I needed.

Turns out RegEvent.vbs is not needed.

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

Go here for details:

All I had to do was right-click on the Component Services COM App....and click START.
Salesforce Made Easy to Use

On-screen guidance at the moment of need enables you & your employees to focus on the core, you can now boost your adoption rates swiftly and simply with one easy tool.


Author Comment

by:Tom Knowlton
ID: 10904783
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.

Author Comment

by:Tom Knowlton
ID: 11119932

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 aslo reommend:

.NET and COM: The Complete Interoperability Guide  ISBN:067232170X

Author Comment

by:Tom Knowlton
ID: 11120264
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.  :)

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes a simple method to resize a control at runtime.  It includes ready-to-use source code and a complete sample demonstration application.  We'll also talk about C# Extension Methods. Introduction In one of my applications…
Summary: Persistence is the capability of an application to store the state of objects and recover it when necessary. This article compares the two common types of serialization in aspects of data access, readability, and runtime cost. A ready-to…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor ( Top Charts is a view in which you can set seve…

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question