BUG: Runtime Error: Attempt to Initialize Tagen.dll Fails

• Microsoft COM Transaction Integrator for CICS and IMS, version 1.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to do this, view the "Restoring the Registry" online Help topic in Regedit.exe or the "Restoring a Registry Key" online Help topic in Regedt32.exe.

SYMPTOMS

When a COMTI application method is invoked, COMTI displays a message box with the title, "mtx.exe - DLL Initialization Failed," and the text:

   Initialization of the dynamic link library
   C:\program files\sna\COMTI\tagen.dll failed.
   The process is terminating abnormally.

   ActiveX component can't create object.

   Event ID: 4128
   Source: Transaction Server
   Type: Error
   Category: Class Factory Wrapper
   The run-time environment was unable to load an application component due
   to either an error obtaining its properties from the catalog, loading
   the DLL, or getting the procedure address of DllGetClassObject. This
   error caused the process to terminate.
   C:\program files\sna\COMTI\tagen.dll
   (Package: CedarBank)
   (Microsoft Transaction Server Internals Information: File:
   d:\viper\src\runtime\cfw\ccomdll.cpp, Line: 151)

CAUSE

At run time, Tagen.dll must have access to the Windows NT registry key that identifies the location of a message DLL needed for writing an informative message to the Windows NT Event Log. However, Tagen.dll attempts to get Write access to the registry key, when only Read access is required. The default user profile does not have that right, only Administrators do.

WORKAROUND

Method 1

Start User Manager for domains and assign the Windows NT User (...of the identity under which the Microsoft Transaction Server package component is to execute) to the Windows NT Administrators Group.

Method 2

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" online Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" online Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

1. Start Registry Editor (Regedt32.exe).

2. Locate the following key and select it:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog \Application\COMTI

   NOTE: The above registry key is one path; it has been wrapped for readability.

3. Click Permissions on the Security menu.

4. Confirm that the Windows NT Group, Everyone, has either Read or Special Access permission for this registry key.

5. Select the Name, Everyone. Click Full Control on the Type of Access menu.

6. Click OK.

STATUS

Microsoft has confirmed this to be a problem in Microsoft COM Transaction Integrator for CICS and Information Management System, version 1.0. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : kbbug1.00 CTIDeploy CTISecurity
Version           : WINDOWS:1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending