The information in this article applies to:
SUMMARY
This article describes how to identify the version of SNA Server or
SNA Server client software that is being used. Windows NT version
dependencies are also described below.
2.11 Service Pack 2 Microsoft SNA Server MORE INFORMATION
The Snaver.exe program can be used to display the internal build
number of any SNA Server Win32 DLL or EXE module. When starting
Snaver, it also displays a version number itself, which are listed
below.
NOTE 1: If SNA Server 2.11 is running on Windows NT 4.0, the SNA Server
Admin Help/About dialog incorrectly shows the SNA Server version
as "Beta Version 2.0.0". To determine the actual SNA Server
version, Snaver.exe should be run instead.
NOTE 2: SNA Server 2.11 was refreshed when 2.11 SP1 was released. Customers purchasing SNA Server 2.11 after January 1996 should have received the 2.11 SP1 version. NOTE 3: SNA Server 3.0 was refreshed when 3.0 SP1 was released. Customers purchasing SNA Server 3.0 after April 1997 should have received the 3.0 SP1 version. NOTE 4: SNA Server 2.11 SP2 did not update the Snaver.exe program, so the internal build number will be unchanged. To determine if 2.11 SP2 has been applied to the server, use Snaver to view the build number of the <snaroot>\system\Snadmod.dllL file, which will be 2.11.0.315. NOTE 5: The initial version of the SNA Server Windows 95 client software was made available electronically by Microsoft on ftp.microsoft.com during December 1995. This version had several problems which caused TCP/IP session drops, which were fixed in the SNA Windows 95 client included in 2.11 SP1. The initial release of SNA Server 2.11 did not include an SNA Windows 95 client since the 2.11 release predated the Windows 95 general release in August 1995. NOTE 6: SNA Server 3.0 SP3 included refreshed client code and setup programs for Windows NT and Windows 95. However, these refreshes incorrectly set the SNA client version information in the registry to "3.0 Service Pack 2". The build will still correctly indicate "Build 471" to reflect that SNA 3.0 SP3 is applied on the client computer. NOTE 7: SNA Server 4.0 SP1 does not update the Snaver.exe program, so the internal build number displays as 4.0.0.500. To determine if 4.0 SP1 has been applied to the server, use Snaver to view the build number of the <Snaroot>\System\Snadmod.dll file, which is 4.0.0.517. SNA Server and Windows NT version dependenciesSNA Server 2.0 - Server runs on Windows NT 3.1. SNA Server 2.0 hotfixes were required to run on Windows NT 3.5. This version is longer supported by Microsoft.SNA Server 2.1 - Runs on either Windows NT 3.1 and 3.5. This version is no longer supported by Microsoft SNA Server 2.11 - Server requires Windows NT 3.5 or greater (does not run on 3.1) SNA Server 3.0 - Server requires Windows NT 3.51 or greater (does not run on 3.5) SNA Server 4.0 - Server and Windows NT client requires Windows NT 4.0 Service Pack 3 or greater (setup prevents installation on NT 3.51 and earlier versions). When choosing to install COM Transaction Integrator (COMTI), OLE/DB Provider, or ODBC Driver for DB2, the system must be installed with Microsoft Internet Explorer 3.02 or later, and the Windows NT 4.0 Option Pack (COMTI requires Microsoft Transaction Server and optionally, IIS from the Option Pack). If COMTI, OLE/DB or ODBC are chosen, SNA Server automatically installs the Microsoft Data Access Components version (MSDAC) 1.5. See the SNA Server 4.0 release notes or Getting Started guide for specific software requirements and instructions. Additional query words: snaver snafaq
Keywords : kbenv kbinterop kbnetwork prodsna |
Last Reviewed: January 17, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |