More Tips and Troubleshooting Help for Classic ASP Developers

Back in May of 2007 I posted a tips for Classic ASP developers post which has since received more than 50 comments and 85,000 views.  Robert McMurray just posted a set of fabulous tutorials for Classic ASP developers.  If you’re out there and having issues with Classic ASP and IIS7 and need some help, you’re not alone!  Read these articles to get help:


Classic ASP is not installed by default on IIS 7.0 and IIS 7.5

In IIS 7.0 and 7.5, the classic version of ASP is not installed by default. Because of this, you might see HTTP 404 errors when you try to browse to an ASP page on your server, or you might see the source code for your ASP page displayed in your browser window ...


Using Classic ASP with Microsoft Access Databases on IIS 7.0 and IIS 7.5

Note: Microsoft Access databases have been popular for many years with developers who use Active Server Pages (ASP) for small-scale applications, but Microsoft Access databases are not designed for scalability, therefore Access databases should only be used ...


Classic ASP script error messages are no longer shown in a Web browser by default

In earlier versions of IIS, error messages from classic ASP scripts were sent to a Web browser, by default. Because these error messages might reveal sensitive information to malicious users, IIS 7.0 disables this feature by default. When your classic ASP ...


Using Failed Request Tracing to troubleshoot Classic ASP errors

One of the great troubleshooting features that is built in to IIS 7.0 is Failed Request Tracing, which lets you configure tracing rules on your server that will create detailed troubleshooting log files for custom failure conditions that you define. For example ...


Classic ASP parent paths are disabled by default

Classic ASP Parent Paths let developers use relative addresses that contain ".." in the paths to files or folders. For example, the following code excerpt illustrates an ASP page that maps a parent path: % Response.Write Server.MapPath("../example.asp")%> ...


APPL_PHYSICAL_PATH Server Variable on Windows Vista RTM

The original release of IIS 7.0 that shipped with Windows Vista returned a different value for the APPL_PHYSICAL_PATH server variable than that which was returned by previous


  • our server is migrated to (windows 2008/sql2008/iis7) it throws error error '80040e4d' while connecting database, i enabled Failed Request Tracing.
    The error log as below

    App Pool DefaultAppPool
    Authentication anonymous
    User from token NT AUTHORITY\IUSR
    Activity ID {00000000-0000-0000-3100-0080000000F2}

    Site 1
    Process 4652
    Failure Reason STATUS_CODE
    Trigger Status 500
    Final Status 500
    Time Taken 47 msec


    LineNumber 24
    ErrorCode 80040e4d


    ModuleName IsapiModule
    Notification 128
    HttpStatus 500
    HttpReason Internal Server Error
    HttpSubStatus 0
    ErrorCode 0
    ErrorCode The operation completed successfully. (0x0)

    and my database connection classic ASP code is as below

    set rsUSERSESSIONEXISTS = Server.CreateObject("ADODB.Recordset")
    rsUSERSESSIONEXISTS.ActiveConnection = "Driver={SQL Server};Server=" & Request.ServerVariables("LOCAL_ADDR") & ";Database=e2mdev"
    rsUSERSESSIONEXISTS.Source = "SELECT * FROM userinfo_userinfo"
    rsUSERSESSIONEXISTS.CursorType = 0
    rsUSERSESSIONEXISTS.CursorLocation = 2
    please help me

  • This error 80040e4d means that the database refused the connection due to ACCESS DENIED. So the actual user tring to connect to the database, does not have permissions to do so. In this case it looks like the user is NT AUTHORITY\IUSR for the thread making the call, and it doesn't look like a username and password is passed in to the connection string. So unless the database e2mdev allows everyone and Anonymous access that call will fail. I would doublecheck the security on the e2mdev database, and then make sure you are connecting as someone with access.

Comments have been disabled for this content.