classic ASP remote debugging with Visual Studio and IIS 4?
From: Rob Locher (rob_at_roblocher.com)
Date: 03/31/04
- Previous message: Adrian Mascarenhas: "RE: How to get the pictures in the Menu"
- Messages sorted by: [ date ] [ thread ]
Date: 31 Mar 2004 15:12:58 -0800
Has anybody ever succeeded at using Visual Studio 2002 to remotely
debug a classic ASP application with the remote server running Windows
NT and IIS 4? I have spent (wasted really) the entire day trying to
get this to run.
We are required by our governmental customer to support our "classic"
ASP app for a legacy environment of NT 4 service pack 6a and no .NET.
I am testing an issue that we see in IIS4 but not in IIS5 or later.
We use Visual Studio .NET instead of Visual InterDev because it
integrates much better with source control.
For the purpose of testing compatibility issues, I created an image
file of our clean testbed server, and then installed the remote
debugging components. I have done quite a bit of research, and
followed the instructions in the "ASP Remote Debugging Setup" MSDN
library article to the letter. My Windows login is a local admin on
the web server and is also in the "Debugger Users" group. I have read
the excellent troubleshooting document in Microsoft Word format from
GotDotNet.com. I have searched Microsoft's Knowledge Base.
The best I can do is to get the error message:
"Auto-attach to process '[240] mtx.exe' on machine 'TB-IRRI-NT'
failed. Error code 0x80040002 (Can't enumerate any more, because the
associated data is missing )."
I tried doing this with a Windows 2000 server a while back and didn't
have too much trouble (relatively speaking). I realize that I'm
trying to do something tricky here -- has anybody else succeeded?
- Rob
- Previous message: Adrian Mascarenhas: "RE: How to get the pictures in the Menu"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
