Microsoft KB Archive/168529
Article ID: 168529
Article Last Modified on 11/11/1999
- Microsoft Transaction Services 1.0
- Microsoft Transaction Services 1.0
This article was previously published under Q168529
Microsoft Transaction Server 1.0 Service Pack 2, released March 1997, introduced a client configuration feature. When a package is exported, Microsoft Transaction Server now produces an executable file. When run on client computers, this executable file makes the necessary changes to the registry and copies and registers any necessary DLLs. This allows the client computer to access the Microsoft Transaction Server application. If you downloaded Microsoft Transaction Server 1.0 Service Pack 2 before May 2, 1997, be aware that the client installation executable file improperly overwrites two components of the Windows NT operating system: Cfgmgr32.dll and Setupapi.dll. After the client installation has occurred on a computer running Windows NT 4.0, certain Control Panel functions will malfunction, and RAS may also be disabled. Client computers running Windows 95 clients are not affected. After you install Transaction Server 1.0 Service Pack 2a, you should regenerate any client configuration executable files you may have created.
The following are some symptoms you may observe after running the client configuration executable file on a client computer running Windows NT:
- Explorer may cause a general protection fault when you open the Fonts folder in Control Panel. Shortly afterwards, Windows NT will restart.
- You may be halted by an unending series of message boxes when you start Add/Remove programs in Control Panel click the Windows NT Setup tab. To stop the message boxes, you must end Rundll32.exe with Task Manager.
- Control Panel Modems does not start.
- You receive the following error when you start Control Panel Devices:
- The RAS client may not start, claiming that no ports exist.
These symptoms only occur if a client installation executable file has already overwritten the copies of Cfgmgr32.dll and Setupapi.dll that are located in your Winnt\System32 directory.
Cfgmgr32.dll and Setupapi.dll have been overwritten by incorrect versions.
To determine whether you have the incorrect versions of these DLLs, do the following:
- On the client computer, check the Winnt\System32 directory for the Cfgmgr32.dll and Setupapi.dll files.
- If any of the following is true, you have copies of the incorrect DLLs:
- Cfgmgr32.dll is 23,552 bytes.
- Cfgmgr32.dll's properties sheet has no Version information tab.
- Setupapi.dll is 327,072 bytes.
If either of these two DLLs is incorrect, you need to obtain the correct versions of the DLLs that come with Windows NT 4.0.
If you have not run the client installation executable file on your computer, the copies of Cfgmgr32.dll and Setupapi.dll (which are located in your Winnt\System32 directory) should still be correct. You can also use these files to restore any other affected Windows NT 4.0 computers to their correct state. For Windows NT 4.0 Service Pack 2 and earlier, the correct size for these files is:
Cfgmgr32.dll 58,128 bytes
Setupapi.dll 286,480 bytes
If all your copies of Cfgmgr32.dll and Setupapi.dll are incorrect, you must restore them from your Windows NT 4.0 compact disc. To do this, perform the following steps:
- Search for Cfgmgr32.dl_ and Setupapi.dl_ on the Windows NT 4.0 compact disc.
Open a command prompt window and run the following commands:
expand <SetupPath>\cfgmgr32.dl_ <SystemPath>\cfgmgr32.dll expand <SetupPath>\setupapi.dl_ <SystemPath>\setupapi.dll
For example, assuming that the Windows NT 4.0 compact disc is in drive D and you have installed Windows NT 4.0 into the C:\Winnt directory, you would type:
expand d:\i386\cfgmgr32.dl_ C:\Winnt\System32\cfgmgr32.dll expand d:\i386\setupapi.dl_ C:\Winnt\System32\setupapi.dll
Because you installed the correct DLL's into your system directory, you do not need to restart the computer.
NOTE: The instructions given above only apply to versions of Windows NT 4.0 that are earlier than Service Pack 3.
If you have previously installed Transaction Server 1.0 Service Pack 2, you should install Transaction Server 1.0 Service Pack 2a over Service Pack 2 and regenerate any client configuration executables you may have created.
Microsoft has confirmed this to be a problem in Microsoft Transaction Server version 1.0 Service Pack 2. This problem has been corrected in U.S. Service Pack 2a for Microsoft Transaction Server version 1.0, dated May 6,
- For more information, contact your primary support provider.
For more information, visit the Web sites at:
Additional query words: mts SP2
Keywords: kbbug kbfix kbenv kbsetup KB168529