Please Help!...Recently we started seeing DTC failures between two of our
servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
t was working a week ago and our Network gurus say nothing has changed on the
network.
I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
in the same domain and network segment with no firewall between them. I also
added entries to the host and lmhost files on both.
I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
when run from A, but not from B (it hangs in the bind phase after
successfully completing the RPC portion but no error is retuned)The DTCTester
returns the following when run from either:
Executed: dtctester
DSN: dtctest
User Name: sa
Password:
tablename= #dtc5330
Creating Temp Table for Testing: #dtc5330
Warning: No Columns in Result Set From Executing: 'create table #dtc5330
(ival i
nt)'
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
Driver]
Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.
If the 2003 server has had sp1 installed recently, this may be your
problem.You will need to change the security settings in DCOM.
"Joe Loyd" wrote:
> Please Help!...Recently we started seeing DTC failures between two of our
> servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> t was working a week ago and our Network gurus say nothing has changed on the
> network.
> I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> in the same domain and network segment with no firewall between them. I also
> added entries to the host and lmhost files on both.
> I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> when run from A, but not from B (it hangs in the bind phase after
> successfully completing the RPC portion but no error is retuned)The DTCTester
> returns the following when run from either:
> Executed: dtctester
> DSN: dtctest
> User Name: sa
> Password:
> tablename= #dtc5330
> Creating Temp Table for Testing: #dtc5330
> Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> (ival i
> nt)'
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> Driver]
> Distributed transaction error'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
>
|||Thank you for the response! What additional settings need to be made?
"BitWise" wrote:
[vbcol=seagreen]
> If the 2003 server has had sp1 installed recently, this may be your
> problem.You will need to change the security settings in DCOM.
> "Joe Loyd" wrote:
|||At the run command type dcomcnfg.exe
Expand Component services >> Computers >> My Computer
Right click My Computer and choose properties
Click on the MSDTC tab
Choose the Security Configuration Button
Under Transaction Manager Communication group, select No Authentication
Required
Click OK
"Joe Loyd" wrote:
[vbcol=seagreen]
> Thank you for the response! What additional settings need to be made?
> "BitWise" wrote:
Showing posts with label win2003. Show all posts
Showing posts with label win2003. Show all posts
Sunday, February 19, 2012
DTC Fails
Please Help!...Recently we started seeing DTC failures between two of our
servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
t was working a week ago and our Network gurus say nothing has changed on the
network.
I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
in the same domain and network segment with no firewall between them. I also
added entries to the host and lmhost files on both.
I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
when run from A, but not from B (it hangs in the bind phase after
successfully completing the RPC portion but no error is retuned)The DTCTester
returns the following when run from either:
Executed: dtctester
DSN: dtctest
User Name: sa
Password:
tablename= #dtc5330
Creating Temp Table for Testing: #dtc5330
Warning: No Columns in Result Set From Executing: 'create table #dtc5330
(ival i
nt)'
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
Driver]
Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.If the 2003 server has had sp1 installed recently, this may be your
problem.You will need to change the security settings in DCOM.
"Joe Loyd" wrote:
> Please Help!...Recently we started seeing DTC failures between two of our
> servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> t was working a week ago and our Network gurus say nothing has changed on the
> network.
> I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> in the same domain and network segment with no firewall between them. I also
> added entries to the host and lmhost files on both.
> I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> when run from A, but not from B (it hangs in the bind phase after
> successfully completing the RPC portion but no error is retuned)The DTCTester
> returns the following when run from either:
> Executed: dtctester
> DSN: dtctest
> User Name: sa
> Password:
> tablename= #dtc5330
> Creating Temp Table for Testing: #dtc5330
> Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> (ival i
> nt)'
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> Driver]
> Distributed transaction error'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
>|||Thank you for the response! What additional settings need to be made?
"BitWise" wrote:
> If the 2003 server has had sp1 installed recently, this may be your
> problem.You will need to change the security settings in DCOM.
> "Joe Loyd" wrote:
> > Please Help!...Recently we started seeing DTC failures between two of our
> > servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> > t was working a week ago and our Network gurus say nothing has changed on the
> > network.
> >
> > I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> > in the same domain and network segment with no firewall between them. I also
> > added entries to the host and lmhost files on both.
> >
> > I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> > when run from A, but not from B (it hangs in the bind phase after
> > successfully completing the RPC portion but no error is retuned)The DTCTester
> > returns the following when run from either:
> >
> > Executed: dtctester
> > DSN: dtctest
> > User Name: sa
> > Password:
> > tablename= #dtc5330
> > Creating Temp Table for Testing: #dtc5330
> > Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> > (ival i
> > nt)'
> > Initializing DTC
> > Beginning DTC Transaction
> > Enlisting Connection in Transaction
> > Error:
> > SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> > Driver]
> > Distributed transaction error'
> > Error:
> > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> > cur
> > sor state
> > Typical Errors in DTC Output When
> > a. Firewall Has Ports Closed
> > -OR-
> > b. Bad WINS/DNS entries
> > -OR-
> > c. Misconfigured network
> > -OR-
> > d. Misconfigured SQL Server machine that has multiple netcards.
> > Aborting DTC Transaction
> > Releasing DTC Interface Pointers
> > Successfully Released pTransaction Pointer.
> >
> >|||At the run command type dcomcnfg.exe
Expand Component services >> Computers >> My Computer
Right click My Computer and choose properties
Click on the MSDTC tab
Choose the Security Configuration Button
Under Transaction Manager Communication group, select No Authentication
Required
Click OK
"Joe Loyd" wrote:
> Thank you for the response! What additional settings need to be made?
> "BitWise" wrote:
> > If the 2003 server has had sp1 installed recently, this may be your
> > problem.You will need to change the security settings in DCOM.
> >
> > "Joe Loyd" wrote:
> >
> > > Please Help!...Recently we started seeing DTC failures between two of our
> > > servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> > > t was working a week ago and our Network gurus say nothing has changed on the
> > > network.
> > >
> > > I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> > > in the same domain and network segment with no firewall between them. I also
> > > added entries to the host and lmhost files on both.
> > >
> > > I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> > > when run from A, but not from B (it hangs in the bind phase after
> > > successfully completing the RPC portion but no error is retuned)The DTCTester
> > > returns the following when run from either:
> > >
> > > Executed: dtctester
> > > DSN: dtctest
> > > User Name: sa
> > > Password:
> > > tablename= #dtc5330
> > > Creating Temp Table for Testing: #dtc5330
> > > Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> > > (ival i
> > > nt)'
> > > Initializing DTC
> > > Beginning DTC Transaction
> > > Enlisting Connection in Transaction
> > > Error:
> > > SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> > > Driver]
> > > Distributed transaction error'
> > > Error:
> > > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> > > cur
> > > sor state
> > > Typical Errors in DTC Output When
> > > a. Firewall Has Ports Closed
> > > -OR-
> > > b. Bad WINS/DNS entries
> > > -OR-
> > > c. Misconfigured network
> > > -OR-
> > > d. Misconfigured SQL Server machine that has multiple netcards.
> > > Aborting DTC Transaction
> > > Releasing DTC Interface Pointers
> > > Successfully Released pTransaction Pointer.
> > >
> > >
servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
t was working a week ago and our Network gurus say nothing has changed on the
network.
I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
in the same domain and network segment with no firewall between them. I also
added entries to the host and lmhost files on both.
I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
when run from A, but not from B (it hangs in the bind phase after
successfully completing the RPC portion but no error is retuned)The DTCTester
returns the following when run from either:
Executed: dtctester
DSN: dtctest
User Name: sa
Password:
tablename= #dtc5330
Creating Temp Table for Testing: #dtc5330
Warning: No Columns in Result Set From Executing: 'create table #dtc5330
(ival i
nt)'
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
Driver]
Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.If the 2003 server has had sp1 installed recently, this may be your
problem.You will need to change the security settings in DCOM.
"Joe Loyd" wrote:
> Please Help!...Recently we started seeing DTC failures between two of our
> servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> t was working a week ago and our Network gurus say nothing has changed on the
> network.
> I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> in the same domain and network segment with no firewall between them. I also
> added entries to the host and lmhost files on both.
> I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> when run from A, but not from B (it hangs in the bind phase after
> successfully completing the RPC portion but no error is retuned)The DTCTester
> returns the following when run from either:
> Executed: dtctester
> DSN: dtctest
> User Name: sa
> Password:
> tablename= #dtc5330
> Creating Temp Table for Testing: #dtc5330
> Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> (ival i
> nt)'
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> Driver]
> Distributed transaction error'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
>|||Thank you for the response! What additional settings need to be made?
"BitWise" wrote:
> If the 2003 server has had sp1 installed recently, this may be your
> problem.You will need to change the security settings in DCOM.
> "Joe Loyd" wrote:
> > Please Help!...Recently we started seeing DTC failures between two of our
> > servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> > t was working a week ago and our Network gurus say nothing has changed on the
> > network.
> >
> > I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> > in the same domain and network segment with no firewall between them. I also
> > added entries to the host and lmhost files on both.
> >
> > I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> > when run from A, but not from B (it hangs in the bind phase after
> > successfully completing the RPC portion but no error is retuned)The DTCTester
> > returns the following when run from either:
> >
> > Executed: dtctester
> > DSN: dtctest
> > User Name: sa
> > Password:
> > tablename= #dtc5330
> > Creating Temp Table for Testing: #dtc5330
> > Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> > (ival i
> > nt)'
> > Initializing DTC
> > Beginning DTC Transaction
> > Enlisting Connection in Transaction
> > Error:
> > SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> > Driver]
> > Distributed transaction error'
> > Error:
> > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> > cur
> > sor state
> > Typical Errors in DTC Output When
> > a. Firewall Has Ports Closed
> > -OR-
> > b. Bad WINS/DNS entries
> > -OR-
> > c. Misconfigured network
> > -OR-
> > d. Misconfigured SQL Server machine that has multiple netcards.
> > Aborting DTC Transaction
> > Releasing DTC Interface Pointers
> > Successfully Released pTransaction Pointer.
> >
> >|||At the run command type dcomcnfg.exe
Expand Component services >> Computers >> My Computer
Right click My Computer and choose properties
Click on the MSDTC tab
Choose the Security Configuration Button
Under Transaction Manager Communication group, select No Authentication
Required
Click OK
"Joe Loyd" wrote:
> Thank you for the response! What additional settings need to be made?
> "BitWise" wrote:
> > If the 2003 server has had sp1 installed recently, this may be your
> > problem.You will need to change the security settings in DCOM.
> >
> > "Joe Loyd" wrote:
> >
> > > Please Help!...Recently we started seeing DTC failures between two of our
> > > servers. The calling server(A) is Win2003 and the destination (B) is Win2K. I
> > > t was working a week ago and our Network gurus say nothing has changed on the
> > > network.
> > >
> > > I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> > > in the same domain and network segment with no firewall between them. I also
> > > added entries to the host and lmhost files on both.
> > >
> > > I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
> > > when run from A, but not from B (it hangs in the bind phase after
> > > successfully completing the RPC portion but no error is retuned)The DTCTester
> > > returns the following when run from either:
> > >
> > > Executed: dtctester
> > > DSN: dtctest
> > > User Name: sa
> > > Password:
> > > tablename= #dtc5330
> > > Creating Temp Table for Testing: #dtc5330
> > > Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> > > (ival i
> > > nt)'
> > > Initializing DTC
> > > Beginning DTC Transaction
> > > Enlisting Connection in Transaction
> > > Error:
> > > SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Server
> > > Driver]
> > > Distributed transaction error'
> > > Error:
> > > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid
> > > cur
> > > sor state
> > > Typical Errors in DTC Output When
> > > a. Firewall Has Ports Closed
> > > -OR-
> > > b. Bad WINS/DNS entries
> > > -OR-
> > > c. Misconfigured network
> > > -OR-
> > > d. Misconfigured SQL Server machine that has multiple netcards.
> > > Aborting DTC Transaction
> > > Releasing DTC Interface Pointers
> > > Successfully Released pTransaction Pointer.
> > >
> > >
DTC Fails
Please Help!...Recently we started seeing DTC failures between two of our
servers. The calling server(A) is Win2003 and the destination (B) is Win2K.
I
t was working a week ago and our Network gurus say nothing has changed on th
e
network.
I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
in the same domain and network segment with no firewall between them. I also
added entries to the host and lmhost files on both.
I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
when run from A, but not from B (it hangs in the bind phase after
successfully completing the RPC portion but no error is retuned)The DTCTeste
r
returns the following when run from either:
Executed: dtctester
DSN: dtctest
User Name: sa
Password:
tablename= #dtc5330
Creating Temp Table for Testing: #dtc5330
Warning: No Columns in Result Set From Executing: 'create table #dtc5330
(ival i
nt)'
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Se
rver
Driver]
Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver
]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.If the 2003 server has had sp1 installed recently, this may be your
problem.You will need to change the security settings in DCOM.
"Joe Loyd" wrote:
> Please Help!...Recently we started seeing DTC failures between two of our
> servers. The calling server(A) is Win2003 and the destination (B) is Win2K
. I
> t was working a week ago and our Network gurus say nothing has changed on
the
> network.
> I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> in the same domain and network segment with no firewall between them. I al
so
> added entries to the host and lmhost files on both.
> I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succee
ds
> when run from A, but not from B (it hangs in the bind phase after
> successfully completing the RPC portion but no error is retuned)The DTCTes
ter
> returns the following when run from either:
> Executed: dtctester
> DSN: dtctest
> User Name: sa
> Password:
> tablename= #dtc5330
> Creating Temp Table for Testing: #dtc5330
> Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> (ival i
> nt)'
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL
Server
> Driver]
> Distributed transaction error'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driv
er]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
>|||Thank you for the response! What additional settings need to be made?
"BitWise" wrote:
[vbcol=seagreen]
> If the 2003 server has had sp1 installed recently, this may be your
> problem.You will need to change the security settings in DCOM.
> "Joe Loyd" wrote:
>|||At the run command type dcomcnfg.exe
Expand Component services >> Computers >> My Computer
Right click My Computer and choose properties
Click on the MSDTC tab
Choose the Security Configuration Button
Under Transaction Manager Communication group, select No Authentication
Required
Click OK
"Joe Loyd" wrote:
[vbcol=seagreen]
> Thank you for the response! What additional settings need to be made?
> "BitWise" wrote:
>
servers. The calling server(A) is Win2003 and the destination (B) is Win2K.
I
t was working a week ago and our Network gurus say nothing has changed on th
e
network.
I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
in the same domain and network segment with no firewall between them. I also
added entries to the host and lmhost files on both.
I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succeeds
when run from A, but not from B (it hangs in the bind phase after
successfully completing the RPC portion but no error is retuned)The DTCTeste
r
returns the following when run from either:
Executed: dtctester
DSN: dtctest
User Name: sa
Password:
tablename= #dtc5330
Creating Temp Table for Testing: #dtc5330
Warning: No Columns in Result Set From Executing: 'create table #dtc5330
(ival i
nt)'
Initializing DTC
Beginning DTC Transaction
Enlisting Connection in Transaction
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL Se
rver
Driver]
Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver
]Invalid
cur
sor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
Aborting DTC Transaction
Releasing DTC Interface Pointers
Successfully Released pTransaction Pointer.If the 2003 server has had sp1 installed recently, this may be your
problem.You will need to change the security settings in DCOM.
"Joe Loyd" wrote:
> Please Help!...Recently we started seeing DTC failures between two of our
> servers. The calling server(A) is Win2003 and the destination (B) is Win2K
. I
> t was working a week ago and our Network gurus say nothing has changed on
the
> network.
> I've set the "TurnOffRpcSecurity" per KB article #827805. Both boxes are
> in the same domain and network segment with no firewall between them. I al
so
> added entries to the host and lmhost files on both.
> I downloaded and ran both DTCPing and DTCTester utilties. DTCPing succee
ds
> when run from A, but not from B (it hangs in the bind phase after
> successfully completing the RPC portion but no error is retuned)The DTCTes
ter
> returns the following when run from either:
> Executed: dtctester
> DSN: dtctest
> User Name: sa
> Password:
> tablename= #dtc5330
> Creating Temp Table for Testing: #dtc5330
> Warning: No Columns in Result Set From Executing: 'create table #dtc5330
> (ival i
> nt)'
> Initializing DTC
> Beginning DTC Transaction
> Enlisting Connection in Transaction
> Error:
> SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL
Server
> Driver]
> Distributed transaction error'
> Error:
> SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driv
er]Invalid
> cur
> sor state
> Typical Errors in DTC Output When
> a. Firewall Has Ports Closed
> -OR-
> b. Bad WINS/DNS entries
> -OR-
> c. Misconfigured network
> -OR-
> d. Misconfigured SQL Server machine that has multiple netcards.
> Aborting DTC Transaction
> Releasing DTC Interface Pointers
> Successfully Released pTransaction Pointer.
>|||Thank you for the response! What additional settings need to be made?
"BitWise" wrote:
[vbcol=seagreen]
> If the 2003 server has had sp1 installed recently, this may be your
> problem.You will need to change the security settings in DCOM.
> "Joe Loyd" wrote:
>|||At the run command type dcomcnfg.exe
Expand Component services >> Computers >> My Computer
Right click My Computer and choose properties
Click on the MSDTC tab
Choose the Security Configuration Button
Under Transaction Manager Communication group, select No Authentication
Required
Click OK
"Joe Loyd" wrote:
[vbcol=seagreen]
> Thank you for the response! What additional settings need to be made?
> "BitWise" wrote:
>
Friday, February 17, 2012
DTC Error
Hi there,
We are having a issue with MSDTC saying that the DTC service is unavailable
when runing a distributed transaction between two WIN2003 servers running
SQL 2000 SP3. Have read all the articles but I am not having much sucess.
Have enabled network DTC access on both servers. The service account is
running under a domain admin account. It seems that one server is the common
donominator as all distributed transactions with this server fails. We read
an article that said to add the reg value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1, this had
the effect of changing the error message to:
Server: Msg 7391, Level 16, State 1, Line 2
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Not sure where to look next, any assistance will be appreciated.
Thanks
Devron Blatchford.
Hi,
I had a similar problem with my Distributed transactions and the problem was
the name resolution within the two servers. I downloaded the MS DTCPing.exe
from microsoft and i found that there wasn't the appropriate name resolution.
Also, if your servers aren't in the same domain, you must trust these domains.
Download the MS DTCPing.exe from the following article
http://support.microsoft.com/default...b;en-us;306843
Andreas
"Devron Blatchford" wrote:
> Hi there,
> We are having a issue with MSDTC saying that the DTC service is unavailable
> when runing a distributed transaction between two WIN2003 servers running
> SQL 2000 SP3. Have read all the articles but I am not having much sucess.
> Have enabled network DTC access on both servers. The service account is
> running under a domain admin account. It seems that one server is the common
> donominator as all distributed transactions with this server fails. We read
> an article that said to add the reg value:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1, this had
> the effect of changing the error message to:
> Server: Msg 7391, Level 16, State 1, Line 2
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Not sure where to look next, any assistance will be appreciated.
> Thanks
> Devron Blatchford.
>
>
We are having a issue with MSDTC saying that the DTC service is unavailable
when runing a distributed transaction between two WIN2003 servers running
SQL 2000 SP3. Have read all the articles but I am not having much sucess.
Have enabled network DTC access on both servers. The service account is
running under a domain admin account. It seems that one server is the common
donominator as all distributed transactions with this server fails. We read
an article that said to add the reg value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1, this had
the effect of changing the error message to:
Server: Msg 7391, Level 16, State 1, Line 2
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Not sure where to look next, any assistance will be appreciated.
Thanks
Devron Blatchford.
Hi,
I had a similar problem with my Distributed transactions and the problem was
the name resolution within the two servers. I downloaded the MS DTCPing.exe
from microsoft and i found that there wasn't the appropriate name resolution.
Also, if your servers aren't in the same domain, you must trust these domains.
Download the MS DTCPing.exe from the following article
http://support.microsoft.com/default...b;en-us;306843
Andreas
"Devron Blatchford" wrote:
> Hi there,
> We are having a issue with MSDTC saying that the DTC service is unavailable
> when runing a distributed transaction between two WIN2003 servers running
> SQL 2000 SP3. Have read all the articles but I am not having much sucess.
> Have enabled network DTC access on both servers. The service account is
> running under a domain admin account. It seems that one server is the common
> donominator as all distributed transactions with this server fails. We read
> an article that said to add the reg value:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOf fRpcSecurity = 1, this had
> the effect of changing the error message to:
> Server: Msg 7391, Level 16, State 1, Line 2
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Not sure where to look next, any assistance will be appreciated.
> Thanks
> Devron Blatchford.
>
>
DTC Error
Hi there,
We are having a issue with MSDTC saying that the DTC service is unavailable
when runing a distributed transaction between two WIN2003 servers running
SQL 2000 SP3. Have read all the articles but I am not having much sucess.
Have enabled network DTC access on both servers. The service account is
running under a domain admin account. It seems that one server is the common
donominator as all distributed transactions with this server fails. We read
an article that said to add the reg value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC\TurnOffRpcSecurity = 1, this had
the effect of changing the error message to:
Server: Msg 7391, Level 16, State 1, Line 2
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Not sure where to look next, any assistance will be appreciated.
Thanks
Devron Blatchford.Hi,
I had a similar problem with my Distributed transactions and the problem was
the name resolution within the two servers. I downloaded the MS DTCPing.exe
from microsoft and i found that there wasn't the appropriate name resolution
.
Also, if your servers aren't in the same domain, you must trust these domain
s.
Download the MS DTCPing.exe from the following article
http://support.microsoft.com/defaul...kb;en-us;306843
Andreas
"Devron Blatchford" wrote:
> Hi there,
> We are having a issue with MSDTC saying that the DTC service is unavailab
le
> when runing a distributed transaction between two WIN2003 servers running
> SQL 2000 SP3. Have read all the articles but I am not having much sucess.
> Have enabled network DTC access on both servers. The service account is
> running under a domain admin account. It seems that one server is the comm
on
> donominator as all distributed transactions with this server fails. We rea
d
> an article that said to add the reg value:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC\TurnOffRpcSecurity = 1, this h
ad
> the effect of changing the error message to:
> Server: Msg 7391, Level 16, State 1, Line 2
> 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 th
e
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Not sure where to look next, any assistance will be appreciated.
> Thanks
> Devron Blatchford.
>
>
We are having a issue with MSDTC saying that the DTC service is unavailable
when runing a distributed transaction between two WIN2003 servers running
SQL 2000 SP3. Have read all the articles but I am not having much sucess.
Have enabled network DTC access on both servers. The service account is
running under a domain admin account. It seems that one server is the common
donominator as all distributed transactions with this server fails. We read
an article that said to add the reg value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC\TurnOffRpcSecurity = 1, this had
the effect of changing the error message to:
Server: Msg 7391, Level 16, State 1, Line 2
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Not sure where to look next, any assistance will be appreciated.
Thanks
Devron Blatchford.Hi,
I had a similar problem with my Distributed transactions and the problem was
the name resolution within the two servers. I downloaded the MS DTCPing.exe
from microsoft and i found that there wasn't the appropriate name resolution
.
Also, if your servers aren't in the same domain, you must trust these domain
s.
Download the MS DTCPing.exe from the following article
http://support.microsoft.com/defaul...kb;en-us;306843
Andreas
"Devron Blatchford" wrote:
> Hi there,
> We are having a issue with MSDTC saying that the DTC service is unavailab
le
> when runing a distributed transaction between two WIN2003 servers running
> SQL 2000 SP3. Have read all the articles but I am not having much sucess.
> Have enabled network DTC access on both servers. The service account is
> running under a domain admin account. It seems that one server is the comm
on
> donominator as all distributed transactions with this server fails. We rea
d
> an article that said to add the reg value:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
DTC\TurnOffRpcSecurity = 1, this h
ad
> the effect of changing the error message to:
> Server: Msg 7391, Level 16, State 1, Line 2
> 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 th
e
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Not sure where to look next, any assistance will be appreciated.
> Thanks
> Devron Blatchford.
>
>
DTC Error
Hi there,
We are having a issue with MSDTC saying that the DTC service is unavailable
when runing a distributed transaction between two WIN2003 servers running
SQL 2000 SP3. Have read all the articles but I am not having much sucess.
Have enabled network DTC access on both servers. The service account is
running under a domain admin account. It seems that one server is the common
donominator as all distributed transactions with this server fails. We read
an article that said to add the reg value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1, this had
the effect of changing the error message to:
Server: Msg 7391, Level 16, State 1, Line 2
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Not sure where to look next, any assistance will be appreciated.
Thanks
Devron Blatchford.Hi,
I had a similar problem with my Distributed transactions and the problem was
the name resolution within the two servers. I downloaded the MS DTCPing.exe
from microsoft and i found that there wasn't the appropriate name resolution.
Also, if your servers aren't in the same domain, you must trust these domains.
Download the MS DTCPing.exe from the following article
http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
Andreas
"Devron Blatchford" wrote:
> Hi there,
> We are having a issue with MSDTC saying that the DTC service is unavailable
> when runing a distributed transaction between two WIN2003 servers running
> SQL 2000 SP3. Have read all the articles but I am not having much sucess.
> Have enabled network DTC access on both servers. The service account is
> running under a domain admin account. It seems that one server is the common
> donominator as all distributed transactions with this server fails. We read
> an article that said to add the reg value:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1, this had
> the effect of changing the error message to:
> Server: Msg 7391, Level 16, State 1, Line 2
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Not sure where to look next, any assistance will be appreciated.
> Thanks
> Devron Blatchford.
>
>
We are having a issue with MSDTC saying that the DTC service is unavailable
when runing a distributed transaction between two WIN2003 servers running
SQL 2000 SP3. Have read all the articles but I am not having much sucess.
Have enabled network DTC access on both servers. The service account is
running under a domain admin account. It seems that one server is the common
donominator as all distributed transactions with this server fails. We read
an article that said to add the reg value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1, this had
the effect of changing the error message to:
Server: Msg 7391, Level 16, State 1, Line 2
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Not sure where to look next, any assistance will be appreciated.
Thanks
Devron Blatchford.Hi,
I had a similar problem with my Distributed transactions and the problem was
the name resolution within the two servers. I downloaded the MS DTCPing.exe
from microsoft and i found that there wasn't the appropriate name resolution.
Also, if your servers aren't in the same domain, you must trust these domains.
Download the MS DTCPing.exe from the following article
http://support.microsoft.com/default.aspx?scid=kb;en-us;306843
Andreas
"Devron Blatchford" wrote:
> Hi there,
> We are having a issue with MSDTC saying that the DTC service is unavailable
> when runing a distributed transaction between two WIN2003 servers running
> SQL 2000 SP3. Have read all the articles but I am not having much sucess.
> Have enabled network DTC access on both servers. The service account is
> running under a domain admin account. It seems that one server is the common
> donominator as all distributed transactions with this server fails. We read
> an article that said to add the reg value:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity = 1, this had
> the effect of changing the error message to:
> Server: Msg 7391, Level 16, State 1, Line 2
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Not sure where to look next, any assistance will be appreciated.
> Thanks
> Devron Blatchford.
>
>
Subscribe to:
Posts (Atom)