ASP Debugging Configuration Error Dialog Box
This dialog box appears when a configuration error occurred during ASP debugging.
For more information, see article Q258930, "PRB: Visual InterDev ASP Remote Debugging Fails from Windows NT 4.0 to Windows 2000 and from Windows 2000 to Windows NT 4.0" in the Microsoft Knowledge Base.
This error might be caused by any one of the reasons described in the following table.
Cannot enable debugging on server
The debugger is unable to automatically enable debugging for Internet Information Services (IIS). You can try enabling server debugging for the application manually by using the IIS management utility (MMC) and setting the application to run out-of-process.Currently, your options are set to enable server debugging automatically when you start the debugger. Choose No if you want to maintain these option settings. Choose Yes if you want to turn off these options. In the latter case, you should set debugger options manually for your IIS applications to be able to debug server script.
Debug user name or password not valid
To debug server script, you must be able to provide the name and password of a Windows user who has administrative privileges on the server. This error indicates that the name or password you provided was not recognized or does not have appropriate privileges for debugging.Error restoring original server state
When the debug session was being closed, the debugger was unable to set the IIS debug flags to the state they were in when the session started. This can result in the debugger remaining enabled and in the IIS application remaining set to run out-of-process. Use the IIS management utility (MMC) to set the application's debug and out-of-process options to their earlier state.Server is not set up for debugging
Debugging is not enabled for this IIS application, and the project settings are not set to automatically enable debugging. You will not be able to set breakpoints or perform other debugging functions in server script. However, you will be able to debug client script.Turn off automated debug setup
An error occurred during the debugger's attempt to set up debugging on the server (details are displayed in the dialog box). The debugger can attempt again to enable debugging on the server. However, unless the error condition has been corrected, the setup might fail again. If errors persist, you can enable debugging on the server manually.Choose Yes if you want the debugger to continue trying to set up debugging. Choose No if you want to enable server debugging manually and don't want the debugger to do so.
Unable to create Internet Information Services administration object for server
The debugger requires that the IIS application to be debugged be run out-of-process. This error indicates that the debugger was unable to change an in-process IIS application to run out-of-process. As a solution, use the IIS management utility (MMC) to set the application to run out-of-process before starting the debugger.Currently, your options are set to enable server debugging automatically when you start the debugger. Choose No if you want to maintain these option settings. Choose Yes if you want to turn off these options. In the latter case, you should set debugger options manually for your IIS applications to be able to debug server script.
Unable to create Microsoft Transaction Server administration object on server
The debugger creates an MTS package to allow you to attach the debugger to the Web application. This error indicates that the debugger was unable to create the package. Likely causes include:The current user does not have proper permissions for MTS.
MTS has not been installed properly on the server.
Some portion of Microsoft Transaction Server has been corrupted. Try reinstalling MTS.
Your computer is not configured for ASP debugging. For more information,Debugging Web Pages Overview.
Currently, your options are set to enable server debugging automatically when you start the debugger. Choose No if you want to maintain these option settings. Choose Yes if you want to turn off these options. In the latter case, you should set debugger options manually for your IIS applications to be able to debug server script.
Unable to find project on server
The debugger could not find the application root for the project. This can occur if:The project has been deleted from the server. If so, you cannot proceed with debugging.
The project's application root has been destroyed. If so, you can create a new application root using the IIS management utilities.
Currently, your options are set to enable server debugging automatically when you start the debugger. Choose No if you want to maintain these option settings. Choose Yes if you want to turn off these options. In the latter case, you should set debugger options manually for your IIS applications to be able to debug server script.
Unable to find server
The server running the process you want to debug cannot be located. Check the server.Unable to retrieve current debug settings from server
The debugger could not read the current debugging settings for the IIS application. This can occur if the server becomes unavailable during the debug setup process. Verify that the server is running, and then try starting the debugger again.