Link to home
Start Free TrialLog in
Avatar of kschletter
kschletter

asked on

ASP pages not working in IIS 6 - "Active Server pages" enabled in Web Extensions

I am having an issue with a web server.  The server has IIS6 installed.  Active Server pages (*.asp) only run when they are in the \Inetpub\wwwroot directory.  Once they are out of that directory, they will not run.  I have checked to make sure directory level security is good (compared to \InetPub\WWWRoot to where they need to be...).  I strongly suspect the server (Win 2k3 Server, SP2) has some flaky security customizations.  I have examined the various service accounts for IIS and assured that security is set with them properly as well.  The specific error message in the IIS Logs is:

2007-12-13 01:59:27 W3SVC1 127.0.0.1 GET /hfm/Default.asp |2|ASP_0224|Cannot_load_TypeLib 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 500 0 0

The key part being "ASP_0224|Cannot_load_TypeLib"

Tried using a very (very) basic ASP - it only has one line in it - a word of text.  Runs beautifully in \Inetput\WWWroot.

Any thoughts / Suggestions?
ASKER CERTIFIED SOLUTION
Avatar of Sam Panwar
Sam Panwar
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of kschletter
kschletter

ASKER

Have now narrowed the issue down to Global.ASA.

Active Server Pages error 'ASP 0224'
Cannot load TypeLib
/LM/W3svc/1/Root/HFM/global.asa, line 2
Cannot load Type Library specified in the METADATA tag.

Have isolated this to a DLL, by removing line 2....    Now to find out why something that works at hundreds of locations fails on this one server...
Hi,

Please recompiled the application or regiter .dll fils which you are using .

You can also upload your all .dll in \bin folder.(bin folder create in your wwwroot folder)


These ideas were right on-track.  Ultimately, the "killer problem" was that there were DLLs in different paths (aside from the web files).  These other folder structures also needed the permissions set.  Typically, this is done by the install EXE, but this site's IIS was very locked down and the installer could not set the permissions.

Thanks for the assistance!