Microsoft KB Archive/256137

= Cannot Log Off or Shut Down a Windows NT Server When a Command Window Is Open =

Article ID: 256137

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Server 4.0 Enterprise Edition

-



This article was previously published under Q256137



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



SYMPTOMS
When you attempt to log off or shut down a server while a command prompt session is still open, the computer may appear to stop responding (hang). When this occurs, you receive the following error message:

The Windows application, Cmd.exe cannot respond to the End Task request.

If you click End Task, the computer pauses for 10 minutes before closing the command window, but does not log you off or shut down. If you click Wait, the command window does not close. If you click Cancel, the command window closes and you are returned to the desktop.



CAUSE
This behavior can occur if the server is deadlocked because of an inappropriate number of CSRSS threads available. This can be caused by a invalid registry entry that is created when you install Seagate Backup Exec version 7.0 build 719.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue:  Start Registry Editor (Regedt32.exe). Locate the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

The data for this value looks something like the following sample data:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads

 Add =16 after "MaxRequestThreads" so that the data looks similar to:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

 Quit Registry Editor. Reboot the computer.</ol>

<div class="moreinformation_section">

MORE INFORMATION
For additional information about other symptoms that can occur if the registry entry is invalid, click the article numbers below to view the articles in the Microsoft Knowledge Base:

187704 Server Lockup Receiving Pop-up Messages with Backup Exec

242118 Connections May Be Lost After You Upgrade to Seagate Backup Exec Version 7.0 Build 719

Keywords: kb3rdparty kberrmsg kbprb KB256137

-

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

© Microsoft Corporation. All rights reserved.