Author |
Message
|
Washington Morais |
Posted: Thu Mar 01, 2012 1:05 pm Post subject: Transaction Scope and Get Issue |
|
|
Newbie
Joined: 09 Feb 2012 Posts: 7
|
Hi, all.
Im facing a problem when i tried to get a message from MQ using Transaction Scope.
In the Get method the error 'MQRC_UOW_ENLISTMENT_ERROR' is thrown. This error only happens on Local Debbug using Visual Studio. If i run the app on the production server, everything works fine.
The MSDTC is configured to perform a Two-Phase-Commit between MQ and SQLServer.
Anyone had a problem like this?
Info:
MQ version: 7.1
SO: Windows XP |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Mar 01, 2012 3:03 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Shall I assume that you have already researched google for MQRC_UOW_ENLISTMENT_ERROR? Lots of hits on this. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
Washington Morais |
Posted: Fri Mar 02, 2012 3:09 am Post subject: |
|
|
Newbie
Joined: 09 Feb 2012 Posts: 7
|
Sure, but this is a specific error that occur only in Windows and could have a lot of possible symptoms. I'm still searching to find out a solution, but maybe someone here had the same problem. |
|
Back to top |
|
 |
JasonE |
Posted: Fri Mar 02, 2012 4:11 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Enabled XA transactions in DTC? FDCs?
Any system (or application) event log messages at the time? |
|
Back to top |
|
 |
Washington Morais |
Posted: Fri Mar 02, 2012 7:54 am Post subject: |
|
|
Newbie
Joined: 09 Feb 2012 Posts: 7
|
|
Back to top |
|
 |
JasonE |
Posted: Fri Mar 02, 2012 8:57 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
The install should have put that there by default... Is that a client image (MC71) or a server install image? |
|
Back to top |
|
 |
JasonE |
Posted: Fri Mar 02, 2012 9:03 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Ahhh... light bulb moment... Is the 7.1 install a non-primary install by any chance? Only the primary should have its registry key set |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Mar 02, 2012 10:29 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Quote: |
In the registry .. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL
|
Strictly a Windows configuration problem and resolution. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
JasonE |
Posted: Fri Mar 02, 2012 12:43 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Eh? This is a registry key under which MQ creates a value during install (7.0 and earlier) for server and client, and when making primary + starting qmgrs (7.1 and later). There shouldnt be a case of needing to use it and it not being there, unless you are trying to do DTC coordination with a client only non-primary install. I would start looking at anything else as a product defect (not saying it is, more that I would start by considering it as one!) |
|
Back to top |
|
 |
|