Transaction Server Error 4097 Occurs Because of Failfast (323879)



The information in this article applies to:

  • Microsoft Transaction Server 2.0

This article was previously published under Q323879

SYMPTOMS

Occasionally, you may see transaction server error 4097 because of a failfast that is trying to create a non-Microsoft Visual J++ object.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time    Version         Size    File Name      Platform 
   --------------------------------------------------------------------- 
   25-Jun-2002   07:25   2002.6.911.0    71,168  Adme.dll       x86
   25-Jun-2002   07:25   2002.6.911.0   131,584  Dtccm.dll      x86
   25-Jun-2002   07:26   2002.6.911.0   185,344  Dtcxatm.dll    x86
   25-Jun-2002   07:26   2002.6.911.0    24,064  Msdtc.dll      x86
   25-Jun-2002   07:26   2002.6.911.0   105,984  MtsEvents.dll  x86
   25-Jun-2002   07:26   2002.6.911.0    49,152  Mtxas.dll      x86
   25-Jun-2002   07:27   2002.6.911.0   466,944  Mtxex.dll      x86
				
NOTE: Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows NT 4.0.

MORE INFORMATION

The call stack appears similar to the following:

0198d020 6981e066 ntdll!DbgBreakPoint
0198d828 6981d89f mtxex!FailFast+0x68 
0198d848 697f1df5 mtxex!InternalError+0x6f 
0198d884 697fb2cc mtxex!CViperThread::Javatize+0x5c 
0198d8b0 697e6eea mtxex!CCFWrapper::GetClassObject+0x166 
0198d8e8 697e68f2 mtxex!CreateInstanceCore+0xaa 
0198d908 697f1782 mtxex!CActivity::OnCreateInstanceAndUnbind+0x22
					

Notice the CViperThread::Javatize call. In the cause of this condition, the object that is being created is not a Visual J++ object. This code path should only be taken for Visual J++ objects.

This hotfix fixes an error that permits this code path to be taken for non-Visual J++ objects.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB323879