Microsoft KB Archive/169014

= How to Setup for a Remote Debug =

Article ID: 169014

Article Last Modified on 6/23/2005

-

APPLIES TO


 * Microsoft Internet Information Server 2.0
 * Microsoft Internet Information Server 3.0

-



This article was previously published under Q169014



We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:

http://www.microsoft.com/technet/security/prodtech/IIS.mspx



SUMMARY
This article describes how to setup a remote debug for troubleshooting problems with your Internet Information Server (IIS). These steps should be followed after you consult a Microsoft Support Professional and you agree that a debug is necessary.



Process 1 - To install the symbol files
This process should be used to enhance the output log of a Dr. Watson file. It should also be used in conjunction with Process 2 for a remote debug.  Make sure you are running the latest Service Pack (SP) update to Microsoft Windows NT Server. Obtain the latest Service Pack symbols file from the Service Pack compact disc.  If you install from the downloaded symbols file, type in the following command to install them:

      Filename -d Install Path where Filename is the downloaded file, and Install Path is the path to your Windows NT Server directory with \Symbols appended. For example, Sym_400I.exe -d C:\Winnt\Symbols.  If you install from the SP compact disc, copy all subdirectories from the Support\Debug\Symbols directory to the Winnt\Symbols directory.

Process 2 - To set up for a debug
 Create a directory called Debug under your Windows NT directory.</li>  Unzip and copy the following files (from the Windows NT Resource Kit) to the debug directory you created:

<pre class="fixed_text">      Tlist.exe (in the \Compdiag directory) Remote.exe (in the \Netadmin directory) If you do not have the resource kit, you can obtain these files from your Microsoft Support Professional. </li> Copy the .Exe and .Dll files located on the Windows NT compact disc (\Support\Debug\) to the Debug directory.</li> Start a command window and change into your debug directory.</li> Use Tlist.exe file to list the processes. Make a note of the ID for the Inetinfo.exe process. It is the number to the left of the process.</li>  Type in the following command (leaving quotes in place):

<pre class="fixed_text">      Remote /s "cdb -p " debug </li>  At the debug prompt, type the following:

<pre class="fixed_text">      .logopen c:\debug.txt </li> Press g and ENTER to restart the inet service.</li> Minimize the command window and wait for the server to stop. Contact your Support Professional, and then start the remote session.</li></ol>

Process 3 - To set up RAS

 * 1) Make sure you have RAS service installed on a Windows NT Server on the network.
 * 2) Make sure that the RAS is set up to receive incoming calls.
 * 3) Create a user account that is a member of the administrators group. Ensure that the user has dial-in privileges.

Process 4 - To create a debug file
These steps can be used in case you get a crash, and you need to restart the computer before a Debug engineer can get back in touch with you.

  In the debug window, type the following:

<pre class="fixed_text">     kv

</li>  Type the following:

<pre class="fixed_text">     .logclose

</li> Type q</li> You can now restart the server and mail the log file to the support professional you are working with.</li></ol>

Keywords: kbhowto kbother KB169014

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.