After an MSMQ receive function picks up a message from a transactional priva
te queue on a separate windows server, it makes it into the work queue, but 
then continually throws the error below every 2 seconds until I manually mov
e the document from the wor
k queue to the suspend queue.  The error is:

An error occurred in BizTalk Server.

Details:
------------------------------
[0x8004d00a] Unable to enlist in the transaction.

[0x1705] There was a failure creating the internal work item. Make sure 
that SQL Server is running.

[0x1705] There was a failure creating the internal work item. Make sure 
that SQL Server is running.


It's on Win2K3, BTS2002 Sp1, and SQL 2000 SP3 on a separate Win2K3 AD server
.  There appear to be no network connection issues between the two servers.

The content of the document received from the MSMQ seems to be valid:

<message><message_id>25cf9d22-f949-452b-9ee7-b6161f9d09b9</message_id><messa
ge_timestamp>2004-05-13T16:00:15</message_timestamp><message_action>update</
message_action><message_objecttype>1</message_objecttype><message_objectid>&
#123;22334C93-19C8-4E6F-830C-41C
48E840397}</message_objectid><message_code>GaleForce Solutions Publisher</me
ssage_code><objectxml><account><name>McDonald's Corporation!</name><modified
by>{DEAA3E87-C528-4794-9149-1D6B98C79D8F}</modifiedby><modifiedon>2004-
05-13T23:00:13Z</modifiedon></ac
count></objectxml></message>

There are no message group posts or technical articles on this error.  How c
an I fix it?

Mike

[ Post a follow-up to this message ]

Hi Mike, does this happen if you read from local MSMQ?  The reason I ask is
that MSMQ doesn't support doing remote transactional reads, which it sounds
like you are trying to do.  If you read from a remote non-transactional
queue or a local transactional queue do you get the same behavior?
Also, make sure that you have network DTC enabled on both the BizTalk and
the SQL 2000 machines.  This is off by default for Windows 2003.  You can
enable this through control panel, add/remove programs, windows components
and then under the applciation server entry.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| Thread-Topic: Unable to enlist in transaction
| thread-index: AcQ5QaiIDBZso7TWQ8em0JPRaXrdYQ==
| X-WN-Post: microsoft.public.biztalk.server
| From: examnotes <mmcguinness@galeforcesolutions.com>
| Subject: Unable to enlist in transaction
| Date: Thu, 13 May 2004 16:26:03 -0700
| Lines: 22
| Message-ID: <0B08B122-AAB9-4BCD-82FF-770D32EBAA9B@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| 	charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.biztalk.server
| Path: cpmsftngxa10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9459
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.biztalk.server
|
| After an MSMQ receive function picks up a message from a transactional
private queue on a separate windows server, it makes it into the work
queue, but then continually throws the error below every 2 seconds until I
manually move the document from the work queue to the suspend queue.  The
error is:

An error occurred in BizTalk Server.

Details:
------------------------------
[0x8004d00a] Unable to enlist in the transaction.

[0x1705] There was a failure creating the internal work item. Make sure
that SQL Server is running.

[0x1705] There was a failure creating the internal work item. Make sure
that SQL Server is running.


It's on Win2K3, BTS2002 Sp1, and SQL 2000 SP3 on a separate Win2K3 AD
server.  There appear to be no network connection issues between the two
servers.

The content of the document received from the MSMQ seems to be valid:

<message><message_id>25cf9d22-f949-452b-9ee7-b6161f9d09b9</message_id><messa
ge_timestamp>2004-05-13T16:00:15</message_timestamp><message_action>update</
message_action><message_objecttype>1</message_objecttype><message_objectid>&
#123;
22334C93-19C8-4E6F-830C-41C48E840397}</message_objectid><message_code>GaleFo
rce Solutions Publisher</message_code><objectxml><account><name>McDonald's
Corporation!</name><modifiedby>{DEAA3E87-C528-4794-9149-1D6B98C79D8F}</
modif
iedby><modifiedon>2004-05-13T23:00:13Z</modifiedon></account></objectxml></m
essage>

There are no message group posts or technical articles on this error.  How
can I fix it?

Mike
|

[ Post a follow-up to this message ]

Hi Larry, thanks for the reply.  It had been working fine using a remote
transactional local queue.  It suddenly stopped working after I re-installed
BizTalk to solve another issue, and then I couldn't even get it to work with
a remote public queue.  I did get it to work using a public transactional
queue directly on the BizTalk server, but this seems like a poor solution
because the whole purpose of using MSMQ was so that the item could be queued
on the Web Server, and picked up by BizTalk whenever the network was online.
All DTC services are running on both machines.

Any ideas on how to solve this?

Thanks,

Mike

