Microsoft KB Archive/327102

= BUG: Remote debugging does not succeed when Microsoft Script Editor is installed =

Article ID: 327102

Article Last Modified on 7/29/2005

-

APPLIES TO


 * Microsoft Visual Studio .NET 2002 Professional Edition
 * Microsoft Visual Studio .NET 2002 Enterprise Architect
 * Microsoft Visual Studio .NET 2002 Enterprise Developer
 * Microsoft Visual Studio .NET 2002 Academic Edition

-



This article was previously published under Q327102



SYMPTOMS
When you try to attach to a process on a remote computer where the Visual Studio .NET Remote Debugging Components and Office XP with the Microsoft Script Editor are installed, you may receive the following error message:

Unable to attach to the process. Server execution failed



CAUSE
During installation, the Microsoft Script Editor setup changes just-in-time (JIT) debugging keys in a way that causes the Visual Studio .NET remote debugger to stop working.



RESOLUTION
To resolve this problem, re-register the remote debugging JIT component on the remote computer by running the following command:

vs7jit.exe /regserver

In a default Visual Studio .NET installation, the VS7jit.exe component is installed in the following folder:

\Program Files\Common Files\Microsoft Shared\VS7Debug\



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Steps to reproduce the behavior
The following list outlines the recommended hardware and software that are required to reproduce the behavior:
 * A primary computer with Visual Studio .NET installed.
 * A secondary computer on which to do remote debugging.

To reproduce the behavior, follow these steps:  Install the Visual Studio .NET Remote Debugging components:  Run the main Visual Studio .NET setup program. In the first Setup dialog box, click Remote Components Setup and then follow the steps to install Remote Debugging Components on the operating system version that you are using.  Install the Office XP Web Debugging component:  Select the Custom setup option.</li> Under Features to install, click Office Tools, and then click HTML Source Editing.</li> Move through the folders until you find the Web Debugging selection.</li> Select Run from My Computer for Web Debugging. This will install the Microsoft Script Editor component on the remote computer.</li></ol> </li> Start Microsoft Script Editor 7.0 (which was automatically installed by Office XP). The executable file is Mse7.exe and is typically installed in the \Program Files\Microsoft Office\Office10\ folder.</li> After you run this program one time to configure registry keys, close the Script Editor.</li> From the primary computer, try to attach to a remote process on the secondary remote debug computer:  On the primary computer, start Visual Studio .NET.</li> On the Tools menu, click Debug Processes.</li> In the Processes dialog box, type the remote computer name in the Name box, and then press ENTER.</li> Select the process that you want to debug in the Available Processes list, and then click Attach.</li></ol> </li> After some time, the error described in &quot;Symptoms&quot; appears on the primary computer. Apply the fix in the Resolution section to the secondary remote debug computer, and then you can attach to processes on the remote computer.</li></ol>

<div class="references_section">