Member Avatar for azapovjednik

Hello all,

I hope you can help me..
I got one assignment: to modify the existing website made of .asp pages. So, I got the working folder, with all the subfolders and files that make one website....
now, in order to start working on it, I need to get it running locally on my PC... how do I do that? I went to windows features and checked the ASP option... still I cannot run the pages... can anyone help me?

I put that folder inside of wwwroot folder and I run http://localhost/demo/default.asp
and I get:

An error occurred on the server when processing the URL. Please contact the system administrator.

If you are the system administrator please click here to find out more about this error.

I have a Win7 64bit operating system... please help!

  • 1 Contributor
  • 1 Reply
  • 490 Views
  • 10 Minutes Discussion Span
  • Latest Post Latest Post by azapovjednik

Dani AI

Generated

A compact, practical checklist to get Classic ASP running under IIS on a modern Windows PC — expands on 's troubleshooting and covers the usual hidden blockers.

Ensure IIS has the right role services enabled (turn Windows features on/off): under Internet Information Services -> World Wide Web Services -> Application Development Features enable ASP, ISAPI Extensions and ISAPI Filters; also enable Static Content and Default Document. Create a site or virtual directory in IIS Manager that points to your project folder and confirm default.asp is in the Default Documents list.

If the site uses old database drivers (Jet, older ODBC) there is often a 32/64-bit mismatch. Two options: set the site’s Application Pool -> Advanced Settings -> Enable 32-Bit Applications = True, or install the matching 64-bit database/ACE drivers. Note: installing 64-bit ACE can conflict with a 32-bit Office install, so the 32-bit pool is usually the safest local fix.

File and identity permissions are common causes of generic 500 errors. Give the site folder read (and write if needed) permissions to IIS_IUSRS or to IIS AppPool\YourAppPool (use Select Users and type the app pool name). To see the real problem instead of the generic message, enable detailed errors: site -> ASP -> Debugging Properties -> Send Errors To Browser = True, and/or enable Detailed Error Pages and check Event Viewer / Failed Request Tracing.

Quick sanity test (drop this as default.asp to verify the engine runs):

<%
Response.Write("Classic ASP is running: " & Now())
%>

If that prints, work through the checklist above (handlers, permissions, 32/64 drivers).

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.