Hi, did somebody know a checklist or Q-Article how to configure MSDTC
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.
Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
Showing posts with label msdtc. Show all posts
Showing posts with label msdtc. Show all posts
Wednesday, March 21, 2012
DMZ, MSDTC and Windows Server 2003 SP1
Hi, did somebody know a checklist or Q-Article how to configure MSDTC
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the service
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
DMZ, MSDTC and Windows Server 2003 SP1
Hi, did somebody know a checklist or Q-Article how to configure MSDTC
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the servic
e
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
between
two SQL Server in two separate DMZ (Firewall Ports) ?
Further, I must find out which impact has Windows Server SP1 on MSDTC or
better
on a BizTalk 2004 Server.
Thanks for all Infos.Hi
Check out "INFO: Configuring Microsoft Distributed Transaction Coordinator
(DTC) to Work Through a Firewall" http://support.microsoft.com/kb/250367/
Service Pack 1 enforces tighter security, if you can test the installation
on another system it would help but not guarantee there will not be issues.
You may want to run MBSA to see what it throws before you install the servic
e
pack as these may be potential problem areas.
John
"MV" wrote:
> Hi, did somebody know a checklist or Q-Article how to configure MSDTC
> between
> two SQL Server in two separate DMZ (Firewall Ports) ?
> Further, I must find out which impact has Windows Server SP1 on MSDTC or
> better
> on a BizTalk 2004 Server.
> Thanks for all Infos.
>
>
Friday, February 17, 2012
Distributed Transaction Error with SQL 2000
I have 2 SQL 2000 servers connected with network.
There is no firewall between them.
MSDTC is running on both servers.
One of the 2 servers is called locale the other is called base.
The base one is a linked server in the locale SQL server.
The base server is on Win server 2003 while the locale server is on Win XP SP1.
The distributed transaction is located in the locale server and trying to insert into the base server.
Every time I encounter this error:
Server: Msg 7391, Level 16, State 1, Procedure proc_UpdateDataFromLocalToServer, Line 8
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
-
What are the possible causes of this error?
Thank you.
Bishoy
Can you try to define a linked server between these two servers and execute the script containing the distributed transaction?|||Take help from this KBA http://support.microsoft.com/kb/839279 & http://support.microsoft.com/kb/329332 for a solution.Tuesday, February 14, 2012
Distributed transaction aborted by MSDTC
hi,
i'm implementing a distributed database(partitioned view) system using 3
linked MSSQL 2000 server(SP3),
when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN, I
get the error "Distributed transaction aborted by MSDTC", or sometime
"Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction."
the http://support.microsoft.com/?kbid=834849 says this only happened if one
of the linked server is MSSQL Server 7.0, but all my servers are 2000 Server
with SP3, so can somebody help to resolve this?
If you are running Windows XP or Windows Server 2003 you can use DTC tracing
to find out why the transaction aborts, otherwise you can use SQL Profiler
and include the DTC transaction event class.
Do you have a trigger on one of the tables that is involved in the
transaction?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"eugeneng" <eugeneng@.discussions.microsoft.com> wrote in message
news:C4FC5E8E-B128-459D-9914-78B8CE2AD795@.microsoft.com...
> hi,
> i'm implementing a distributed database(partitioned view) system using 3
> linked MSSQL 2000 server(SP3),
> when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN,
> I
> get the error "Distributed transaction aborted by MSDTC", or sometime
> "Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction."
> the http://support.microsoft.com/?kbid=834849 says this only happened if
> one
> of the linked server is MSSQL Server 7.0, but all my servers are 2000
> Server
> with SP3, so can somebody help to resolve this?
>
>
i'm implementing a distributed database(partitioned view) system using 3
linked MSSQL 2000 server(SP3),
when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN, I
get the error "Distributed transaction aborted by MSDTC", or sometime
"Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction."
the http://support.microsoft.com/?kbid=834849 says this only happened if one
of the linked server is MSSQL Server 7.0, but all my servers are 2000 Server
with SP3, so can somebody help to resolve this?
If you are running Windows XP or Windows Server 2003 you can use DTC tracing
to find out why the transaction aborts, otherwise you can use SQL Profiler
and include the DTC transaction event class.
Do you have a trigger on one of the tables that is involved in the
transaction?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"eugeneng" <eugeneng@.discussions.microsoft.com> wrote in message
news:C4FC5E8E-B128-459D-9914-78B8CE2AD795@.microsoft.com...
> hi,
> i'm implementing a distributed database(partitioned view) system using 3
> linked MSSQL 2000 server(SP3),
> when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN,
> I
> get the error "Distributed transaction aborted by MSDTC", or sometime
> "Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction."
> the http://support.microsoft.com/?kbid=834849 says this only happened if
> one
> of the linked server is MSSQL Server 7.0, but all my servers are 2000
> Server
> with SP3, so can somebody help to resolve this?
>
>
Distributed transaction aborted by MSDTC
hi,
i'm implementing a distributed database(partitioned view) system using 3
linked MSSQL 2000 server(SP3),
when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN, I
get the error "Distributed transaction aborted by MSDTC", or sometime
"Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction."
the http://support.microsoft.com/?kbid=834849 says this only happened if one
of the linked server is MSSQL Server 7.0, but all my servers are 2000 Server
with SP3, so can somebody help to resolve this?If you are running Windows XP or Windows Server 2003 you can use DTC tracing
to find out why the transaction aborts, otherwise you can use SQL Profiler
and include the DTC transaction event class.
Do you have a trigger on one of the tables that is involved in the
transaction?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"eugeneng" <eugeneng@.discussions.microsoft.com> wrote in message
news:C4FC5E8E-B128-459D-9914-78B8CE2AD795@.microsoft.com...
> hi,
> i'm implementing a distributed database(partitioned view) system using 3
> linked MSSQL 2000 server(SP3),
> when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN,
> I
> get the error "Distributed transaction aborted by MSDTC", or sometime
> "Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction."
> the http://support.microsoft.com/?kbid=834849 says this only happened if
> one
> of the linked server is MSSQL Server 7.0, but all my servers are 2000
> Server
> with SP3, so can somebody help to resolve this?
>
>
i'm implementing a distributed database(partitioned view) system using 3
linked MSSQL 2000 server(SP3),
when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN, I
get the error "Distributed transaction aborted by MSDTC", or sometime
"Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction."
the http://support.microsoft.com/?kbid=834849 says this only happened if one
of the linked server is MSSQL Server 7.0, but all my servers are 2000 Server
with SP3, so can somebody help to resolve this?If you are running Windows XP or Windows Server 2003 you can use DTC tracing
to find out why the transaction aborts, otherwise you can use SQL Profiler
and include the DTC transaction event class.
Do you have a trigger on one of the tables that is involved in the
transaction?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"eugeneng" <eugeneng@.discussions.microsoft.com> wrote in message
news:C4FC5E8E-B128-459D-9914-78B8CE2AD795@.microsoft.com...
> hi,
> i'm implementing a distributed database(partitioned view) system using 3
> linked MSSQL 2000 server(SP3),
> when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN,
> I
> get the error "Distributed transaction aborted by MSDTC", or sometime
> "Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction."
> the http://support.microsoft.com/?kbid=834849 says this only happened if
> one
> of the linked server is MSSQL Server 7.0, but all my servers are 2000
> Server
> with SP3, so can somebody help to resolve this?
>
>
Distributed transaction aborted by MSDTC
hi,
i'm implementing a distributed database(partitioned view) system using 3
linked MSSQL 2000 server(SP3),
when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN, I
get the error "Distributed transaction aborted by MSDTC", or sometime
"Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction."
the http://support.microsoft.com/?kbid=834849 says this only happened if one
of the linked server is MSSQL Server 7.0, but all my servers are 2000 Server
with SP3, so can somebody help to resolve this?If you are running Windows XP or Windows Server 2003 you can use DTC tracing
to find out why the transaction aborts, otherwise you can use SQL Profiler
and include the DTC transaction event class.
Do you have a trigger on one of the tables that is involved in the
transaction?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.
"eugeneng" <eugeneng@.discussions.microsoft.com> wrote in message
news:C4FC5E8E-B128-459D-9914-78B8CE2AD795@.microsoft.com...
> hi,
> i'm implementing a distributed database(partitioned view) system using 3
> linked MSSQL 2000 server(SP3),
> when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN,
> I
> get the error "Distributed transaction aborted by MSDTC", or sometime
> "Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction."
> the http://support.microsoft.com/?kbid=834849 says this only happened if
> one
> of the linked server is MSSQL Server 7.0, but all my servers are 2000
> Server
> with SP3, so can somebody help to resolve this?
>
>
i'm implementing a distributed database(partitioned view) system using 3
linked MSSQL 2000 server(SP3),
when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN, I
get the error "Distributed transaction aborted by MSDTC", or sometime
"Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction."
the http://support.microsoft.com/?kbid=834849 says this only happened if one
of the linked server is MSSQL Server 7.0, but all my servers are 2000 Server
with SP3, so can somebody help to resolve this?If you are running Windows XP or Windows Server 2003 you can use DTC tracing
to find out why the transaction aborts, otherwise you can use SQL Profiler
and include the DTC transaction event class.
Do you have a trigger on one of the tables that is involved in the
transaction?
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2004 All rights reserved.
"eugeneng" <eugeneng@.discussions.microsoft.com> wrote in message
news:C4FC5E8E-B128-459D-9914-78B8CE2AD795@.microsoft.com...
> hi,
> i'm implementing a distributed database(partitioned view) system using 3
> linked MSSQL 2000 server(SP3),
> when I try update the distributed table within a BEGIN TRAN & COMMIT TRAN,
> I
> get the error "Distributed transaction aborted by MSDTC", or sometime
> "Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction."
> the http://support.microsoft.com/?kbid=834849 says this only happened if
> one
> of the linked server is MSSQL Server 7.0, but all my servers are 2000
> Server
> with SP3, so can somebody help to resolve this?
>
>
Distributed transaction
I tri do start distribute transaction from a Server sql 2005, and other 2
server SQL 2000. I starto MSDTC service, the 2 server 2000 are connetcetd
true Linked Server from the SQL 2005 with SQLNCLI provider.
When i start the transaction and update a table on my first remote server
SQL server 2000 i get this error:
Server: messgae 7391, level 16, state 2, row 6
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "SQL-SERVER2" was unable to begin a distributed transaction.
OLE DB provider "SQLNCLI" for linked server "SQL-SERVER2" returned message
"The transaction coordinator has disabled the support for remote/network
transaction".
(Sorry but i translate the message error from italian)
If i update the remote server qithout transaction i've got no problem. Works
perfectly.
Someone can help me? How can i solve this problem?
ThanksIf you're sure MSDTC is enabled and running on all your computers then I
would guess there is a firewall blocking the connection in one of the
machines.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"checcouno" <checcouno@.discussions.microsoft.com> wrote in message
news:53CAD34E-4F66-4D30-825B-FB59FACB6D22@.microsoft.com...
>I tri do start distribute transaction from a Server sql 2005, and other 2
> server SQL 2000. I starto MSDTC service, the 2 server 2000 are connetcetd
> true Linked Server from the SQL 2005 with SQLNCLI provider.
> When i start the transaction and update a table on my first remote server
> SQL server 2000 i get this error:
> Server: messgae 7391, level 16, state 2, row 6
> The operation could not be performed because OLE DB provider "SQLNCLI" for
> linked server "SQL-SERVER2" was unable to begin a distributed transaction.
> OLE DB provider "SQLNCLI" for linked server "SQL-SERVER2" returned message
> "The transaction coordinator has disabled the support for remote/network
> transaction".
> (Sorry but i translate the message error from italian)
> If i update the remote server qithout transaction i've got no problem.
> Works
> perfectly.
> Someone can help me? How can i solve this problem?
> Thanks|||Could be a user's permission problem? And how i should configure the DTC
service and MSSQLSERVER service? What kinf of users these services sholud us
e
to run?
My configuration:
My local pc with WINXP SP2 (firewall disabled) and SQL Server 2005 with
MYLOCALDB and one linked server on a Server 2000 sp4 and SQL SERVER 200 sp2.
On both is running and enabled MSDTC, MSSQLSERVER and SQLSERVERAGENT and bot
h
the machine on the same domain.If i try to update a table on the remote
linked server the updata success. If i start a transaction and update the
remote table i've got this error:
OLE DB provider "SQLNCLI" for linked server "SQL-SERVER2" returned message
"The transaction coordinator has disabled its support for remote
transaction/network ".
Thanks
"Roger Wolter[MSFT]" wrote:
> If you're sure MSDTC is enabled and running on all your computers then I
> would guess there is a firewall blocking the connection in one of the
> machines.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "checcouno" <checcouno@.discussions.microsoft.com> wrote in message
> news:53CAD34E-4F66-4D30-825B-FB59FACB6D22@.microsoft.com...
>
>
server SQL 2000. I starto MSDTC service, the 2 server 2000 are connetcetd
true Linked Server from the SQL 2005 with SQLNCLI provider.
When i start the transaction and update a table on my first remote server
SQL server 2000 i get this error:
Server: messgae 7391, level 16, state 2, row 6
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "SQL-SERVER2" was unable to begin a distributed transaction.
OLE DB provider "SQLNCLI" for linked server "SQL-SERVER2" returned message
"The transaction coordinator has disabled the support for remote/network
transaction".
(Sorry but i translate the message error from italian)
If i update the remote server qithout transaction i've got no problem. Works
perfectly.
Someone can help me? How can i solve this problem?
ThanksIf you're sure MSDTC is enabled and running on all your computers then I
would guess there is a firewall blocking the connection in one of the
machines.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"checcouno" <checcouno@.discussions.microsoft.com> wrote in message
news:53CAD34E-4F66-4D30-825B-FB59FACB6D22@.microsoft.com...
>I tri do start distribute transaction from a Server sql 2005, and other 2
> server SQL 2000. I starto MSDTC service, the 2 server 2000 are connetcetd
> true Linked Server from the SQL 2005 with SQLNCLI provider.
> When i start the transaction and update a table on my first remote server
> SQL server 2000 i get this error:
> Server: messgae 7391, level 16, state 2, row 6
> The operation could not be performed because OLE DB provider "SQLNCLI" for
> linked server "SQL-SERVER2" was unable to begin a distributed transaction.
> OLE DB provider "SQLNCLI" for linked server "SQL-SERVER2" returned message
> "The transaction coordinator has disabled the support for remote/network
> transaction".
> (Sorry but i translate the message error from italian)
> If i update the remote server qithout transaction i've got no problem.
> Works
> perfectly.
> Someone can help me? How can i solve this problem?
> Thanks|||Could be a user's permission problem? And how i should configure the DTC
service and MSSQLSERVER service? What kinf of users these services sholud us
e
to run?
My configuration:
My local pc with WINXP SP2 (firewall disabled) and SQL Server 2005 with
MYLOCALDB and one linked server on a Server 2000 sp4 and SQL SERVER 200 sp2.
On both is running and enabled MSDTC, MSSQLSERVER and SQLSERVERAGENT and bot
h
the machine on the same domain.If i try to update a table on the remote
linked server the updata success. If i start a transaction and update the
remote table i've got this error:
OLE DB provider "SQLNCLI" for linked server "SQL-SERVER2" returned message
"The transaction coordinator has disabled its support for remote
transaction/network ".
Thanks
"Roger Wolter[MSFT]" wrote:
> If you're sure MSDTC is enabled and running on all your computers then I
> would guess there is a firewall blocking the connection in one of the
> machines.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "checcouno" <checcouno@.discussions.microsoft.com> wrote in message
> news:53CAD34E-4F66-4D30-825B-FB59FACB6D22@.microsoft.com...
>
>
Subscribe to:
Posts (Atom)