Click to See Complete Forum and Search --> : Server object, ASP 0177 (0x800401F3) - just installed VS.NET


crmpicco
04-24-2006, 11:23 AM
THis is a code snippet from my Classic ASP File 'nf1_search_db.asp' :

set objdll = server.CreateObject("PiccoDb.SearchFares") <---- THIS LINE
set objxmlReply = server.CreateObject("Microsoft.freethreadedXMLDOM")
Set objxmlReply = objdll.PiccoSearchQuery(objxml)



I get this error on the line above, does anyone know why this would be the case?

Error:


Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string
/v2/asp/net_includes/nf1_search_db.asp, line 207


I installed Visual Studio .NET this morning and now i get this after I registered (regsvr32) a new DLL.

Has installing VS.NET blocked calls to Server.CreateObject?

Thanks,
Picco
:eek:

russell
04-24-2006, 06:20 PM
.net shouldn't interfere with your ability to instantiate objects with createObject().

tried uninstalling the dll and re-registering?

are u doing this locally, or on a remote server?

check the guid of the dll and look for it in the registry.

who wrote the dll? was it recently recompiled? if so, what compatibility method?

crmpicco
04-25-2006, 04:31 AM
I am doing it locally on a Windows XP Professional machine with SP2.

The DLL is a custom .dll. It is not third party.

When you say 'uninstall' the .dll do you mean delete the component in the 'Component Services' and add a new one? If so, i already tried that.

When i installed .NET framework it did give me a pop-up window saying something about 'if i was to run a development environment then i would need to remove something'. But, stupidly, i just clicked continue and it installed OK!

Yes, it was compiled locally on my machine.

Thanks for your reply.

Any more ideas?

Picco

russell
04-25-2006, 01:22 PM
If you registered with regsvr32 then you need to un-register and delete the dll file. look in the registry for potential multiple versions -- particularly if you've compiled several times -- and delete the registry entries for it. compiling automatically registers on local machine.

if you registered with com+ explorer, then shut down the application and delete the component from the application in the com+ mmc.

are u trying to instantiate from asp or .net?

are u running .net framework on local web server?

try recompile and see if it works. should register itself. if not (and look in the registry using regedit to see) try regsvr32 or even better create com+ application for it.

crmpicco
04-26-2006, 12:35 PM
I am unsure why you are saying to DELETE the .dll?

Are you saying compiling it means i dont have to do a 'regsvr32'?

I am trying to instaniate from Classic ASP (.asp file)

I have .NET Framework installed.

russell
04-26-2006, 02:43 PM
you want to make sure the registry entry is correct and clean. often times when you compile several times and/or register several versions, the registry points to the wrong version. you don't want any version in the registry except for the latest. if the dll was compiled on the same machine that the web server is running on, then it is highly likely that the registry entry is wrong. when i say uninstall, i mean regsvr32 -u dllName.dll. Have you recompiled since installing the framework? what compatibility mode if you did. It is often best to purposely break binary compatibility, even if the interface doesn't change...

crmpicco
04-27-2006, 05:10 AM
<%

response.write "TEST"

Set nl=Server.CreateObject("MSWC.NextLink")

%>

I have this file 'testSer.asp' inside my wwwroot - that is all thats in it. It gives me this error;


Error Type:
Server object, ASP 0177 (0x800401F3)
Invalid class string
/testSer.asp, line 5


I have re-installed IIS and unistalled .NET framework??