You may need to make sure that component got registered properly and that it is located where it is supposed to be located. Also make
sure there are not multiple versions on the machine. I have seen some instances where if the DLL is supposed to be in the Application
directory but was actually installed in the System32 folder that it breaks it. I cannot recall however if that only occured if Early or Late
binding was involved.
Scot Rose, MCSD
Microsoft Visual Basic Developer Support
Email : XXXX@XXXXX.COM <Remove word online. from address>
This posting is provided S IS with no warranties, and confers no rights.
>>From: "Z-man"<< XXXX@XXXXX.COM >>
>>Subject: CreateObject and com+
>>Date: Tue, 3 Feb 2004 17:34:03 -0500
>>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>>Message-ID:<< XXXX@XXXXX.COM >>
>>Xref: cpmsftngxa07.phx.gbl microsoft.public.vb.database.ado:94057
>>I installed this app on more then 20 win2k servers and everything was just
>>fine on all of them.
>>Now, there is this one server that reports the "Error loading dll" when
>>application tries to create object from com+ component.
>>This happens only on this one server. There is obviously something different
>>on this one but they all have win2k sp3 installed.
>>This happens on that one server only if I use early binding and works fine
>>for late binding.
>>If I do:
>> Dim objConnStrings As util_Connections.ConnStrings
>> Set objConnStrings = CreateObject("util_Connections.ConnStrings") - here
>>it bombs out
>>but if I do:
>> Dim objConnStrings As object
>> Set objConnStrings = CreateObject("util_Connections.ConnStrings")
>>it works well.
>>This server seems to be workin OK for everything else, and I don't want to
>>do fresh install of operating system on it (I'm sure that would solve the
>>problem). I know something is wrong with that server, it is not an
>>Where to look for an error? It looks some system service does not work well,
>>or some dll is not registered properly.