You receive error messages in the application log when you run BizTalk Adapter for MQSeries 1.0 on Windows Server 2003 (834159)
The information in this article applies to:
- Microsoft BizTalk Adapter for MQSeries 1.0
Important This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry SYMPTOMSAfter you install Microsoft BizTalk Adapter for MQSeries 1.0
on a computer that is running Microsoft Windows Server 2003, you may receive a
warning message that is similar to the following in the BizTalk Server
application log: Event Type: Warning Event Source:
COM+ Event Category: (99) Event ID: 4458 Date: 12/10/2003 Time:
11:53:50 AM User: N/A Computer:
BIZTALKSERVER Description: During installation of this component into a
COM+ application a registry value was changed from its original value. If you
are experiencing activation problems with this component then please check the
registry values. C:\Program Files\Microsoft BizTalk Adapter for
MQSeries\MQHelper.dll Interface\
{0B7CE8E2-B8CA-4BE0-AD68-B111D7089FAF}\ProxyStubClsid32 Process Name:
RunDll32.exe Comsvcs.dll file version: not loaded For more
information, see Help and Support Center at
http://support.microsoft.com. You may also receive event
messages that are similar to the following three messages when you try to
process documents by using the BizTalk Adapter for MQSeries: Message 1 Event Type: Error Event Source: BizTalk
Server Event Category: Document Processing Event ID: 324 Date:
12/10/2003 Time: 12:45:30 PM User: N/A Computer:
BIZTALKSERVER Description: An error occurred in BizTalk
Server. Details: ------------------------------ [0x80070005] Access
is denied. [0x0159] The server encountered a transport error while
processing the messaging port "ToMQSeries", which uses a transport component
with a ProgID of "AICMQ.MQPipeline.1". [0x012a] All retry transmissions
failed. [0x80070005] Access is denied. [0x0156] The server could not
finish processing messaging port "ToMQSeries". [0x1730] Suspended Queue ID:
"{94C24112-7404-41D2-B631-4667B669111D}" [0x80070005] Access is
denied.
For more information, see Help and Support Center at
http://support.microsoft.com. Message 2 Event Type: Error Event Source: BizTalk
Server Event Category: Document Processing Event ID: 324 Date:
12/10/2003 Time: 12:50:56 PM User: N/A Computer:
BIZTALKSERVER Description: An error occurred in BizTalk
Server. Details: ------------------------------ [0x8004e02f] The
TxIsolation Level property for the COM+ component being created is stronger
than the TxIsolationLevel for the "root" component for the transaction. The
creation failed. [0x0159] The server encountered a transport error while
processing the messaging port "ToMQSeries", which uses a transport component
with a ProgID of "AICMQ.MQPipeline.1". [0x012a] All retry transmissions
failed. [0x8004e02f] The TxIsolation Level property for the COM+ component
being created is stronger than the TxIsolationLevel for the "root" component
for the transaction. The creation failed. [0x0156] The server could not
finish processing messaging port "ToMQSeries". [0x1730] Suspended Queue ID:
"{5E06FF05-0292-4C90-B309-21C32989276C}" [0x8004e02f] The TxIsolation Level
property for the COM+ component being created is stronger than the
TxIsolationLevel for the "root" component for the transaction. The creation
failed.
For more information, see Help and Support Center at
http://support.microsoft.com. Message 3 Event Type: Error Event Source:
MSDTC Event Category: XATM Event ID: 4445 Date:
12/10/2003 Time: 1:10:46 PM User: N/A Computer:
BIZTALKSERVER Description: The XA Transaction Manager cannot load the
requested XA Dll since a registry entry is required for this operation. Please
create a string value in the registry under HKLM\Software\Microsoft\MSDTC\XADLL
where the value name is the name of the dll in the format dllname.dll and the
value is the full path of the Dll. If you are not sure about the name or path
of your XA Dll then please check the documentation for your XA provider. If
this machine is part of a cluster please note that this registry entry needs to
be made for each node in the cluster. amqmtsxatm.dll
For more
information, see Help and Support Center at
http://support.microsoft.com. CAUSEThese errors occur for the following reasons:
- By default, the Security settings for the BizTalk Adapter
for MQSeries COM+ application are different, depending on whether BizTalk
Adapter for MQSeries is installed on Windows 2000 Server or on Windows Server
2003.
- When the BizTalk Adapter for MQSeries is installed on
Windows 2000 Server, the Enforce access checks for this
application option for the BizTalk Adapter for MQSeries COM+
application is not enabled.
- When the BizTalk Adapter for MQSeries is installed on
Windows Server 2003, the Enforce access checks for this
application option for the BizTalk Adapter for MQSeries COM+
application is enabled.
- By default, the Transaction Isolation Level setting for the BizTalk Server Internal Utilities COM+
application is different, depending on whether Microsoft BizTalk Server 2002 is
installed on Windows 2000 Server or on Windows Server 2003.
- When BizTalk Server 2002 is installed on Windows 2000
Server, the Transaction Isolation Level for the
BizTalk.InterchangeStateEngineTx.1 COM+ component is set to
Serialized.
- When BizTalk Server 2002 is installed on Windows Server
2003, the Transaction Isolation Level for the
BizTalk.InterchangeStateEngineTx.1 COM+ component is set to Read
Committed.
- The IBM MQSeries Server Setup routine does not create an
appropriate registry entry for the Amqmtsxatm.dll file.
RESOLUTIONWarning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own
risk. To resolve this problem, follow these steps after
you install BizTalk Adapter for MQSeries on Windows Server 2003:
- Start the Component Services Microsoft Management Console (MMC) snap-in. To do this,
click Start, point to Programs,
point to Administrative Tools, and then click
Component Services.
- In the Component Services snap-in, expand
Computers, expand My Computer, and then
expand COM+ Applications.
- Clear the Enforce access check on this application option for the BizTalk Adapter For MQSeries COM+ application:
- Right-click the BizTalk Adapter For
MQSeries COM+ application, and then click
Properties.
- Click the Advanced tab.
- On the Advanced tab, click to clear
the Disable changes check box, and then click
OK.
- Right-click the BizTalk Adapter For
MQSeries COM+ application, and then click
Properties.
- Click the Security tab.
- On the Security tab, click to clear
the Enforce access checks for this application check box, and
then click OK.
- Change the Transaction Isolation Level setting for the BizTalk.InterchangeStateEngineTx.1 component of
the BizTalk Server Internal Utilities COM+ application from Read
Committed to Serialized:
- In the Component Services snap-in, right-click
the BizTalk Adapter For MQSeries COM+ application, and then
click Properties.
- Click the Advanced tab.
- On the Advanced tab, click to clear
the Disable changes check box, and then click
OK.
- Expand the BizTalk Server Internal
Utilities COM+ application, expand Components,
right-click the BizTalk.InterchangeStateEngineTx.1 component,
and then click Properties.
- Click the Transactions tab.
- On the Transactions tab, change the
selected value in the Transaction Isolation Level list from
Read Committed to Serialized, and then click
OK.
- Quit the Component Services snap-in.
- Create a string value in the registry for the
Amqmtsxatm.dll file:
- Click Start, and then click
Run.
- In the Open box, type
regedit, and then click OK to start
Registry Editor.
- In Registry Editor, locate and then click the following
registry key:
\HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC\XADLL - On the Edit menu, click
New, and then click String Value.
- Type the following properties for the new registry
value:
Value name: amqmtsxatm.dll Value data: Path of the Amqmtsxatm.dll File
Note By default, the path of the Amqmtsxatm.dll file is C:\Program
Files\IBM\WebSphere MQ\Bin\Amqmtsxatm.dll. - Quit Registry Editor.
- Restart the BizTalk Messaging Service:
- Click Start, point
to Programs, point to Administrative
Tools, and then click Services.
- Right-click BizTalk Messaging Service, and then click Restart.
- Quit the Services snap-in.
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section of this
article.
The third-party products that this article discusses are
manufactured by companies that are independent of Microsoft. Microsoft makes no
warranty, implied or otherwise, regarding the performance or reliability of
these products.
Modification Type: | Major | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbprb KB834159 kbAudDeveloper |
---|
|