IIS 7“ Server.CreateObject失败”

Question

I've installed IIS7 on my workstation and enabled IIS6 compatibility so I can test classic asp pages (for some old projects here at work).

Some pages work, but others don't.

I receive:

Serverobject error 'ASP 0177 : 800401f3'

Server.CreateObject failed

/master.central.be/master_connection.asp, line 55

800401f3

On that line i've got:

Set dicTalenLabels = Server.CreateObject("Scripting.Dictionary")

Anybody got some ideas what todo to fix this?

Edit:

As suggested by Michael Pryor, i've ran a vbscript with similar code and it was succesful. So it probably has something todo with permissions. Currently trying to figure out which files exactly...

Do I need to add IUSR to scrrun.dll? When trying, I do not have permission, although i'm a adminstrator.

Answer 1

Edited: He's running 32 bit vista, so it's definitely not a 64 bit issues.

Make a test.vbs file and put this in it

Dim o: Set o = CreateObject("Scripting.Dictionary")

Then run it like so

cscript.exe test.vbs

Does it give you the same error?

If it does, then the regsvr32 is failing or something is wrong with the registry keys it would normally put in the registry.

If it doesn't fail, it's likely that the user you have running your asp page (by default it is IUSR_machinename) doesn't have permissions on either ther registry keys it needs, or the actual .dll

Answer 2

0x800401f3 means that the "Scripting.Dictionary" is incorrect or not found. The Scripting.FileSystemObject is provided by the same dll file, and I know that some hosts have disabled this by unregistering the dll file, which would also disable the Dictionary object. Could you check if the Scripting.FileSystemObject works?

Both objects are provided by Windows\\System32\\scrrun.dll (or Windows\\SysWOW64\\scrrun.dll if you're executing 32bit on 64bit host). Check the permissions on this file, and verify what privileges your asp script executes as.

Answer 3

I've found that calls to system objects such as

set rs = server.createobject("adodb.recordset") 

and

set fs = server.createobject("scripting.filesystemobject");

sometimes fail after running fine for weeks on a production server. It's not a great solution, but manually recycling the app pool fixes it. Also, setting the app pool to recycle every few hours is a way to keep it fresh. Just make sure that you don't accidentally log everyone off (if using session for credentials).

It could be that the developer forgot to 'close' and 'set to nothing' the objects. Any objects you create using 'set' need to be allowed to dispose by setting them to nothing after use.

set rs = server.createobject("adodb.recordset")
rs.open sql, db, 1, 3       ' adOpenKeyset, adLockOptimistic
' some process here
rs.close
set rs = nothing

Answer 4

Take a look at:

• Tips for Classic ASP developers on IIS7
• More Tips and Troubleshooting Help for Classic ASP Developers

Both the links are from Bill Staples' blog, he's one of the head honchos on the IIS side of things and the tips in the first link sorted me out when I was trying to get Classic ASP up and running.