Fault Tolerant Systems May Encounter Problems with Windows NT Service Pack 3

This article was previously published under Q171295
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
With the FirstWatch program, transition failures have been observed thatrequire the use of CLARiiON's Trespass utility. For example, the system maystart in Online Primary mode, but any attempt to change into Dual modefails. The Ha.log file contains errors that occurred while using Trespass.You may also notice that the Scsi.exe, Clarscsi.exe, and Diskcfg.exeprograms do not display LUNs (logical unit numbers), which Trespass needsto access.

The CLARiiON Agent Service may report problems in the event log. Thefollowing two events messages have been logged:
ERROR: Opening Device: , 1:0:0.
Is the device configured correctly?
After these events, attempting to select the host in ArrayGuide reports thefollowing error:
Could not connect to the chassis, check device name in fw31a's agent configuration file.
ATF failures have also been observed.
CAUSE
This problem is caused by changes in the way Windows NT handles the SCSILUN enumeration in Service Pack 3.
RESOLUTION
Perform the following steps to resolve this problem:
  1. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
    152734 How to Obtain the Latest Windows NT 4.0 Service Pack


    For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem.NOTE: Service Pack 3 must be applied to Windows NT 4.0 prior to applying this fix.

  2. For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem.WARNING: Using Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

    Install the new Scsiport.sys and go to the following registry key:
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\ 						
  3. For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem.Add the following new value to the above registry path to activate the new code:
          Value Name = ScanDisconnectedDevices      Data Type = REG_DWORD      Data = 1						
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
MORE INFORMATION
The third-party products discussed here are manufactured by vendorsindependent of Microsoft; we make no warranty, implied or otherwise,regarding these products' performance or reliability.
4.00 sp3 NG
Properties

Article ID: 171295 - Last Review: 10/07/2013 05:01:24 - Revision: 1.2

  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
  • kbnosurvey kbarchive kbhotfixserver kbqfe kb3rdparty kbbug kbfile kbfix kbwinnt400sp4fix KB171295
Feedback