How to Enable Debug Mode for Remote Install Servers

ID: Q236033

`
The information in this article applies to:
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows 2000 Server
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

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).


MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

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.

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:
  1. 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:


    2. net stop binlsvc
  2. Start Registry Editor (Regedt32.exe).


  3. Locate the following key in the registry:


    4. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc\Parameters
  4. On the Edit menu, click Add Value, and then add the following registry value:


    5. Value Name: Debug
    Data Type: Reg_dword
    Value: 0x80FFFFFF
  5. Quit Registry Editor.


  6. Start the Binlsvc service by either using the Computer Management snap-in or by typing the following line at a command prompt:


    7. net start binlsvc
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.

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.
  1. 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:


    2. net stop binlsvc
  2. Start Registry Editor (Regedt32.exe).


  3. Locate the following key in the registry:


    4. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc\Parameters
  4. On the Edit menu, click Add Value, and then add the following registry value:


    5. Value Name: Debug
    Data Type: Reg_dword
    Value: 0x00FFFFFF
  5. Locate the following key in the registry:


    6. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Binlsvc
  6. Change the value for the ImagePath entry from


    7. "%SystemRoot%\System32\tcpsvcs.exe"
    to:
    "ntsd -g -G %SystemRoot%\System32\tcpsvcs.exe"
  7. Verify that the new registry entries appear correctly.


  8. Quit Registry Editor.


  9. Using the Computer Management snap-in, expand Services and Applications, and then click Services.


  10. Double-click the Boot Information Negotiation Layer service, click the Logon tab, and then click to select Allow Service to interact with desktop.


  11. Start the Binlsvc service by either using the Computer Management snap-in or by typing the following line at a command prompt:


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

Additional query words: binlsvc.dll

Keywords : kbenv kbtool
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbhowto


Last Reviewed: December 30, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.