Server object, ASP 0178 (0x80070005) The call to Server.CreateObject f

[Dashley]

Hi,

I just set up a new machine. Win 2K pro SP4.I put VStudio on it and all the current SP's etc.. etc.

I register my dll (Written in VB6) and all works fine with the page code below. When I unregister the DLL and unlaod it, restart IIS, I can tell its gone (unloaded) since I get an invalid prog ID when I rerun the ASP page.

I bring up VB6 and run the code for the DLL to debug or test new code the run the very same ASP page and I get the error - Server object, ASP 0178 (0x80070005) (shown in its entirety below). I've cut everything out of the page except for the lines needed to test the page.

I've been doing the same thing for over a year with no problems. I know its a permission issue. The problem is I cant figure out where. I am using a UDL file to SQLServer and have checked its permissions. I know there good since it works when I used the registered DLL.

I've checked the Dll's permissions, MDAC's Dll's. I've used Filemon to look for it.etc.. I've given everybody read write execute in permission and the IUSER accounts. I've gone itno DCOMcnfg and checked the permissions for VbASP Debugging.

Can anyone suggest andother place to check?


Thanks

Dan

<%@ Language=VBScript %>
<%	Option Explicit 
	
dim obj
dim ret

set obj = server.CreateObject("Medatrax.CUser") 'this is line 8

ret = obj.Login (Request("location"), Request("name"))

Response.Write ret

Set obj=nothing	
%>

Server object, ASP 0178 (0x80070005)
The call to Server.CreateObject failed while checking permissions. Access is denied to this object.
/Medatrax_Local/[URL unfurl="true"]wwwroot/1test.asp,[/URL] line 8

 

[DotNetGnat]

try this:

1) On the machine running IIS find the virtual directory and make a note the account (e.g. IUSR) specified under "Directory Security"
2) On the machine open the registry error regedit
3) Use regedit's find feature to find the location of your DLL
4) Find your DLL on disk and access the file's properties
5) Add the account noted from step #1 and give it "read" and "execute" permissions.

OR simply...

right-click on the appropriate component DLL on the server's hard drive, select Properties/Security, and give the "Everyone" account Full Control over it.

-DNG

 

[Dashley]

DNG,

Thanks. I had tried that before and found the permissions for the Dll were ok. My problem wasnt with the DLL. It was working fine when registered. Its when I ran it in VB6 so I could debug it.
Around 2:am last night I found the cure. I found that I was missing a library (windows API(ASCI) that was showing as missing from the VB6 project references list. I also should have set the home directory properties in IIS to run both script and executables (Duhhh). Once I set this up correctly everything started to come to life. I also found a problem with one of my DB user permissions and restored the permissions. Once I had done this the vb library error showed up. It seemed like I ran into a marathon of config problems.

Oh well alls I can say is that it was one of those days

Take Care

dan