Microsoft KB Archive/320433

= PRB: Error when you debug remote ASP.NET application =

Article ID: 320433

Article Last Modified on 8/26/2004

-

APPLIES TO

 Microsoft ASP.NET 1.1, when used with:  Microsoft Visual Studio .NET 2003 Academic Edition

 Microsoft Visual Studio .NET 2003 Enterprise Developer

 Microsoft Visual Studio .NET 2003 Enterprise Architect

 Microsoft Visual Studio .NET 2003 Professional Edition</li></ul> </li> Microsoft ASP.NET 1.0, when used with:  Microsoft Visual Studio .NET 2002 Academic Edition</li></ul>

 Microsoft Visual Studio .NET 2002 Enterprise Architect</li></ul>

 Microsoft Visual Studio .NET 2002 Enterprise Developer</li></ul>

 Microsoft Visual Studio .NET 2002 Professional Edition</li></ul> </li></ul>

-

<div class="notice_section">

This article was previously published under Q320433

<div class="notice_section">

If you are debugging on Microsoft Windows XP Service Pack 2, see the following article before you continue reading this article:

833977 How to turn on remote debugging in Windows XP Service Pack 2

<div class="symptoms_section">

SYMPTOMS
When you debug a remote ASP.NET application, you may receive one of the following error messages:

Error while trying to run project: Unable to start debugging on the web server. Unable to map the debug start page URL to a machine name.

-or-

Error while trying to run project: Unable to start debugging on the web server. Not enough storage is available to complete this operation.

<div class="cause_section">

CAUSE
These errors can occur when Distributed Component Object Model (DCOM) traffic cannot flow between the remote computer and the computer that is used for debugging.

<div class="resolution_section">

RESOLUTION
See the &quot;More Information&quot; section for information about how to resolve this problem.

<div class="status_section">

STATUS
This behavior is by design.

<div class="moreinformation_section">

MORE INFORMATION
To debug remote ASP.NET applications, you must have DCOM connectivity. DCOM uses remote procedure call (RPC) as the underlying protocol for communications. If RPC fails between the two computers, the errors may occur.

Some common reasons why RPC communication can fail and cause these errors include:
 * 1) These errors can occur when you debug through a firewall. Microsoft does not recommend and does not support remote ASP.NET debugging through a firewall. Use Terminal Services to log on to the remote server and to debug locally instead.
 * 2) RPC cannot resolve the remote computer name. RPC relies on name resolution to communicate between computers. If you cannot resolve the computer name of the remote server to the correct Internet Protocol (IP) address, errors can occur.
 * 3) RPC traffic can flow in one direction but not in the other. RPC traffic must be able to go from the remote server to the computer that is used to debug and vice versa to successfully debug remotely. To resolve this problem, make sure that RPC communication is enabled in both directions. You can use RPCPing to test the connectivity between the two computers.

<div class="references_section">