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:
[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:

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.
> > >
> > >

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:
>

DSN vs login authentication

Hello everybody!
I've created a DSN from a WIN2K Pro client to connect to a SQL Server 7.0
running on a WIN2K Server with domain controller.
The SQL Server authentication mode on the server machine is "Mixed mode"
Inside the client DSN configuration I've specified that the Authentication
Mode is SQL Server Mode, so I've entered the correct values for Access Id
and Password (I've already tested them connecting directly on the server
machine from query analyzer).
If I test this DSN connection everything works fine.
But if I run my VisualFoxPro Application (that use surely the DSN I've set
up) and appears the "sql server connection dialog box" when I click on "Ok"
I obtain the following error:
...
[Microsoft]ODBC-SQL Server Drive][Sql Server][Login failed for u
ser "server
name/user"]
as the Authentication Mode was "Windows" (trusted connection) and not "SQL
Server" as truly is.
Note that on the same network I've others WIN2K box with the same setup
(same MDAC 2.6, same domain user properties, same DSN setup) and for them I
don't have any problems.
Is there a way to force the connection process from the client to the server
to use always "SQL server authentication mode" (if DSN is not enough)?!?!
Can anyone help me? Thanks in advance!
Riccardo Piccini
Supporto Software
EDP SERVICE SRLCheck the version of the SQL Server ODBC driver on the client machine. It
sounds like you are running into a problem with sqlsrv32.dll version
2000.80.194. This version ignores SQL authentication and uses NT
authentication. The only way to resolve the problem is to upgrade teh
version of MDAC. I believe the problem was resolved in MDAC 2.6 SP2.
Rand
This posting is provided "as is" with no warranties and confers no rights.

DSN vs login authentication

Hello everybody!
I've created a DSN from a WIN2K Pro client to connect to a SQL Server 7.0
running on a WIN2K Server with domain controller.
The SQL Server authentication mode on the server machine is "Mixed mode"
Inside the client DSN configuration I've specified that the Authentication
Mode is SQL Server Mode, so I've entered the correct values for Access Id
and Password (I've already tested them connecting directly on the server
machine from query analyzer).
If I test this DSN connection everything works fine.
But if I run my VisualFoxPro Application (that use surely the DSN I've set
up) and appears the "sql server connection dialog box" when I click on "Ok"
I obtain the following error:
...
[Microsoft]ODBC-SQL Server Drive][Sql Server][Login failed for user "server
name/user"]
as the Authentication Mode was "Windows" (trusted connection) and not "SQL
Server" as truly is.
Note that on the same network I've others WIN2K box with the same setup
(same MDAC 2.6, same domain user properties, same DSN setup) and for them I
don't have any problems.
Is there a way to force the connection process from the client to the server
to use always "SQL server authentication mode" (if DSN is not enough)?!?!
Can anyone help me? Thanks in advance!
Riccardo Piccini
Supporto Software
EDP SERVICE SRL
Check the version of the SQL Server ODBC driver on the client machine. It
sounds like you are running into a problem with sqlsrv32.dll version
2000.80.194. This version ignores SQL authentication and uses NT
authentication. The only way to resolve the problem is to upgrade teh
version of MDAC. I believe the problem was resolved in MDAC 2.6 SP2.
Rand
This posting is provided "as is" with no warranties and confers no rights.