Microsoft KB Archive/236033

= How to enable debug mode for Remote Install Servers =

Article ID: 236033

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition

-



This article was previously published under Q236033



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



IN THIS TASK

 * SUMMARY
 * Setting RIS for Normal Debug Mode
 * Setting RIS for Full Debug Mode



SUMMARY
You can enable a Windows 2000 Remote Install Server (RIS) to run in Debug mode for troubleshooting purposes. This can be useful when you are trying to troubleshoot client/server issues (such as pre-staged systems not connecting to the RIS server, or clients not receiving information sent to or from the RIS server).

There are two debugging modes that you can enable. The first is Normal Debug mode, which logs output to a file. The other is Full Debug mode, which displays output via NTSD or Kernel Debugger. Both of these options require manual editing of the registry.

back to the top

Setting RIS for Normal Debug Mode
Normal Debug mode enables the BinlSvc (Boot information Negotiation Layer) service to log information to a %SystemRoot%\Debug\Binlsvc.log file. To enable this mode:  Using the Computer Management snap-in, expand Services and Applications, and then click Services. Locate and stop the Boot Information Negotiation Layer service. Or, you can stop the service by typing the following line at a command prompt:

net stop binlsvc

Note If DHCP services are also running on the RIS server, you must stop the DHCP services so that the binlsvc will be able to properly initialize the debug log. Start Registry Editor (Regedt32.exe). Locate the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc\Parameters

 On the Edit menu, point to New, click DWORD Value, and then add the following registry value:

Value Name: Debug

Data Type: Reg_Dword

Value: 0x80FFFFFF

 Quit Registry Editor. Start the Binlsvc service. Start DHCP services if they were stopped in step 1. To start the services, use the Computer Management snap-in or type the following lines at a command prompt. Press ENTER after each line.

net start binlsvc

net start "DHCP Client"

</li></ol>

View the Binlsvc service output in the %SystemRoot%\Debug\Binlsvc.log file to assist in troubleshooting.

NOTE: The output log file does not have standard control characters. If you use a text viewer such as Notepad.exe the file may be difficult to read. You may want to stop the Binlsvc service again and view the file with Write.exe or WordPad.exe.

back to the top

Setting RIS for Full Debug Mode
Full Debug mode sends information out an NTSD window on the console. Most problems can be solved by using the first debug method, but in rare cases in which more debug information is required you can use the method outlined below. <ol> Using the Computer Management snap-in, expand Services and Applications, and then click Services. Locate and stop the Boot Information Negotiation Layer service. Or, you can stop the service by typing the following line at a command prompt:

net stop binlsvc

</li> Start Registry Editor (Regedt32.exe).</li> Locate and click the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc\Parameters

</li> On the Edit menu, point to New, click DWORD Value, and then add the following registry value:

Value Name: Debug

Data Type: Reg_Dword

Value: 00FFFFFF

</li> Locate the ImagePath value under the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc

By default, the setting for the ImagePath value is "%SystemRoot%\System32\tcpsvcs.exe"</li> On the Edit menu, click String, type ntsd -g -G %SystemRoot%\System32\tcpsvcs.exe, and then click OK.</li> Verify that the ImagePath value contains the new setting.</li> Quit Registry Editor.</li> Using the Computer Management snap-in, expand Services and Applications, and then click Services.</li> Double-click the Boot Information Negotiation Layer service, click the Logon tab, and then click to select Allow Service to interact with desktop.</li> Start the Binlsvc service by either using the Computer Management snap-in or by typing the following line at a command prompt:

net start binlsvc

</li></ol>

Try to reproduce the problem. When the problem occurs, look for errors creating machine accounts and LDAP errors.

back to the top

Additional query words: binlsvc.dll binl

Keywords: kbenv kbhowtomaster KB236033

-

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

© Microsoft Corporation. All rights reserved.