MS SQL Server Connectivity - Network transactions not allowed

Author

Network transactions not allowed

Jan Eliasen

2006-02-15, 9:23 am

Hi

I am trying to use the SQL Adapter in BizTalk 2004 against a SQL
Server 2005. When trying to fire a stored procedure, I get the error
you can see in http://www.eliasen.dk/biztalk/SQLSERVER2005ERROR.jpg

Can anyone tell me what the cause of this can be? I have been to
"Add/Remove windows components" and installed the "Enable Network DTC
Access" or whatever it is called...

Thanks in advance

--
Eliasen Jr. representing himself and not the company he works for.

Private email: jan@eliasen.dk

Peter Yang [MSFT]

2006-02-15, 8:23 pm

Hello Jan,

This issue can occur if the following registry key values on the SQL 2005
servers are not set to 1:

HKey_Local_Machine\S
oftware\Microsoft\MS
DTC\Security\Network
DTCAccess
NetworkDTCAccessAdmi
n
NetworkDTCAccessTran
sactions

I suggest that you check this and restart DTC service on both servers to
test. Moreover, please add the TurnOffRpcSecurity registry by referring to
the following article to isolate the issue:

839187 You receive an "A Microsoft Distributed Transaction Coordinator
problem
http://support.microsoft.com/?id=839187

Also, I have included the following articles for your reference:

293799 How To Use DTCTester Tool
http://support.microsoft.com/?id=293799

I suggest that you test on different SQL 2005/2000 servers if possible to
make sure this issue is related to this specific server.

Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

====================
====================
=============

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: Jan Eliasen <eliasen@nospam.nospam>
>Subject: Network transactions not allowed
>Date: Wed, 15 Feb 2006 15:44:51 +0100
>Message-ID: < d6f6v1pph2beupfe4uar
aet3e43ug933sd@4ax.com>
>X-Newsreader: Forte Free Agent 3.1/32.783
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>Newsgroups: microsoft.public.sqlserver.connect
>NNTP-Posting-Host: 194.192.110.10
>Lines: 1
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:46912
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>
>Hi
>
>I am trying to use the SQL Adapter in BizTalk 2004 against a SQL
>Server 2005. When trying to fire a stored procedure, I get the error
>you can see in http://www.eliasen.dk/biztalk/SQLSERVER2005ERROR.jpg
>
>Can anyone tell me what the cause of this can be? I have been to
>"Add/Remove windows components" and installed the "Enable Network DTC
>Access" or whatever it is called...
>
>Thanks in advance
>
>--
>Eliasen Jr. representing himself and not the company he works for.
>
>Private email: jan@eliasen.dk
>

Jan Eliasen

2006-02-16, 7:23 am

On Thu, 16 Feb 2006 02:11:10 GMT, petery@online.microsoft.com (Peter
Yang [MSFT]) wrote:

>This issue can occur if the following registry key values on the SQL 2005
>servers are not set to 1:
>
> HKey_Local_Machine\S
oftware\Microsoft\MS
DTC\Security\Network
DTCAccess
> NetworkDTCAccessAdmi
n
> NetworkDTCAccessTran
sactions
>
>I suggest that you check this and restart DTC service on both servers to
>test. Moreover, please add the TurnOffRpcSecurity registry by referring to
>the following article to isolate the issue:
>
>839187 You receive an "A Microsoft Distributed Transaction Coordinator
>problem
>http://support.microsoft.com/?id=839187

The registry keys you mentioned weren't set to 1, so now they are.
Also, I have turned off RpcSecurity, as you suggested.

This has just lead to another problem, though. Ig got me a bit
further, but now I get this error instead:
http://www.eliasen.dk/biztalk/newdtcerror.jpg

>Also, I have included the following articles for your reference:
>
>293799 How To Use DTCTester Tool
>http://support.microsoft.com/?id=293799

I have downloaded and tried the dtctester tool, and here is the
result: http://www.eliasen.dk/biztalk/dtc_error.jpg

>I suggest that you test on different SQL 2005/2000 servers if possible to
>make sure this issue is related to this specific server.
The computer with SQL Server 2005 is running in domain A, and the
computer I am trying to connect to the SQL Server 2005 from is in
workgroup mode. Does this change anything?

--
Eliasen Jr. representing himself and not the company he works for.

Private email: jan@eliasen.dk

Peter Yang [MSFT]

2006-02-17, 7:23 am

Hello Jan,

Since a machine is in workgroup, you need to set authentication to "None"
in addition to TurnOffRpcSecurity settings

"No Authentication Required" means that the MSDTC communication on the
network can use non-authenticated and non-encrypted communication, if the
attempts fail to start secure communication

http://blogs.msdn.com/florinlazar/a...3/02/82916.aspx

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

====================
====================
=============

Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:

BCPS:
https://partner.microsoft.com/US/te...erview/40010469

Others: https://partner.microsoft.com/US/te...upportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/defaul...a
l.aspx.