""larry franks"" <larryfr@online.microsoft.com> wrote in message
news:LZBSoIDPEHA.304@cpmsftngxa10.phx.gbl...
> Hi Mike, does this happen if you read from local MSMQ?  The reason I ask
is
> that MSMQ doesn't support doing remote transactional reads, which it
sounds
> like you are trying to do.  If you read from a remote non-transactional
> queue or a local transactional queue do you get the same behavior?
> Also, make sure that you have network DTC enabled on both the BizTalk and
> the SQL 2000 machines.  This is off by default for Windows 2003.  You can
> enable this through control panel, add/remove programs, windows components
> and then under the applciation server entry.
>
> Larry Franks
>
> This posting is provided "AS IS" with no warranties,and confers no rights.
> Subscribe at
>
http://support.microsoft.com/defaul...msdn/nospam.asp
> &SD=msdn
> --------------------
> | Thread-Topic: Unable to enlist in transaction
> | thread-index: AcQ5QaiIDBZso7TWQ8em0JPRaXrdYQ==
> | X-WN-Post: microsoft.public.biztalk.server
> | From: examnotes <mmcguinness@galeforcesolutions.com>
> | Subject: Unable to enlist in transaction
> | Date: Thu, 13 May 2004 16:26:03 -0700
> | Lines: 22
> | Message-ID: <0B08B122-AAB9-4BCD-82FF-770D32EBAA9B@microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.biztalk.server
> | Path: cpmsftngxa10.phx.gbl
> | Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9459
> | NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
> | X-Tomcat-NG: microsoft.public.biztalk.server
> |
> | After an MSMQ receive function picks up a message from a transactional
> private queue on a separate windows server, it makes it into the work
> queue, but then continually throws the error below every 2 seconds until I
> manually move the document from the work queue to the suspend queue.  The
> error is:
>
> An error occurred in BizTalk Server.
>
>  Details:
>  ------------------------------
>  [0x8004d00a] Unable to enlist in the transaction.
>
>  [0x1705] There was a failure creating the internal work item. Make su
re
> that SQL Server is running.
>
>  [0x1705] There was a failure creating the internal work item. Make su
re
> that SQL Server is running.
>
>
> It's on Win2K3, BTS2002 Sp1, and SQL 2000 SP3 on a separate Win2K3 AD
> server.  There appear to be no network connection issues between the two
> servers.
>
> The content of the document received from the MSMQ seems to be valid:
>
>
<message><message_id>25cf9d22-f949-452b-9ee7-b6161f9d09b9</message_id><messa
>
ge_timestamp>2004-05-13T16:00:15</message_timestamp><message_action>update</
>
message_action><message_objecttype>1</message_objecttype><message_objectid>{
>
22334C93-19C8-4E6F-830C-41C48E840397}</message_objectid><message_code>GaleFo
> rce Solutions Publisher</message_code><objectxml><account><name>McDonald's
>
Corporation!</name><modifiedby>{DEAA3E87-C528-4794-9149-1D6B98C79D8F}</modif
>
iedby><modifiedon>2004-05-13T23:00:13Z</modifiedon></account></objectxml></m
> essage>
>
> There are no message group posts or technical articles on this error.  How
> can I fix it?
>
> Mike
> |
>

[ Post a follow-up to this message ]

As long as you are using remote transactional queues, no, I don't really
have suggestions.  While it may have worked for you, it's completely
unsupported by MSMQ.
http://msdn.microsoft.com/library/d...-us/msmq/msmq_a
bout_transactions_98vi.asp has the supported matrix of
read/write/transactional/non-transactional.

I would suggest either having the web application post directly to
MSMQ/MSMQt on the biztalk machine (would use the local MSMQ on the web
server to send to BizTalk,) or create an application on the web server that
reads from the local MSMQ and does a transactional write to the BizTalk
machine.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| From: "Greaterthantwo Media" <nospam_info@greaterthantwo.com>
| References: <0B08B122-AAB9-4BCD-82FF-770D32EBAA9B@microsoft.com>
<LZBSoIDPEHA.304@cpmsftngxa10.phx.gbl>
| Subject: Re: Unable to enlist in transaction
| Date: Mon, 17 May 2004 12:01:00 -0700
| Lines: 107
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.132
| Message-ID: <u7CjOFEPEHA.3452@TK2MSFTNGP10.phx.gbl>
| Newsgroups: microsoft.public.biztalk.server
| NNTP-Posting-Host: h209-139-213-230.gtconnect.net 209.139.213.230
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA07.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa0
6.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9484
| X-Tomcat-NG: microsoft.public.biztalk.server
|
| Hi Larry, thanks for the reply.  It had been working fine using a remote
| transactional local queue.  It suddenly stopped working after I
re-installed
| BizTalk to solve another issue, and then I couldn't even get it to work
with
| a remote public queue.  I did get it to work using a public transactional
| queue directly on the BizTalk server, but this seems like a poor solution
| because the whole purpose of using MSMQ was so that the item could be
queued
| on the Web Server, and picked up by BizTalk whenever the network was
online.
| All DTC services are running on both machines.
|
| Any ideas on how to solve this?
|
| Thanks,
|
| Mike
|
| ""larry franks"" <larryfr@online.microsoft.com> wrote in message
| news:LZBSoIDPEHA.304@cpmsftngxa10.phx.gbl...
| > Hi Mike, does this happen if you read from local MSMQ?  The reason I ask
| is
| > that MSMQ doesn't support doing remote transactional reads, which it
| sounds
| > like you are trying to do.  If you read from a remote non-transactional
| > queue or a local transactional queue do you get the same behavior?
| > Also, make sure that you have network DTC enabled on both the BizTalk
and
| > the SQL 2000 machines.  This is off by default for Windows 2003.  You
can
| > enable this through control panel, add/remove programs, windows
components
| > and then under the applciation server entry.
| >
| > Larry Franks
| >
| > This posting is provided "AS IS" with no warranties,and confers no
rights.
| > Subscribe at
| >
|
http://support.microsoft.com/defaul...msdn/nospam.asp
| > &SD=msdn
| > --------------------
| > | Thread-Topic: Unable to enlist in transaction
| > | thread-index: AcQ5QaiIDBZso7TWQ8em0JPRaXrdYQ==
| > | X-WN-Post: microsoft.public.biztalk.server
| > | From: examnotes <mmcguinness@galeforcesolutions.com>
| > | Subject: Unable to enlist in transaction
| > | Date: Thu, 13 May 2004 16:26:03 -0700
| > | Lines: 22
| > | Message-ID: <0B08B122-AAB9-4BCD-82FF-770D32EBAA9B@microsoft.com>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.biztalk.server
| > | Path: cpmsftngxa10.phx.gbl
| > | Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:9459
| > | NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| > | X-Tomcat-NG: microsoft.public.biztalk.server
| > |
| > | After an MSMQ receive function picks up a message from a transactional
| > private queue on a separate windows server, it makes it into the work
| > queue, but then continually throws the error below every 2 seconds
until I
| > manually move the document from the work queue to the suspend queue.
The
| > error is:
| >
| > An error occurred in BizTalk Server.
| >
| >  Details:
| >  ------------------------------
| >  [0x8004d00a] Unable to enlist in the transaction.
| >
| >  [0x1705] There was a failure creating the internal work item. Make 
sure
| > that SQL Server is running.
| >
| >  [0x1705] There was a failure creating the internal work item. Make 
sure
| > that SQL Server is running.
| >
| >
| > It's on Win2K3, BTS2002 Sp1, and SQL 2000 SP3 on a separate Win2K3 AD
| > server.  There appear to be no network connection issues between the two
| > servers.
| >
| > The content of the document received from the MSMQ seems to be valid:
| >
| >
|
<message><message_id>25cf9d22-f949-452b-9ee7-b6161f9d09b9</message_id><messa
| >
|
ge_timestamp>2004-05-13T16:00:15</message_timestamp><message_action>update</
| >
|
message_action><message_objecttype>1</message_objecttype><message_objectid>&
#123;
| >
|
22334C93-19C8-4E6F-830C-41C48E840397}</message_objectid><message_code>GaleFo
| > rce Solutions
Publisher</message_code><objectxml><account><name>McDonald's
| >
|
Corporation!</name><modifiedby>{DEAA3E87-C528-4794-9149-1D6B98C79D8F}</
modif
| >
|
iedby><modifiedon>2004-05-13T23:00:13Z</modifiedon></account></objectxml></m
| > essage>
| >
| > There are no message group posts or technical articles on this error.
How
| > can I fix it?
| >
| > Mike
| > |
| >
|
|
|

[ Post a follow-up to this message ]

Anyone get any further on this one?  I'm having almost exactly the same issu
es, but with a local queue.

BTS2002 SP1, Win 2k3, MSMQ
and
SQL2000 SP3, Win2k3

both with network COM+ and DTC enabled.  I'm getting the same results from a
 file receive function, the file is absorbed from the file system and makes 
it to the work queue, but sits there generating the error above every 2 seco
nds.

Anyone at all?

[QUOTE]Originally posted by larry franks 
[B]As long as you are using remote transactional queues, no, I don't really
have suggestions.  While it may have worked for you, it's completely
unsupported by MSMQ.
http://msdn.microsoft.com/library/d...-us/msmq/msmq_a
bout_transactions_98vi.asp has the supported matrix of
read/write/transactional/non-transactional.

I would suggest either having the web application post directly to
MSMQ/MSMQt on the biztalk machine (would use the local MSMQ on the web
server to send to BizTalk,) or create an application on the web server that
reads from the local MSMQ and does a transactional write to the BizTalk
machine.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------

[ Post a follow-up to this message ]