Microsoft KB Archive/251320

From BetaArchive Wiki

Article ID: 251320

Article Last Modified on 5/23/2003


  • Microsoft Windows 2000 Server
  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 Service Pack 1
  • Microsoft SNA Server 4.0 Service Pack 2
  • Microsoft SNA Server 4.0 Service Pack 3

This article was previously published under Q251320


Although SNA Server 4.0 SP3 and later is supported on Windows 2000, when you run Autorun.exe or Setup.exe from the SNA Server 4.0, 4.0 SP1, or 4.0 SP2 refresh CD-ROM on a new installation, the following error message occurs:

This program does not run correctly on this version of Windows. To continue, click Run Program. To exit, click Cancel. For more information, click Details.

When this message is displayed, click Run Program to continue with the install process.

Because SNA Server did not include a refresh, you must install Service Pack 3 on the Windows 2000 computer for it to be supported. After you run the Setup program, the following error message occurs:

A review of your system for external software dependencies has found the following issue:

You are installing SNA Server onto Windows 2000. Not all hardware adapters and features are supported at this time.

Review the Readme included on your CD for details about these dependencies and how you can correct them.

Click OK to continue with the service pack installation.


The following notes are taken from the SNA 4.0 SP3 Readme file, which explains certain caveats when you are running SNA Server 4.0 SP3 on Windows 2000. Note that this information has not been edited by the Microsoft Developer Support Knowledge Base editing team. =======================================
2.0 Running SNA Server on Windows 2000

2.1 Windows 2000 Compatibility

SNA Server 4.0 SP3 contains Windows 2000 compatibility fixes. It was fully tested on Windows 2000 and is fully functional with the exceptions noted below.

  • Certain link services are not supported. In these cases the supplier of the interface adapter has not provided Microsoft with a Windows 2000 compliant link service. Please contact your supplier to see if an updated link service is available. Supported link services include: DLC, Distributed Link Service, Microgate SDLC/X.25, Cirel, and IBM SDLC/X.25.
  • The FTP-AFTP gateway feature does not function because of changes in the underlying FTP support.
  • The SNARAS feature does not function due to changes in the RAS architecture.

The product is fully supported on Windows 2000 Beta 3 and later versions. Full QFE support is available for any compliance issues on the supported versions of the operating system.

Note that an important problem in DLC support was fixed in Windows 2000. The SNA Server team strongly recommends Windows 2000 installations upgrade to the released version of Windows 2000.

2.2 Link Services on Windows 2000

SNA Server link services are composed of two parts: the link service and the underlying device driver. Device drivers that work with SNA Server link services must be rewritten to function correctly under Windows 2000. Currently, the device drivers that run under Windows 2000 are Distributed Link Service (DLS), 802.2 (DLC), Demo Link Service, Microgate SDLC/X.25, and IBM SDLC/X.25.

If Windows 2000 is installed after SNA Server 4.0, then any supported device driver already installed prior to Windows 2000 is upgraded.

If Windows 2000 is already installed and you need to install an SNA Server link service, then you must first install the device driver in Windows 2000 using the device driver wizard. Then you can install the associated link service in SNA Server.

All of the SNA Server-aware device drivers that are developed to be compatible with Windows 2000 will be included on the Windows 2000 CD-ROM.

2.3 Error Message: Error occurred when enumerating the MTS Snap-in

MMC Snap-In Failed to initialize
Name: Not Available
CLSID: {D4D0 226B-93D1-11D0-B1A4-00AA00445589}

You will receive an error if you attempt to open the COMTI management console on a server that was upgraded from Windows NT Server 4.0 to Windows 2000. This happens because the MTS snap-in was replaced by the COM Explorer.

To correct this problem, remove the MTS snap-in and replace it with the COM Manager snap-in.

Any features not described in this section have not been tested at this time. When Windows 2000 is released, a service pack for SNA Server 4.0 will be made available to address any compatibility issues between SNA Server and Windows 2000.

2.4 Windows 2000 Security

Windows 2000 introduces a new "Secure Windows" state. This state affects the capabilities of a normal (non-administrative, non-power) user. In this configuration, users cannot compromise the operating system because they have read-only privileges to all critical operating system components. When Windows 2000 is "clean installed" onto an NTFS partition, it is the default state for all interactive, non-administrative users. If you upgrade from Windows NT 4.0 or do not install onto an NTFS partition, you will need to remove Interactive Users from the Power Users group to configure this state.

SNA Server 4.0 with Service Pack 3 is fully functional in a secure Windows-based configuration with the following restrictions:

  • Restricted Users will be unable to install SNA Server or SNA Server clients. All SNA Server applications are available to all users on the system, so they must be installed by an administrator or power user.

  • None of the management console snap-ins (SNA, COMTI, OLE DB Data Description Utility)can be used by a Restricted User. All of the snap-ins perform administrative functions inappropriate to a Restricted User.

  • The SNA Trace utility cannot be used by a Restricted User. To enable tracing an administrator can run the utility remotely SNATRACE \\<machine name>. The administrator must also change the trace file location in the utility to write the trace files to a directory which exists on <machine name> and the Restricted User has read/write access to.

  • A Restricted User cannot save a data source to the default location when using the new OLE DB Data Source utility. Data sources are typically only created by administrators and power users, so this restriction should have little impact.

To work around any of these restrictions, the user can sign on as a power user or administrator, or Interactive Users can be added to the Power Users group. The latter allows full backward compatibility equivalent to the Windows NT 4.0 Local Users group.

2.5 Host Security and Windows 2000

The Windows NT Password Synchronization Service, and Host Account Cache Service must be installed on the PDC emulator on the Windows 2000 system.

NOTE: The actual Readme file included with SNA 4.0 SP3 indicates that the SNA Host Account Synchronization Service must also be installed on the PDC Emulator, but this is incorrect. The SNA Host Account synchronization Service must be installed on a system running SNA Server and SNA Server does not need to be installed on a PDC Emulator or any other Windows 2000 DC. SNA Server can be installed on Windows 2000 DCs (including the PDC Emulator) or on Windows 2000 Member Servers.

2.6 Host Print Service and Windows 2000

Remote printing from a Windows 2000 server to a Windows NT 4.0 server may consume excessive memory on the Windows 2000 server. To work around this condition, do one of the following:

  1. Print to a remote Windows 2000 server.
  2. Define a local printer pointing to the Windows NT 4.0 Server computer. To do this select "Local Printer" in the "Local or Network Printer" page of the Windows 2000 Add Printer Wizard. On the "Select the Printer Port" page, any of the ports can be used.

Note: If you wish to use Microsoft Networking, then you must specify a "local port" and provide the full UNC (Universal Naming Convention) path to the shared printer on the remote system (example: \\server1\HP4), where server1 is the remote Windows NT 4.0 server and HP4 is the shared printer on server1).

Additional query words: W2K

Keywords: kbprb kbfaq KB251320