====================
====================
=============

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: Jan Eliasen <eliasen@nospam.nospam>
>Subject: Re: Network transactions not allowed
>Date: Thu, 16 Feb 2006 13:43:45 +0100
>Message-ID: < oes8v11dj1p4pjoqk90k
cl39rsso3h7mho@4ax.com>
>References: < d6f6v1pph2beupfe4uar
aet3e43ug933sd@4ax.com>
<QvAKC5pMGHA.668@TK2MSFTNGXA01.phx.gbl>
>X-Newsreader: Forte Free Agent 3.1/32.783
>MIME-Version: 1.0
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>Newsgroups: microsoft.public.sqlserver.connect
>NNTP-Posting-Host: 194.192.110.10
>Lines: 1
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.connect:46916
>X-Tomcat-NG: microsoft.public.sqlserver.connect
>
>On Thu, 16 Feb 2006 02:11:10 GMT, petery@online.microsoft.com (Peter
>Yang [MSFT]) wrote:
>
to[color=darkred]
>
>The registry keys you mentioned weren't set to 1, so now they are.
>Also, I have turned off RpcSecurity, as you suggested.
>
>This has just lead to another problem, though. Ig got me a bit
>further, but now I get this error instead:
>http://www.eliasen.dk/biztalk/newdtcerror.jpg
>
>
>I have downloaded and tried the dtctester tool, and here is the
>result: http://www.eliasen.dk/biztalk/dtc_error.jpg
>
>The computer with SQL Server 2005 is running in domain A, and the
>computer I am trying to connect to the SQL Server 2005 from is in
>workgroup mode. Does this change anything?
>
>--
>Eliasen Jr. representing himself and not the company he works for.
>
>Private email: jan@eliasen.dk
>

Jan Eliasen

2006-02-17, 7:23 am

On Fri, 17 Feb 2006 03:52:13 GMT, petery@online.microsoft.com (Peter
Yang [MSFT]) wrote:

>Since a machine is in workgroup, you need to set authentication to "None"
>in addition to TurnOffRpcSecurity settings
>
>"No Authentication Required" means that the MSDTC communication on the
>network can use non-authenticated and non-encrypted communication, if the
>attempts fail to start secure communication
>
>http://blogs.msdn.com/florinlazar/a...3/02/82916.aspx
This article mentions adding an TurnOffRpcSecurity key that I should
add to the registry. But isn't that the same as the one you suggested
in your first answer to me? Which I have tried without success?

--
Eliasen Jr. representing himself and not the company he works for.

Private email: jan@eliasen.dk

Jan Eliasen

2006-02-17, 9:23 am

On Fri, 17 Feb 2006 12:54:36 +0100, Jan Eliasen
<eliasen@nospam.nospam> wrote:

>This article mentions adding an TurnOffRpcSecurity key that I should
>add to the registry. But isn't that the same as the one you suggested
>in your first answer to me? Which I have tried without success?
Anyway, I have now added the developing machine from which I am trying
to establish a connection to our domain, and I get the same error.
Note, that the two mahchines are still in two different domains.

--
Eliasen Jr. representing himself and not the company he works for.

Private email: jan@eliasen.dk

Peter Yang [MSFT]

2006-02-20, 3:23 am

Hello Eliasen,

Usuaully TurnOffRpcSecurity key shall solve this problem. Please make sure
this registry key is configured on both machines

MSDTC fails to mutually authenticate when computers do not run in the same
domain
<http://support.microsoft.com/?id=827805>

Please use DTC ping instead mentioned in the following KB to make sure and
TurnOffRpcSecurity is set to True on both machines.
How to troubleshoot MS DTC firewall issues
<http://support.microsoft.com/?id=306843>

Also, did you conifgure "default auentication level" to "none" by running
dcomcnfg?

In addition, please make sure the following registry keys are correct
AllowOnlySecureRpcCa
lls = 0
FallbackToUnsecureRP
CIfNecessary = 0

More related information:

New DTC Functionality in Windows Server 2003 Service Pack 1
http://msdn.microsoft.com/library/e...60b3-4d26-bc04-
e0676ec97786.asp?frame=true

Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

====================
====================
=============

This posting is provided "AS IS" with no warranties, and confers no rights.

Jan Eliasen

2006-02-25, 9:28 am

On Mon, 20 Feb 2006 07:38:12 GMT, petery@online.microsoft.com (Peter
Yang [MSFT]) wrote:

>In addition, please make sure the following registry keys are correct
> AllowOnlySecureRpcCa
lls = 0
This one did the trick, apparently.

Thank you very much!

--
Eliasen Jr. representing himself and not the company he works for.

Private email: jan@eliasen.dk

"Ford," he said, "you're turning into a penguin. Stop it."

Peter Yang [MSFT]

2006-02-25, 9:28 am

Great to hear the issue is resolved. :-)

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

====================
====================
=============

This posting is provided "AS IS" with no warranties, and confers no rights.

Sponsored Links