Using Oracle Databases with
Microsoft Transaction Server
Version 2.12
April 07, 1999
This information entirely replaces earlier documentation that described how to use Oracle with Microsoft Transaction Server including the documentation that accompanied the Microsoft Transaction Server 2.0 release.
Microsoft Transaction Server components may access both Oracle7 and Oracle8 database servers. They may access Oracle database servers on Windows NT, Unix, and other systems. They may access Oracle Workgroup Servers, Oracle Enterprise Servers, and Oracle Parallel Servers.
The following software is required to access an Oracle database from MTS components.
Component |
Version |
|
|
Oracle 7.3 |
|
Oracle Server on Windows NT |
7.3.3.5.2 or later |
Oracle SQL*Net |
2.3.3.0.4 or later |
Oracle OCIW32.DLL |
1.0.0.5 or later |
Oracle SQLLIB18.DLL |
1.8.3.0.4 or later |
Oracle XA73.DLL |
7.3.3.5.2 or later |
Oracle Server on UNIX |
7.3.3 or later with patches |
|
|
Oracle8 |
|
Oracle Server on Windows NT |
8.0.4.1.1c or later |
Oracle Net8 |
|
Oracle OCIW32.DLL |
8.0.4.0.0 or later |
Oracle SQLLIB80.DLL |
8.0.4.1.0 or later |
Oracle XA80.DLL |
8.0.4.1.0 or later |
Oracle Server on UNIX |
8.0 or later |
|
|
Microsoft |
|
Microsoft Transaction Server |
MTS 2.0 or later on Intel x86 MTS 2.0 and Windows NT4 Service Pack 4 on Compaq Alpha |
Microsoft ODBC Driver for Oracle (MSORCL32.DLL) |
2.73.7283.03 or later on Intel x86 2.573.2927 or later on Compaq Alpha |
ActiveX Data Objects (ADO)* msado15.dll |
1.50.2404 (MDAC 1.5c) or later |
Important Note: Earlier versions of the software may not work properly. We strongly suggest that you install the most recent patch release available from Oracle. The Oracle software versions listed above are the minimum versions required, but please use the most recent version of Oracle software available. Failing to do this is by far the most common source of problems when trying to use Microsoft Transaction Server with Oracle.
Your transactional Microsoft Transaction Server components may access an Oracle 7.3.3 or later database server on Windows NT. You may use either the Oracle 7.3.3 Workgroup Server release for Windows NT or the Oracle 7.3.3 Enterprise Server release for Windows NT.
We do not recommend using
Oracle 7.3.2 or earlier versions of Oracle with Microsoft Transaction Server.
Oracle first supported XA transactions on Windows NT in the Oracle 7.3.3
release; therefore Oracle 7.3.2 and earlier releases cannot be used when
Microsoft Transaction Server transactions are required. In the Oracle 7.3.3.5.0 and higher releases
Oracle works much more reliably on multiprocessor machines and in highly
multi-threaded applications such as IIS or Microsoft Transaction Server.
Your transactional Microsoft Transaction Server components may access an Oracle8 database server on Windows NT.
Your transactional Microsoft Transaction Server components may access an Oracle 7.3 database server on Unix.
You must install the Oracle 7.3.3 release (or later) for that UNIX platform. In most cases, you will also be required to install an Oracle 7.3.3 patch release for Oracle on UNIX.
You must check with Oracle Customer Support to determine if an Oracle 7.3.3 patch release is required for your UNIX platform. Explain that you are going to access your Oracle database on UNIX using the XA transaction support that is included in the Oracle 7.3.3 release on Windows NT.
Your transactional Microsoft Transaction Server components may access an Oracle8 database server on Unix.
Transactional Microsoft Transaction Server components that are running on Intel x86 platforms may access an Oracle 7.3 or Oracle8 database using either Oracle 7.3 or Oracle8 Client software.
By default, Microsoft Transaction Server is configured to use Oracle 7.3 Client Software. For more information on configuring Microsoft Transaction Server to use Oracle8 Client software see Setting Up Oracle Support below.
Transactional Microsoft Transaction Server components that are running on Compaq Alpha platforms may access an Oracle 7.3 or Oracle8 database using Oracle 7.3 Client software. The Required Software section specifies the versions of MTS and the Microsoft Oracle ODBC 2.5 driver you must install on the Compaq Alpha platform.
The Microsoft Oracle ODBC driver (MSORCL.DLL) will not work with the Compaq Alpha Oracle8 Client software. We intend to eliminate this Microsoft Oracle ODBC driver restriction in a future release.
When you use Oracle 7.3 Client software, you must install the Oracle OCIW32.DLL that is designed to work with the Oracle 7.3 release. This DLL is contained in the “WIN32\V7\RSF73” directory of the Oracle 7.3 CDROM.
Oracle also includes an older version of the OCIW32.DLL on the Oracle 7.3 CDROM that is designed to work with the Oracle 7.2 release. This DLL is contained in the “WIN32\V7\RSF72” directory. This DLL will not work with Microsoft Transaction Server.
The following version of the Oracle OCIW32.DLL is provided in the “WIN32\V7\RSF72” director and is known to fail when used with Microsoft Transaction Server:
Version 7.x
Thursday, February 01, 1996 12:50:06 AM
Size 36 KB
You must install Microsoft Transaction Server 2.0 or later if you wish to access an Oracle database using Microsoft Transaction Server under transaction control.
You must install one of the following Microsoft Oracle ODBC drivers if you wish to use Microsoft Transaction Server transactions from an Intel x86 platform.
MS
Oracle ODBC Driver |
Version
Number |
Release
Vehicles |
2.0 updated |
2.73.7283.03 |
MDAC 1.5b & MDAC 1.5c & Windows NT 4.0 Option Pack |
2.0 updated |
2.73.7356 |
ODBC 3.5 SDK |
2.5 |
2.573.2927 |
Visual
Studio 6.0 & Data Access
SDK 2.0 & MDAC 2.0 |
You must install the Microsoft Oracle ODBC 2.5 driver version 2.573.2927, if you wish to use Microsoft Transaction Server transactions from a Compaq Alpha platform. Earlier versions of the Microsoft Oracle ODBC driver did not support the Compaq Alpha platform.
You can obtain the Microsoft Oracle ODBC Driver 2.5 from www.microsoft.com/data by following the “Downloads” link.
If you wish to access an Oracle database, we strongly suggest that you use one of the Microsoft Oracle ODBC Drivers listed above even if you do not require transaction support. These drivers offer better performance than the Oracle 1.0 driver they replace The Oracle 1.0 driver serialized all activity at the driver level; requests were single-threaded through the driver. The Oracle 2.0 and 2.5 drivers serialize all activities at the connection level. This allows different database connections to be used in parallel.
If your application uses ADO, we strongly suggest that you install either the Microsoft Data Access Components 1.5c release or the Microsoft Data Access Components 2.0 release. You can obtain either of these releases from www.microsoft.com/data by following the “Downloads” link to the “Universal Data Access Downloads” section.
If you wish to access an Oracle database from a Microsoft Transaction Server application residing on a MSCS (Wolfpack) cluster, you must install the Windows NT 4.0 Service Pack 4 release after installing the Windows NT4 Option Pack release.
Previously, Microsoft Transaction Server applications that resided on MSCS clusters could not access XA databases including Oracle databases. This was the result of a limitation in Microsoft Distributed Transaction Coordinator version 2.0. Microsoft Distributed Transaction Coordinator stores encryption information related to XA recovery in the Windows NT registry. Previously, this information could not be replicated between the two nodes in an MSCS cluster. As a result, Microsoft DTC could not be used with any XA compliant database in a clustered environment. This restriction has been eliminated in the NT 4.0 Service Pack 4 release.
To set up Oracle to work with transactional Microsoft Transaction Server component, do the following:
1. Install Oracle Database Server Software.
Install the appropriate Oracle software on your database server system.
If your Microsoft Transaction Server application is accessing an Oracle database on either Windows NT or Unix, ensure that the latest Oracle patch is installed on that system. You can obtain the latest Oracle patches for Windows NT from the Oracle FTP site. Go to ftp://oracle-ftp.oracle.com and select "server", "wgt-tech", "server", and "windowsNT"
2. Install Oracle Client Software.
Install the latest Oracle 7.3 or Oracle8 client software on your Microsoft Transaction Server system.
Ensure that the latest Oracle 7.3 or Oracle 8 Client software patch release is installed on the system containing your Microsoft Transaction Server components. Customers often upgrade these Oracle patch releases on the system containing their Oracle database but fail to install the Oracle patch release on the system containing their Microsoft Transaction Server components. Oracle has corrected several bugs that affect their XA transactional client support; therefore, installing the latest Oracle patch release on your Microsoft Transaction Server system is essential. You can obtain the latest Oracle patches Windows NT from the Oracle FTP site. Go to ftp://oracle-ftp.oracle.com and select "server", "wgt-tech", "server", and "windowsNT"
If you are using Oracle 7.3 Client software, ensure that the correct version of the Oracle OCIW32.DLL is installed as described in the Required Software section.
3. Install Microsoft Transaction Server 2.0
Install Microsoft Transaction Server 2.0 by installing the Windows NT4 Option Pack release. When you install Microsoft Transaction Server 2.0, the following software will be installed.
· Microsoft Transaction Server 2.0, including the Microsoft OCI Interface DLL (MTXOCI.DLL)
· Microsoft ODBC 3.5 Driver Manager
· Microsoft ODBC Driver for Oracle 2.0
· ADO 1.5
4. Install Windows NT4.0 Service Pack 4 or Windows NT4.0 Service Pack 5
Install the Windows NT4.0 Service Pack 4 or the Windows NT4.0 Service Pack 5 release. These releases include corrections for several XA related MS DTC problems.
You must install the Windows NT4.0 Service Pack 4 or Windows NT4.0 Service Pack 5 releases after you install the Windows NT4 Option Pack release. This is essential because the NT4.0 Service Pack setup program will only update MTS and MS DTC when the Windows NT4 Option Pack has previously been installed.
5. Install Microsoft Data Access Components 2.0 or Later
If you wish, you may install the Microsoft Data Access Components 2.0 release or later from www.microsoft.com/data by following the “Download” link to the “Universal Data Access Downloads” section.
6. Update Oracle Client Software Registry Keys
If you are using Oracle 7.3 Client software, you may skip this step. If
you are using Oracle8 Client software, you must modify the values of two registry keys.
Under the HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Transaction Server\Local
Computer\My Computer registry
key there are two string-named values that specify the names of the Oracle 7.3
Client software DLLs.
OracleXaLib "xa73.dll"
OracleSqlLib "sqllib18.dll"
Change
these values to specify the names of the Oracle8 Client software DLLs.
OracleXaLib "xa80.dll"
OracleSqlLib "sqllib80.dll"
7. Delete the DTCXATM.LOG.
If you have never installed the Microsoft Transaction
Server 2.0 Beta release, skip this step.
If you previously installed the Microsoft Transaction
Server 2.0 Beta release, use the Windows Explorer to determine if the
DTCXATM.LOG file is present on your system. If so, stop the Microsoft DTC
service and delete the DTCXATM.LOG file.
You should only delete the DTCXATM.LOG file once when
you first upgrade from the Microsoft Transaction Server 2.0 beta release. You
should never delete the DTCXATM.LOG file thereafter, because it may contain
vital recovery information.
8. Enable Oracle XA Transaction Support
If you are using Oracle 7.3
a. Ensure that V$XATRANS$ exists. This view should have been created when the XA library was installed. If this view does not exist, your Oracle system administrator must create it by running the Oracle-supplied script named "XAVIEW.SQL". This file can be found in C:\ORANT\RDBMS73\ADMIN. This SQL script must be executed by the Oracle user “SYS”.
b.
The Oracle system administrator must grant SELECT access to
the public on the $XATRANS$ view. This can be done as follows:
Grant Select on V$XATRANS$ to public.
If you are using Oracle8
a. Oracle8 should have created both the V$XATRANS$ and the DBA_PENDING_TRANSACTIONS views. You should not need to create either of these views.
b.
The Oracle system administrator must grant SELECT access to
the public for the DBA_PENDING_TRANSACTIONS view. This can be done as follows:
Grant Select on DBA_PENDING_TRANSACTIONS to
public.
9. Configure Enough Concurrent Distributed Transactions.
In the Oracle Instance Manager, click “Advanced Mode” on the View menu and select “Initialization Parameters” in the left pane. In the right pane, select “Advanced Tuning” and increase the "distributed_transactions" parameter to allow more concurrent MTS transactions to update the database at a single time.
10. Configuring Integrated Security
Integrated security allows an Oracle database to rely upon Windows NT authentication to validate database users. This permits a user to log in to Oracle without supplying a separate login ID or password. Users can maintain one login ID and password for both Windows NT and Oracle.
If your Microsoft Transaction Server components always supply a login ID and password when connecting to Oracle databases, then you are not using integrated security. This is true whether your applications specify the login ID and password directly or indirectly through a DSN. In either event, you are not using integrated security and can ignore this step.
If you use integrated security, you must configure Microsoft Distributed Transaction Coordinator to run under a login ID and password authorized to connect to your Oracle database. This is required because during database recovery, Microsoft Distributed Transaction Coordinator opens your Oracle database to tell it the outcome of in doubt transactions.
You can configure the login ID for the Microsoft Distributed Transaction Coordinator as follows. From the “Start” menu select “Settings” and then “Control Panel”. Start the “Services” applet on the control panel. Double click on “MSDTC”. Select “Log On As” and specify a login ID and password. Use the Oracle security administration tools to ensure that the login ID you specify is authorized to open your Oracle database.
For more information on Oracle’s integrated Windows NT security facilities consult your Oracle documentation.
11. Configuring Oracle “Multi-Threaded Server” Support
You must configure the Oracle “Multi-Threaded Server” feature if you wish to open a database link to a remote Oracle database. This is essential because when using XA transaction support, the Oracle database must be able to move the XA transaction between processes (in the general case) so it cannot have any operating system file descriptors open but rather it must connect to the remote database using a virtual circuit. Virtual circuits are only supported with Oracle “Multi-Threaded Server”.
If the Oracle “Multi-Threaded Server” feature if not configured properly, Oracle will report the error:
ORA-24777: Cannot create migratable transaction
Note that Oracle refers to the “Multi-Threaded Server” feature using the acronym “MTS”. Microsoft refers to “Microsoft Transaction Server” using the acronym “MTS”. The only relation between these two terms is the one described above. Sorry, we recognize that this is confusing.
12. Configuring Oracle To Support More Connections
If you want to create more than a few dozen connections
to an Oracle database, you must configure the Oracle server to support
additional database connections. See Configuring
Oracle to Support a Large Number of Connections below for more information.
After installing and configuring Oracle support, you must validate your Oracle installation using the Oracle test program installed with MTS. The Oracle test program uses Oracle's OCI XA interfaces in much the same way that MTS uses them. The Oracle test program determines whether you can connect to an Oracle database using Oracle's XA facility. The Oracle test program uses standard Oracle interfaces and transaction facilities. It makes no use of Microsoft Transaction Server or Microsoft Distributed Transaction Coordinator. Therefore, failure of the test program indicates that your Oracle system is improperly installed or configured. If the Oracle test program fails, reinstall and reconfigure Oracle, or contact the Oracle Support Organization for assistance.
To obtain the Oracle test program
The Oracle test program for Oracle7 is installed when Microsoft Transaction Server is installed. You may obtain both the source and object code for the Oracle test program for Oracle 7.3 from ftp://ftp.microsoft.com/bussys/viper/Utilities/OracleTestProgram/Oracle7.3/
You may obtain both the source and object code for the Oracle test program for Oracle8 from ftp://ftp.microsoft.com/bussys/viper/Utilities/OracleTestProgram/Oracle8/
You may compile the source code for either Oracle 7.3 or Oracle8 using the C++ compiler. If you recompile the Oracle test program, we recommend you call the resulting program “TestOracleXaConfig.exe”. That is the name we give it and the instructions that follow assume that you use that name.
To run the Oracle test program
1. Verify that you have installed all of the correct versions of the software as described in Required Software.
2. Create an ODBC DSN that refers to your Oracle database. Ensure that your DSN uses the Microsoft Oracle ODBC driver.
3. Ensure that you have enabled Oracle XA support as described in EnableOracleXATransactionSupport .
4. Delete all existing Oracle trace files from the machine containing the MTS components that access the Oracle database. The easiest way to do this is to use the Windows Explorer to locate and delete all *.TRC files. If the Oracle test program fails, the trace files may help you determine the source of the problem. By deleting all obsolete trace files, you make it easier to find any newly created ones.
5. If you have never installed the Microsoft Transaction Server 2.0 beta release, you can skip this step. If you previously installed the Microsoft Transaction Server 2.0 beta release, use the Windows Explorer to determine if the DTCXATM.LOG file is present on your system. If so, stop the Microsoft DTC service and delete the DTCXATM.LOG file. You should only delete the DTCXATM.LOG file once when you first upgrade from the Microsoft Transaction Server 2.0 beta release. You should never delete the DTCXATM.LOG file thereafter, because it may contain vital recovery information.
6. From the MS-DOS Command prompt run the Oracle test program (TestOracleXaConfig.exe) and supply your Oracle server user ID, password, and service_name. For example:
c:>TestOracleXaConfig.exe -U<user id> -P<Password>
-S<Service_Name as contained in the TNS file>.
7. If you run the test program with no parameters, it will display help information that describes the required parameters. The test program will display information about each Oracle operation it performs and will indicate whether each operation was successful.
8. If the Oracle test program is able to connect to your Oracle database server without error, then it is very likely that MTS will work with Oracle also. If the Oracle test program reports any errors, follow these steps:
8.1. Document the exact error message that the Oracle test program displays.
8.2. Examine the Oracle trace file produced when running the Oracle test program. The Oracle trace information is located in the *.TRC file. The Oracle trace file contains extended error information that is extremely helpful in diagnosing problems.
8.3. Contact your Oracle support representative for assistance.
After you have validated your Oracle installation and configuration using the Oracle test program, you should use the Sample Bank Application supplied with Microsoft Transaction Server to ensure that Microsoft Transaction Server can access your Oracle database.
To validate Oracle support using Sample Bank
1. Verify that your Oracle system is installed and configured correctly using the Oracle test program provided by MTS. If the Oracle test programs reports any error, you must correct that problem before proceeding.
2. On the Oracle database server, create a table named "Account". The following example demonstrates how to set up the Account table.
Owner scott
Name of Table Account
Column 1 Name AccountNo of type NUMBER
Column 2 Name Balance of type NUMBER
3. Populate the "Account” table with at least two rows. The following table illustrates how to populate the table.
AccountNo Balance
1 1000
2 1000
4. On the Oracle database server, create a table named "Receipt". The following example demonstrates how to set up the Receipt table.
Owner scott
Name of Table Receipt
Column 1 Name NextReceipt of type NUMBER
5. Populate the "Receipt" table with at least one row. The following table illustrates how to populate the table.
NextReceipt
1000
6. Create a file DSN using the ODBC configuration utility. Name the file DSN "MTSSamples". Then manually update the DSN file to add the user’s password. The following example demonstrates how to add the user’s password to a file DSN.
[ODBC]
DRIVER=Microsoft ODBC for Oracle
UID=scott
PWD=mypassword
ConnectString=myserver
SERVER=myserver
7. Save the file DSN and run the Sample Bank client.
Oracle changes DLL names when they release new versions of their product. Microsoft Transaction Server relies upon knowing the name of some Oracle Client DLLs. MTS stores these DLL names under the HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Transaction Server\Local Computer\My Computer registry key.
By default, Microsoft Transaction
Server stores the Oracle 7.3 Client DLLs names as two string-named values.
OracleXaLib "xa73.dll"
OracleSqlLib "sqllib18.dll"
If you wish to use Oracle8 Client software, you must
change these values to specify the names of the Oracle8 Client software DLLs.
OracleXaLib "xa80.dll"
OracleSqlLib "sqllib80.dll"
Microsoft Distributed Transaction Coordinator maintains information in the secure portion of the NT registry. It uses this information when performing recovery with XA compliant databases including Oracle. If you change the user id under which Microsoft Distributed Transaction Coordinator executes, you must be careful to ensure that Microsoft Distributed Transaction Coordinator can still access the information it has previously stored in the secure portion of the registry.
If you change Microsoft Distributed Transaction Coordinator’s user id, and it is unable to access the information in the secure registry, you will see the following message in the Windows NT event log.
XATM log object failed to set log encryption key
You can correct this problem as follows:
1. Stop Microsoft Distributed Transaction Coordinator.
2. Change the user id for Microsoft Distributed Transaction Coordinator back to its previous value. Alternatively you can assign a user id that is a member of the administrative group. To change the user id and password, run the Services applet in the Control Panel, double click on the entry for “MSDTC”, and change the “log on as” value.
3. Restart Microsoft Distributed Transaction Coordinator.
If you want to create more than a few dozen connections to an Oracle database, you must configure the Oracle server to support additional database connections.
You may experience one or more of the following errors if you fail to do this:
1. Failures on SQLConnect calls.
2. Failures to enlist on the calling object’s transaction, which may result in any of the following errors in the Oracle trace file:
2.1. Too many sessions
2.2. TNS server failed to locate the server name
2.3. Too many distributed transactions
3. Timeouts while waiting for database locks. This is likely to occur if the configured number of locks is insufficient for the number of concurrently active transactions.
4. Record collision due to locks held by in-doubt transactions.
If you experience any of these problems, consider increasing the following Oracle server configuration parameters:
Oracle Configuation Parameter |
sessions |
distributed_lock_timeout |
distributed_transactions |
dml_locks |
max_transaction_branches |
open_cursors |
processes |
queuesize |
Sessions
The
value for sessions should typically be three times the total number
of database connections that you expect your applications to make.
Queuesize
If
the queue size for the Oracle Listener process is inadequate,
the Listener sometimes falls behind and rejects database open requests. This
happens if the Oracle Listener receives too many connection requests and its
queue overflows. A client that encounters this error reports
To
correct this problem:
1.
Stop the Oracle
listener on the system containing the Oracle database server.
2.
Increase the
QUEUESIZE parameter in the LISTENER.ORA, TNSNET.ORA, or NAMES.ORA files on the
Oracle database server system. Choose the queue size based on the number of
simultaneous, or nearly simultaneous, connection you anticipate. We suggest that you select a
generous value for QUEUESIZE because the Oracle 7.3
system typically opens three database sessions for each transactional database
connection that your application opens. As a result, the Oracle listener queue
may become full and overflow. For example, to accommodate 100 requests, change
the LISTENER.ORA file as follows:
QUEUESIZE = 100
3. Restart the Oracle listener.
If your applications use ADO, make certain that you install the ADO 1.5c release or later. Refer to Required Software for more information.
Currently, the Microsoft Oracle ODBC driver (MSORCL.DLL) will not work with the Compaq Alpha Oracle8 Client software. We intend to correct this Microsoft Oracle ODBC driver problem in a future release.
It is important that the correct version of the OCIW32.DLL is installed on your computer. You should check the version of this DLL any time you reinstall Oracle software. Refer to OracleOCIW32DLL for more information.
This problem is occurring because both MTS and MS DTC must load the Oracle ociw32.dll on their main thread before doing any operation that might access an Oracle database. MTS must load mtxoci.dll because your application may wish to open a connection to an Oracle database. MS DTC must load mtxoci.dll because it may need to perform Oracle database recovery. Since we cannot predict whether your application may wish to use an Oracle database, we always load the ociw32.dll.
We are forced to load the ociw32.dll unconditionally at initialization because of the way that Oracle is implemented on Windows NT. Oracle's implementation on NT monitors all thread attaches. It insists on seeing all thread attaches and will only accept database open requests from threads for which it has seen the initial thread attach. Because of this, we cannot simply fault in the Oracle support DLLs when you actually use them.
You can circumvent this problem in two ways.
If you never use Oracle with MTS or MS DTC, you can rename or delete the Microsoft Oracle database support DLL (mtxoci.dll). When MTS and MS DTC are initiated, they look for and load the mtxoci.dll. The Microsoft mtxoci.dll then loads the Oracle ociw32.dll. MTS and MS DTC will continue to work properly if they cannot locate and load the mtxoci.dll. However, they cannot access or recover an Oracle database if this DLL is absent.
Alternatively you may install the Oracle ociw32.dll that is designed to work with the Oracle 7.3 release. This DLL is contained in the “WIN32\V7\RSF73” directory of the Oracle 7.3 CDROM. You must install version 1.0.0.5 or later of this DLL.
Oracle includes an older version of the ociw32.dll on the Oracle 7.3 CDROM that
is designed to work with the Oracle 7.2 release. This DLL is contained in the
“WIN32\V7\RSF72” directory. This DLL will not work with Microsoft Transaction
Server. The following version of the Oracle ociw32.dll is provided in the
“WIN32\V7\RSF72” director and is known to fail when used with Microsoft
Transaction Server:
Version 7.x
Thursday, February 01, 1996 12:50:06 AM
Size 36 KB