PRB: VI Debugger Does Not Close Connections When Stopping Before Page Executes

• Microsoft Visual InterDev, version 6.0

SYMPTOMS

When debugging server-side script in Active Server Pages (ASP) pages with Visual InterDev 6.0, you may notice that connections occasionally do not close when you stop the debugger.

The browser may also return the following error:

HTTP Error 403

403.9 Access Forbidden: Too many users are connected

This error can be caused if the Web server is busy and cannot process your request due to heavy traffic. Please try to connect again later.

Please contact the Web server's administrator if the problem persists.

CAUSE

Stopping the Visual InterDev 6.0 debugger before all server-side script has been executed causes connections to remain open indefinitely. These connections will remain open until the Web service is restarted or the Web server is rebooted.

The above error message will occur on a machine running Windows NT Workstation when the 10-connection limit has been reached as a result of the connections not being closed.

RESOLUTION

Do not stop the debugger until all server-side scripts have been executed. If you do run into an error and need to stop the debugger, use the Set Next Statement command in the shortcut menu to skip over the portion of the script that is causing the error and then continue execution.

If you do stop the debugger, you will need to stop and start the Web service in order to drop the existing connections. Issue the following commands from a command prompt to stop and start the Web service:

1. net stop iisadmin



2. net start w3svc

STATUS

This behavior is by design.

REFERENCES

Please refer to the following Web site for related debugging articles:

http://msdn.microsoft.com/vinterdev/technical/articles/debug.asp

Additional query words:

Keywords          : kbVisID600 kbGrpASP kbScriptDebugger 
Version           : WINDOWS:6.0
Platform          : WINDOWS 
Issue type        : kbprb 

Last Reviewed: July 15, 1999