IIS 5 & IIS 6
Help! Server object error 'ASP 0177 : 8000ffff'
Last post Feb 16, 2009 08:49 AM by lprete
Aug 22, 2007 03:51 PM|minhau|LINK
I created a COM interop class library that I want to call from classic ASP. The class library is actually a wrapper for a .NET assembly log4net, it has a Guid and ClassInterfaceType.None. I generate a strong name for it using sn -k and I make it a signed
assembly before building it
I put it on a server running windows server 2003. It is placed in a directory where the Internet Guest Account, IUSR_machinename has full control.
In IIS the execute permissions is set to scripts only. The ASP .NET version is 1.1.4322.
I call regasm on it in the c:\windows\microsoft.net\framework\v1.1.4322\regasm
The types are registered correctly, now I created a test web page that does
Set Obj = Server.CreateObject("ClassLibrary1.Class1")
When I hit that web page I get the error
Server object error 'ASP 0177 : 80070002'
so I regasm it using /codebase flag and try again
regasm mylib.dll /codebase
This time when I hit the page I get the error
Server object error 'ASP 0177 : 8000ffff'
I have been able to get it to run before, but after some time it just starts to fail. Any have any ideas?
Aug 23, 2007 09:21 AMemail@example.com|LINK
A quick search of the forums came up with:
Aug 30, 2007 12:39 PM|garrylindsay|LINK
Did you ever resolve this? I am having the sample problem, it worked when I first developed it, then I built the dll again and now it gives the error, its almost as if the registry is messed up?
Aug 30, 2007 12:59 PM|minhau|LINK
I have managed to get it working. Although some steps I did may be omitted to get it to work, here is what I did.
1. I did a regasm /unregister on the dll but it seemed that entries still existed in the registry. So I used regedit and I removed all the entries to the GUID and progID in the registry.
2. I rebuilt the dll using a different progID, strong name key file, and GUID.
3. I copied it onto the machine and did regasm /codebase on it.
4. I added the assembly and the assembly it was dependant upon, the log4net assembly, to the global assembly cache. I did it using the Microsoft .NET Framework Configuration in Administrative Tools. You can also do it using gacutil -i command.
5. I rebooted the computer.
I think the key steps for me to get it working was adding it to the global assembly cache then rebooting the computer. All the errors seemed to have gone away after the reboot. After I rebuilt the dll under a different progID I never went back to the old
Sep 25, 2007 10:15 AM|juanitosan|LINK
Hi guys, I finally solved the problem. It is an issue more or less documented by Microsoft in the following links:
The problem is an automatic update from IE7, specifically 937143. Just uninstall this update and voila!.
Jan 26, 2008 03:54 PM|spiderroll|LINK
Your post sent me to the right direction. For me, it worked for me after I did only steps 1, 2, and 3.
Feb 28, 2008 10:06 AM|juanitosan|LINK
Hi, I found another workaround for this problem because uninstalling KB937143 seems not to be a good idea since it is a security patch:
"Give the IUSR (or whoever your site is running as) read access to HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones - this key might change depending on who your app pool is running as (default is Network Service [aka
Taken from : http://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=294241
It works fine.
Feb 10, 2009 05:25 AMfirstname.lastname@example.org|LINK
Whether it is correct or not. Please verify.
Feb 16, 2009 08:49 AM|lprete|LINK
KB950759 replaces KB945701.