We help IT Professionals succeed at work.

Classic ASP is not working under Windows 2008 64 bit with IIS 7.5

Tpaul_10
Tpaul_10 asked
on
Experts,

I have a brand new server (which is running under windows 2008, 64 bit, IIS 7.5) and unable to run
.asp files and keep getting the 500 internal server error. Based on the google search, I have tried or checked the options and couldn't get it worked.

ASP and IsapiModule filters are installed.

Here are the error details.
--------------------------------
Module :IsapiModule
Notification: ExecuteRequestHandler
Handler :AboMapperCustom-2068971
Error Code: 0x8007007e
Requested URL : MYurl
Physical Path : D:\MyPath\myAspPage.asp
Logon Method: Anonymous
Logon User: Anonymous
Failed Request Tracing Log Directory C:\inetpub\logs\FailedReqLogFiles (don't see any files here)


Appreciate your help to get this resolved and would like to increase or award 500 points if I get this resolved by end of today and this is kind of urgent.

Please let me know if you need any further information from me.
Thanks
Comment
Watch Question

Paul MacDonaldDirector, Information Systems
BRONZE EXPERT
Commented:
Try this:
Open a command prompt and navigate to the location of the IIS admin scripts (typically C:\inetpub\AdminScripts).  Then run:
cscript.exe adsutil.vbs set W3SVC/AppPools/Enable32BitAppOnWin64 true
G_H

Commented:
Can you also check the log file for any .asp requests with the 500 error. Post the contents of any line which has 500 near the end.

This is in case your scripts are running, but then failing due to a setting like (but not limited to) parent paths.

GH

Author

Commented:
Thanks for the quick reply Paulmacd.

I have navigated to C:\inetpub\AdminScripts and ran the commnad.

Here is what I got and still getting the 500 error after restarting the machine.
Enable32BitAppOnWin64 : <BOOLEAN> True

Thanks
Paul MacDonaldDirector, Information Systems
BRONZE EXPERT

Commented:
How about running this from a command prompt:
%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

Author

Commented:
GH,

I don't see anything or the folder is empty under C:\inetpub\logs\FailedReqLogFiles
Is there any other place where I need to check for the logfiles? Please let me know

Thanks

Author

Commented:
@Paul I have tried %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

Here is what I am getting

ERROR (Message : Cannot find requested collection element)

Thanks
Paul MacDonaldDirector, Information Systems
BRONZE EXPERT

Commented:
Doesn't matter, I just wanted to see what would happen if you turned off compression. You can do the same thing in the ISM.  Give it a go and see if your symptoms change.  

Author

Commented:
From Server manger, Under Role Services I have checked Dynamic Content Compression chekced (or installed) and still getting the same error.
===========================================================================
Just to let you here are the things I see on the webpage and not sure if it helps.
Most likely causes
The path to the ISAPI Filter is incorrect.
IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
IIS was not able to process configuration for the Web site or application.
The authenticated user does not have permission to use this DLL.


Things you can try
Ensure that the path to the ISAPI DLL is correct.
Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
Check the event logs to see if any additional information was logged.
Verify the permissions for the DLL.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

Thanks

Author

Commented:
Please find the attached log file from C:\inetpub\logs\FailedReqLogFiles

Hoping that this may be helpful to trace the error I am having and trying to fix it for the last 2 days with no luck -:(

Thanks
fr000001.txt
Commented:
Sorry for the delay.

No, I mean the genuine  log files. Have a look in IIS to check the directory being used for the site, and go get one of the log files. You are looking for lines with 500 near the end like this:


2011-10-26 08:43:09 XXX.121.221.212 GET /Mountain_Footprint/ q=Mountain_Footprint|109|800a01a8|Object_required:_'ConnS3' 80 - XXX.96.192.206 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/535.1+(KHTML,+like+Gecko)+Chrome/14.0.835.202+Safari/535.1 500 0 0 171

Open in new window

Commented:
Here is what I did and is woriking. This is due to the pointing out to the right DLL

Here is the link or directions : http://digitallibraryworld.com/?p=6
G_H

Commented:
If you have found the error then great.

I guess if you had looked at the log file as I suggested then you would have found a reference to the file and line number (and one of those cryptic error numbers), which would have pointed you in the right direction.

It would still be worth your while finding the log file, as this is another way you can debug your scripts.

GH

Author

Commented:
ok