Help and Support
 

powered byLive Search

Disconnected WinStation Sessions that Generate a "Hard Error" Dialog Boxes Cannot be Reset

Article ID:229012
Last Review:February 22, 2007
Revision:1.3
This article was previously published under Q229012
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 (http://support.microsoft.com/kb/256986/EN-US/) Description of the Microsoft Windows Registry

SYMPTOMS

Terminal Server clients go into a "down" state and cannot be reset.

Back to the top

CAUSE

If a disconnected session has an active "Hard Error" dialog box that is generated by a DOS or 16-bit program, it cannot be reset. If a reset is attempted on the workstation, it stays in a "down" state until the computer is restarted.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 (http://support.microsoft.com/kb/152734/EN-US/) How to Obtain the Latest Windows NT 4.0 Service Pack

Back to the top

WORKAROUND

To work around this problem, you can disable dialog boxes from ever being displayed. This is done with a registry setting. For additional information, see the following article or articles in the Microsoft Knowledge Base:
124873 (http://support.microsoft.com/kb/124873/EN-US/) Disabling System Hard Error Message Dialog Boxes
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.

1.Start Registry Editor (Regedt32.exe).
2.Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode
3.Change the default value of 0 to 2. The following table defines the three possible values for ErrorMode:
   Value   Result
   -----   ----------------------------------------------------------------
     0     Errors are serialized and wait for a response.
 
     1     If the error does not come from the system, then the system
           continues in normal operating mode. If the error comes from the
           system, then it is written to the system log; no user
           intervention is required and dialog boxes are not displayed.
 
     2     The error is written to the system log; the dialog box is not
           displayed.
						

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 5.

Back to the top


APPLIES TO
Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4

Back to the top

Keywords: 
kbhotfixserver kbqfe kbbug kbfix kbwinnt400sp5fix KB229012

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.