RE: Repost: Help-Debug classic ASP with VS.NET and Windows Server 2003

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Steven Cheng[MSFT] (v-schang_at_online.microsoft.com)
Date: 07/28/04

  • Next message: Developer: "Crash under debugger" 
    Date: Wed, 28 Jul 2004 08:24:46 GMT

    Hi Brent,

    I'm sorry for keeping your waiting. After some tests on my side, here are
    some of my findings and suggestions:

    In addition to the break point not hitting, have you ever got any other
    error messages ? And have you have a look at the VS.NT's debug window to
    see whether the asp's process have been correctly attached?

    Thought you've mentioned that you've done the steps in the
    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebug/htm
    l/vxtskaspremotedebuggingsetup.asp

    I'd like to confirm the following two registry which is most important for
    enabling the remote debuging component on the serverside.

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{6EB22881-8A19-11D0-81B6-00A0C923
    1C29}]
    @="Catalog Class"
    "DllSurrogate"=""

    [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{6EB22881-8A19-11D0-81B6-00A0C923
    1C29}]
    @="Catalog Class"
    "AppID"="{6EB22881-8A19-11D0-81B6-00A0C9231C29}"

    Well, if not other obvious error messages. I think here is one thing
    specified to IIS6 we may have a check. In IIS6, the web site can be
    configured to run under either of the following two processModel:
    1. IIS6's worker process isolation model
    2. IIS5's worker process isolation model

    >From our test, when the site is under IIS5's process isolation Model, the
    remote debugging can work well and the break points can be hit correctly.
    However, when under the IIS6's isolation mode, we need to rebuild the
    project before F5 debug and sometimes the break point won't hit. So please
    have a try under both the two models(and try rebuilding the project when
    test under IIS6 model) to see whether the behavior is same with our test.

    And here is the referece on configuring IIS for running IIS5 isolation mode:
    ========================================
    Configuring IIS for IIS 5.0 Isolation Mode

    You must use IIS 5.0 isolation mode for applications that conflict with
    worker process isolation mode until the applications are modified.

    The following application characteristics conflict with worker process
    isolation mode:

    Dependency on Inetinfo.exe: If the application must run in the Inetinfo.exe
    process, it must be run in IIS 5.0 isolation mode because applications do
    not run in Inetinfo.exe in worker process isolation mode.
    Requires Read Raw Data Filters: Read Raw Data Filters are available in IIS
    5.0 isolation mode only.
    Requires Dllhost.exe: Applications that must be run in a Dllhost.exe
    environment can be run only in IIS 5.0 isolation mode because Dllhost.exe
    is not available in worker process isolation mode.
    If the IIS 6.0 service is running in worker process isolation mode (the IIS
    6.0 default mode), and you must run applications that do not meet the
    requirements for worker process isolation mode, switch to IIS 5.0 isolation
    mode. This means you will not be able to take advantage of worker process
    isolation and the other features of worker process isolation mode.

    After you complete the following procedure, you must restart the WWW
    service, which will temporarily interrupt the service.

    To configure IIS for IIS 5.0 isolation mode

    In IIS Manager, expand the local computer, right-click Web Sites, and then
    click Properties.
    Click the Service tab, select the Run WWW service in IIS 5.0 isolation mode
    check box, and then click OK.
    To start the WWW service, click Yes.
    ===============================================

    Also, don't forget to set the "Enable ASP Debugging" in the web application
    project's property and the
    "Enable ASP ServerSide script debuging" option in the IIS site's
    HomeDirectory--->configuration->debugging Panel.

    Please have a check on the above items. If you have any other findings,
    please also feel free to post here. Thank.s

    Regards,

    Steven Cheng
    Microsoft Online Support

    Get Secure! www.microsoft.com/security
    (This posting is provided "AS IS", with no warranties, and confers no
    rights.)

    Get Preview at ASP.NET whidbey
    http://msdn.microsoft.com/asp.net/whidbey/default.aspx

  • Next message: Developer: "Crash under debugger"

    Relevant Pages