Microsoft KB Archive/216668

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

Article ID: 216668

Article Last Modified on 10/15/2002

-

APPLIES TO


 * Microsoft Visual InterDev 6.0 Standard Edition

-



This article was previously published under Q216668



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 before all server-side code is executed, 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

If these steps fail to stop the Web service, you will need to reboot the Web server.



STATUS
This behavior is by design.

