Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using COM in .NET

Status
Not open for further replies.

jasonmarsh

Programmer
Aug 31, 2005
5
US
I've never had a problem in the past accessing COM within .NET but I am running into a vague (potentially unrelated) issue.

I'm attempting use DataJunction 7.5 from within C#.

I've made a reference to the DJEngine 7.5 Components Type Library within the Solution Explorer.

I try to create and instantiate the engine using the following syntax:

DJEC.Engine eng = new DJEC.Engine();

When I run the test program, I receive the following error.

Creating an instance of the COM component with CLSID {E2ED7231-D342-11D3-BC59-0090279AB966} from the IClassFactory failed due to the following error: 80004005.

Can anyone explain how I can get around this issue?

Thank you in advance ~ J
 
Googling that error, I found that it means that

Error 80004005 is a ADO/ODBC error. The error 80004005 indicates that you does not have appropriate permissions to make some work or the data you want to get cannot be available for some reason. If you cannot connect, check the user account you connected under. If you work through IIS, check the authentication properties.


This also has some discussion on the issue

Much of what I found dealt with classic ASP, but since you are trying to use a COM component, this doesn't seem out of the ordinary. Additionally, the data portion seems consistent since you are using DataJunction.

----------------------------------------

TWljcm8kb2Z0J3MgIzEgRmFuIQ==
 
Yeah, I googled the same thing.

I don't know what connection it would be referring to. At this point I am not making any connections to any databases or using any sort of authentication. The code above is it, there is nothing more. That would be the very thing needed to start things off and it fails.

I got the line of code from the sample code included. It was written for VB. So, to humor myself, I tried the example in VB and it worked fine. So, that makes me believe that it is some .NET setting... that or some inability of .NET to talk to this particular COM Object.

Thanks ~ J
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top