STOP Message May Appear When You Administer 3.5 Server

ID: Q117860

The information in this article applies to:

Microsoft Windows NT operating system version 3.1
Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

When you attempt to use Windows NT 3.1 User Manager to administer a beta Windows NT Server 3.5, the following STOP message may appear:

User Manager for Domains
<STOP> A device attached to the system is not functioning.

This message may appear only when you attempt to administer a Windows NT Server 3.5 that is not a domain controller.

CAUSE

This message appears when the Windows NT 3.1 User Manager for Domains reads information incorrectly from the Registry of the Windows NT Server 3.5.

Information from the bug report NTRAID:NTBUG:19250 explains: from Thomas Payne, "The 3.1 Usrmgr is checking to see if it is a workstation or a server, and puking when it reads "ServerNT" out of the remote registry.

The ServerNT entry under \\localmachine\system\currentcontrolset\control\product option was changed back to LanmanNT instead of ServerNT for the gold code (build 807)/

STATUS

Microsoft has confirmed this to be a problem in Windows NT and Windows NT Advanced Server version 3.1. This problem has been corrected in Windows NT Workstation and Windows NT Server version 3.5. This problem has also been corrected in the latest U.S. Service Pack for Windows NT and Windows NT Advanced Server version 3.1. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K

Additional query words: prodnt err msg blue trap

Keywords : kbnetwork ntstop ntdomain kbbug3.10
Version : 3.1
Platform : WINDOWS
Issue type :