June 20, 2005 at 11:54 am
I have been researching this, but have not yet resolved my problem. Though Server 1 can successfully query Server 2, I cannot get DTC to work. I only need for Server 1 to be able to execute a DTC on Server 2. Please help!
NOTE: The SQL Service is run as a non-privleged user
(Sorry for the length of this message - just trying to show that I have tried a number of tests...)
Server 1:
Name: ssel-sched
OS: Windows Server 2003
IP1: 192.168.168.200
IP2: 192.168.1.241
DB: SQL Server 2000 SP3a
MSDTC: Installed, running as Network Service account
MSDTC configuration: Network DTC Access (checked), Network Administration (checked), Network Tranactions (checked), XA Transactions (checked)
Server 2:
Name: ssel-sched
OS: Windows Server 2003 SP1
IP1: 192.168.168.100
IP2:
DB: SQL Server 2000 SP3a
MSDTC: Installed, running as Network Service account
MSDTC configuration: Network DTC Access (checked), Allow Remote Clients (checked), Allow Remote Administration (checked), Allow Inbound (checked), Allow Outbound (checked), No Authentication Required (selected), XA Transactions (checked)
Network configuration:
Both machine sit on a private network. There is no firewall between the machines.
On ssel-sched, using sp_helpserver:
SSEL-SCHED SSEL-SCHED rpc,rpc out,use remote collation 0 NULL 0 0
SSEL-SEC SSEL-SEC rpc,rpc out,data access 1 NULL 0 0
Results of DTCping:
From ssel-sched:
Platform:Windows 2003
Security settings for DTC under Windows 2003
NetworkDtcAccess :true
NetworkDtcAccessAdmin :true
NetworkDtcAccessClients :false
NetworkDtcAccessTransactions:true
NetworkDtcAccessTip :false
XaTransactions :true
DomainControllerState :false
AccountName :NT Authority\NetworkService
TurnOffRpcSecurity :false
IP Configure Information
Host Name . . . . . . . . . : ssel-sched
DNS Servers . . . . . . . . : 141.213.4.4
141.213.24.5
Node Type . . . . . . . . . :
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : no
WINS Proxy Enabled. . . . . : no
NetBIOS Resolution Uses DNS : no
Ethernet adapter {CB9992BC-F7FB-4D90-A198-47D2EF4EB516}:
Description . . . . . . . . : Intel(R) PRO/1000 MT Network Adapter
Physical Address. . . . . . : 00-30-48-73-F9-2A
DHCP Enabled. . . . . . . . : no
IP Address. . . . . . . . . : 192.168.168.200
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.168.1
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . : 0.0.0.0
Secondary WINS Server . . . : 0.0.0.0
Lease Obtained. . . . . . . : Thu Jan 01 00:00:00 1970
Lease Expires . . . . . . . : Thu Jan 01 00:00:00 1970
Ethernet adapter {0166AAD1-2701-41AE-92C2-E5F7208C88E9}:
Description . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . : 00-30-48-73-F9-2B
DHCP Enabled. . . . . . . . : no
IP Address. . . . . . . . . : 192.168.1.241
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . : 0.0.0.0
Secondary WINS Server . . . : 0.0.0.0
Lease Obtained. . . . . . . : Thu Jan 01 00:00:00 1970
Lease Expires . . . . . . . : Thu Jan 01 00:00:00 1970
++++++++++++lmhosts.sam++++++++++++
++++++++++++hosts ++++++++++++
127.0.0.1 localhost
192.168.1.2 ssel-kiosk1
192.168.1.3 ssel-kiosk2
192.168.1.4 ssel-kiosk3
192.168.1.60 ssel-kiosk4
192.168.1.101 wago-test
192.168.1.102 wago-bypass
192.168.1.241 ssel-sched
192.168.1.242 ssel-apps
192.168.1.243 ssel-test
++++++++++++++++++++++++++++++++++++++++++++++
DTCping 1.8 Report for SSEL-SCHED
++++++++++++++++++++++++++++++++++++++++++++++
Firewall Port Settings:
Port:4000-4010
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
06-20, 12:27:10.380-->Start DTC connection test
Name Resolution:
ssel-sec-->192.168.168.100-->SSEL-SEC
06-20, 12:27:15.208-->Start RPC test (SSEL-SCHED-->ssel-sec)
RPC test is successful
Partner's CID:7461CE5E-7FC6-4937-9E13-547724C76F04
++++++++++++RPC test completed+++++++++++++++
06-20, 12:27:35.943-->RPC server:SSEL-SCHED received following information:
Network Name: ssel-sched
Source Port: 4009
Partner LOG: SSEL-SEC2584.log
Partner CID: 7461CE5E-7FC6-4937-9E13-547724C76F04
++++++++++++Start Reverse Bind Test+++++++++++++
Received Bind call from SSEL-SEC
Network Name: ssel-sched
Source Port: 4009
Hosting Machine:SSEL-SCHED
06-20, 12:27:35.974-->Trying to Reverse Bind to SSEL-SEC...
Test Guid:7461CE5E-7FC6-4937-9E13-547724C76F04
Name Resolution:
SSEL-SEC-->192.168.168.100-->SSEL-SEC
Reverse Binding success: SSEL-SCHED-->SSEL-SEC
++++++++++++Reverse Bind Test ENDED++++++++++
06-20, 12:27:40.489-->Called POKE from Partner:SSEL-SEC
Network Name: ssel-sched
Source Port: 4009
Hosting Machine:SSEL-SCHED
++++++++++++Start DTC Binding Test +++++++++++++
Trying Bind to SSEL-SEC
06-20, 12:27:40.489-->SSEL-SCHED Initiating DTC Binding Test....
Test Guid:1F6869DA-44DB-42FE-9C14-3359F788C6C1
Received reverse bind call from SSEL-SEC
Network Name: ssel-sched
Source Port: 4009
Hosting Machine:SSEL-SCHED
Binding success: SSEL-SCHED-->SSEL-SEC
++++++++++++DTC Binding Test END+++++++++++++
From ssel-sec:
Platform:Windows 2003
Security settings for DTC under Windows 2003
NetworkDtcAccess :true
NetworkDtcAccessAdmin :true
NetworkDtcAccessClients :false
NetworkDtcAccessTransactions:true
NetworkDtcAccessTip :false
XaTransactions :true
DomainControllerState :false
AccountName :NT Authority\NetworkService
TurnOffRpcSecurity :true
IP Configure Information
Host Name . . . . . . . . . : ssel-sec
DNS Servers . . . . . . . . : 141.213.4.4
141.213.4.5
Node Type . . . . . . . . . :
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : no
WINS Proxy Enabled. . . . . : no
NetBIOS Resolution Uses DNS : no
Ethernet adapter {7EB4FBE3-8F31-4C3C-9B80-DE15653C285F}:
Description . . . . . . . . : Intel(R) PRO/1000 MT Network Adapter
Physical Address. . . . . . : 00-30-48-72-26-4E
DHCP Enabled. . . . . . . . : no
IP Address. . . . . . . . . : 192.168.168.100
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.168.1
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . : 0.0.0.0
Secondary WINS Server . . . : 0.0.0.0
Lease Obtained. . . . . . . : Thu Jan 01 00:00:00 1970
Lease Expires . . . . . . . : Thu Jan 01 00:00:00 1970
Ethernet adapter {E5FEBE8A-0901-40CF-8AD8-A2A30A84F6BD}:
Description . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . : 00-30-48-72-26-4F
DHCP Enabled. . . . . . . . : yes
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
DHCP Server . . . . . . . . : 255.255.255.255
Primary WINS Server . . . . : 0.0.0.0
Secondary WINS Server . . . : 0.0.0.0
Lease Obtained. . . . . . . : Mon May 09 20:37:16 2005
Lease Expires . . . . . . . : Mon May 09 21:37:16 2005
++++++++++++lmhosts.sam++++++++++++
++++++++++++hosts ++++++++++++
127.0.0.1 localhost
++++++++++++++++++++++++++++++++++++++++++++++
DTCping 1.8 Report for SSEL-SEC
++++++++++++++++++++++++++++++++++++++++++++++
RPC server is ready
06-20, 12:27:44.156-->RPC server:SSEL-SEC received following information:
Network Name: ssel-sec
Source Port: 1694
Partner LOG: SSEL-SCHED324.log
Partner CID: 1F6869DA-44DB-42FE-9C14-3359F788C6C1
++++++++++++Validating Remote Computer Name++++++++++++
06-20, 12:28:00.328-->Start DTC connection test
Name Resolution:
ssel-sched-->192.168.168.200-->SSEL-SCHED
06-20, 12:28:04.890-->Start RPC test (SSEL-SEC-->ssel-sched)
RPC test is successful
Partner's CID:1F6869DA-44DB-42FE-9C14-3359F788C6C1
++++++++++++RPC test completed+++++++++++++++
++++++++++++Start DTC Binding Test +++++++++++++
Trying Bind to ssel-sched
06-20, 12:28:04.890-->SSEL-SEC Initiating DTC Binding Test....
Test Guid:7461CE5E-7FC6-4937-9E13-547724C76F04
Received reverse bind call from ssel-sched
Network Name: ssel-sec
Source Port: 1694
Hosting Machine:SSEL-SEC
Binding success: SSEL-SEC-->ssel-sched
++++++++++++DTC Binding Test END+++++++++++++
++++++++++++Start Reverse Bind Test+++++++++++++
Received Bind call from ssel-sched
Network Name: ssel-sec
Source Port: 1694
Hosting Machine:SSEL-SEC
06-20, 12:28:09.453-->Trying to Reverse Bind to ssel-sched...
Test Guid:1F6869DA-44DB-42FE-9C14-3359F788C6C1
Name Resolution:
ssel-sched-->192.168.168.200-->SSEL-SCHED
Reverse Binding success: SSEL-SEC-->ssel-sched
++++++++++++Reverse Bind Test ENDED++++++++++
Result of DTCtester running on ssel-sched:
(Note: the DSN was created and tested and worked properly)
C:\Program Files\dtcping>dtctester sselsec sa
DSN: sselsec
User Name: sa
Password:
Creating Temp Table for Testing: #dtc9119
Warning: No Columns in Result Set From Executing: 'create table #dtc9119 (ival int)'
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 cursor 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.
June 23, 2005 at 8:00 am
This was removed by the editor as SPAM
June 23, 2005 at 9:21 am
I seriously doubt this is your problem, but we ran into the same error message due to two problems on our system, so these might help you. First was the DTC timeout settings were way too low. Of course the core problem there was that our procedures were running far too long, not that DTC was configured incorrectly. However as part of the overall troubleshooting, in addition to tuning the procedures (and restructuring tables, indexes, etc.) we did expand the DTC timemout settings. It helped. We also got that problem due to DTC having too small a cache allocation. We expanded that a bit and it eliminated a lot of these errors.
The main problem is, that we were getting the same error for both problems, "cannot enlist in the specified transaction", even though it was two completely unrelated problems. I think that regardless of the issue, this is the fallback setting for error reporting in DTC.
Good luck.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
June 23, 2005 at 9:48 am
Found a solution - I had to simply create the registry key (DWORD)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\TurnOffRpcSecurity
and set its value to 1
July 29, 2005 at 7:18 am
I found this same solution and it got things working. The only question that remains for me is 'what are the ramifications of turning off Rpc Security?'.
From articles that I found, it appears that this allows a communication channel to be established between Win2003 and a remote computer running Win2000 or between domains that don't have a trusted relationship. The communication on the network between DCTs falls back to a non-authentication or non-encrypted communication if a secure one cannot be established.
Can anyone explain what the possible problems are if Rpc Security is turned off?
April 18, 2006 at 6:40 pm
I also have this problem - I have:
1) turned off Windows Firewall
2) checked appropriate settings in dcomcnfg.exe
3) checked that DTCPing works
My Windows XP SP2 machine STILL will not run a simple test ASP page that calls COM+ objects. Annoyingly, another machine I'm using to test VS2005 will run this test page fine.
(getting the project to work under VS2005 is a different matter...)
Any more solutions would be appreciated.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply