Class Not Registered Crash

[jbeerhalter]

I'm writing a C# application using the Desktop API, and whenever the Constructor for my form is called, I get a "Class Not Registered" exception. This happens only on certain computers, and not others, but I can't figure out what the difference is.

The exception gets thrown on the call to the AxDBCCTRLLib.AxDataManager's EndInit method that happens at the end of InitializeComponent method in the constructor.

Has anyone ever seen this before?

[TritonSystems]

Addedum,

We are creating a simple C# WinForm application right now that reproduces this issue we are having on different computer to make it easier to reproduce.

Again, on our "Development" computers this stuff works fine, but we have visual Studio installed so I dont think that is a good gauge.

I guess it would help if there was a list of files that we had to make sure are present for eSginal Desktop API to work properly.

The computer we are testing on that has the issue is a brand new blank windows XP installation with only esginal Installed on it. no MS office no toher apps that dont come with the OS.

I looked on the support site but could not find a FAQ I can click on to se a list of files the DESKTOP API requires to be present in the run directory. Is there anywhere we can look on the site to get this list?

My assumption is the that the desktop api is a ATL com ActiveX control is that correct?

[TGafford]

Hello jbeerhalter and TritonSystems,

I've read your posts and I believe you are talking about two different APIs.

~~~~~~

jbeerhalter,

You mention the Desktop API, but the object you identify with the problem is from the eSignal Control API:

AxDBCCTRLLib.AxDataManager

There is no Data Manager object, per se, in the eSignal Desktop API.

Please submit all questions regarding the eSignal Control API to [email protected]. This forum deals specifically with the eSignal Desktop API.

In this scenario, it sounds as if the DbcCtrl.dll has not been registered. Please ensure that you register this dll.


~~~~~~~

TritonSystems,

You mention that you are developing an application in C# that uses the eSignal Desktop API. I have written a small test sample that does nothing more than instantiate the eSignal object (IESignal.Hooks) and I too have found that it works in my Visual Studio environment, but failed on another system without the Visual Studio environment and a freshly installed eSignal application. I should also mention that this machine does have the .NET framework.

What I have found is that I had to launch the eSignal application at least once prior to launching the C# application. The reason why this is required is because eSignal registers itself and the eSignal Desktop API. Without this registration, the C# application doesn't have a reference point for the IESignal.Hooks object.

If you have launched eSignal on this machine, then you might want to ensure that the .NET framework is also installed on the machine. Without the .NET framework and a registered eSignal application, your C# application won't work.

If you are still having difficulty, please let us know.

~~~~~~~~

I hope this helps you both. If not, please let us know.

[TritonSystems]

That solved the problem. Apparently we are using the control API, and we needed to register the DbcCtrl.dll.