Late binding my dll is not currently an option for me, so please do not just reply with "Use Late Binding", or any of the million plus links to MSKB or thread post proclaiming this advice.

This is an application that runs fine on Windows 2000. When running on Windows 2003 for the App server and Windows XP for the Client I am receiving Error 48 when trying to instantiate a dll that is installed on the Client using a proxy exported from the App server.

There are no event log messages, on the client or the server, and this is not likely a permission issue, since I the object can be instantiated late bound.

Thanks,
Joshua

error 48 is about standard dll (like API's, no ActiveX), see:http://msdn2.microsoft.com/en-us/library/2c4wchf4.aspx

so I do not understand how you can instantiate it, either early or late bound. Can you be more specific?

Marco

CreateObject("Foo.Bar") works. Dim Baz As Foo.Bar does not.

I wish when people post about errors they would post the [u]text</u> of the message, rather than just the number . . . *sigh*

My guess, given the limited data so far, would be that you need to add a reference to the item containing Foo.Bar.

CreateObject(...) looks in the registry for the class by name, and finds the executable through the info about it contained therein. Dim <var> As . . . format uses references that the app has specific knowledge of. (As I recall, anyway . . . )

Well... the reference must be there or the code will not compile using the "Dim As" mechanism. But just because the reference is there doesn't mean the dll still exists.

However, as Marco has mentioned, this is the error you get when you are working with a library dll like Kernel32.dll, and not ActiveX dlls.

However - it is not specifically stated, so I am asking directly: Is the dll running in COM+ on the server machine? You state you have exported the proxy, so I assume you have exported the proxy using COM+. Is this correct? If you have done that, I must assume you have installed the proxy into COM+ on your client machine. Is this correct?

When you use "Dim Baz As Foo.Bar" how are you instantiating the object? Set Baz = New Foo.Bar?

When you say CreateObject("Foo.Bar") works, what do you mean by "works". Is it that all the functionality and all the method calls are working when you do this? Do you have methods that allow you to test and prove that the DLL is running on the server machine? Does it work using CreateObject using the COM+ proxy with the code running on the remote server? etc....

You are leaving out a lot of information if you expect anyone to be able to help you out.

Things like... what code is in the line code that causes the error? The "Dim" statement can't cause a runtime error - it isn't a line of code. It is just a declaration.

There could be a number of causes for this error.

Woody Z
http://www.learntoprogramnow.com
How to use a forum to help solve problems

Although it is possible that the dll relies on Windows calls this dll was created in VB.

The dll is installed in a COM+ Package on the Application Server, and a Proxy is being exported from COM+

To the first question, if I recall, still using CreateObject("Foo.Bar"). To the second yes, the client says "Object Created" and I can see the Component spin in COM+ on the App Server.

Sorry, the context in my head often overshadows the typing of my fingers. Sorry my reply took so long. I actually found this post again because I'm getting Error 48 again.

So it appears that you both hit it on the head. The issue was with the MDAC version on the machines. Thank you for your help.

Cool. Glad you found the problem!

Woody Z
http://www.learntoprogramnow.com
How to use a forum to help solve problems