Classic ASP code is not working in IIS 6.0. [Answered]RSS

3 replies

Last post May 24, 2012 10:30 PM by sonic go - msft

  • Classic ASP code is not working in IIS 6.0.

    May 18, 2012 05:00 AM|kalscorpio|LINK

    Hi,

    We have  Classic ASP application which is used to work fine in IIS 5.0 and Operating System is windows 2000.

    We migrated the ASP code to IIS 6.0 and Operating System is windows 2003. Server team i have done all the settings and application is running .

    We are facing one generic error

    Error Desc:Active Server Pages error 'ASP 0115' Unexpected error A trappable error (E06D7363) occurred in an external object. The script cannot continue running".

    we have  gone through so many blogs and we done IIS settings still same error is coming.

    We have gone through the below microsoft link

    http://support.microsoft.com/default.aspx/kb/194190

    Based on the link we have added service account to admin group in that server after we have restarted IIS mutiple times and server reboot is done.still same issue we are getting.

    Next link

    http://support.ipswitch.com/kb/wp-20080815-sp01.htm

    Based on the above link we have followed that steps but still no luck.

     

    Can any one help uson this urgent issue ,any more  IIS settings still we need to do.

    My Email : kbhairraju@csc.com

    Mobile No:+919985510022.

    Thanks,

    kalyan

     


     


     

     

  • Re: Classic ASP code is not working in IIS 6.0.

    May 22, 2012 02:12 AM|Lloydz|LINK

    Hi,

    Currently, I'm trying to involve someone familiar with this issue to help. To narrow down the issue, could you please check event viewer to see if there's any related events logged?

    Thanks.

  • Re: Classic ASP code is not working in IIS 6.0.

    May 22, 2012 05:56 AM|kalscorpio|LINK

    Hi Lloydz,

     Thanks for your response,

    I checked  event viewer in that server i can see mutiple  times the same error message.

     Is this a generic IIS Error which could mean one of many things in IIS 6.0 ?

     Because we have same ASP Classic code and application working in fine in different server with same OS windows 2003 and IIS 6.0.

    We copied the same code  to different server  with same OS windows 2003 and IIS 6.0 not working..

     

     

     

     

     

  • Re: Classic ASP code is not working in IIS 6.0.

    May 24, 2012 10:30 PM|Sonic Go - MSFT|LINK

    Hi Kalyan,

    Active Server Pages error 'ASP 0115' Unexpected error A trappable error (E06D7363) occurred in an external object. It means an unhandled exception has occurred, and ASP does not have any more information about the error. The exception thrown outside of ASP source code.

    As research you did, you're knowing that the issue may occur at permission, AspMaxRequestEntityAllowed or something else. As experience, the E06D7363 may relate to 3rd party DLL. You could check your source code to see if any 3rd party DLL or function does ASP call.

    For other choose, you can capture a crash dump with DebugDiag v1.2. After finish, analyze the dump with DebugDiag v1.2. It can show you a summary report regarding to the E06D7363 exception.

    Step 1 Download DebugDiag v.12 from http://www.microsoft.com/en-us/download/details.aspx?id=26798
    Step 2 Click Start menu -> All Programs->Debug Diagnostics Tool 1.2->DebugDiag 1.2
    Step 3 Click Add Rule
    Step 4 Select Crash and click Next
    Step 5 Select A specific IIS web application pool and click Next
    Step 6 Find and select a specific application pool which asp webiste hosted and click Next.
    Step 7 Click Exceptions.
    Step 8 In Exception Code (hex), type E06D7363. In Action Type select Full  Userdump. In the Action Limit, type 1. And the click OK.
    Step 9 Click Save & Close.
    Step 10 Click Next.
    Step 11 Type a Rule Name, select a userdump location and click Next.
    Step 12 Select Activate the rule now, and then click Finish.
    Step 13 Keep DebugDiag running in the background. It will capture the crash dump automatically and stop the rule. When the rule keep running, the status is Active. When the monitoring complete, the status become Completed, and Userdump Count should not be 0.

    After crash dump created by DebugDiag.

    1.Click Start menu -> All Programs->Debug Diagnostics Tool 1.2->DebugDiag 1.2
    2.Click Advanced Analysis tag.
    3.Click Add Data Files button on the bottom.
    4.On the pop window, select the crash dump created, click OK.
    5.Select "Crash/Hang Analyzers", click next.
    6.Wait for the analysis report finish.

    Analysis report can give you a overview of the issue. But if you want to know the root cause of the issue. I suggest you creating a Email support ticket or Phone Support ticket, Microsoft will assign an engineer help you analyze the dump and find the root cause of the issue.