RESOLVED!!!

 

With much help from my DBA, I gave him a ton of documentation on the issue and 
he was able to fix the remote server's configurations.

 

Below are the steps he performed in detail, so if anyone in the future has this 
issue, hopefully they won't have to spend almost two weeks working it.

 

Step One: Enable Network DTC Access

1.      Click Start, point to Control Panel, and then click Add or Remove 
Programs. 

2.      Click Add/Remove Windows Components. 

3.      Select Application Server, and then click Details. 

4.      Select Enable network DTC access...de-select all others, and then click 
OK. 

5.      Click Next. 

6.      Click Finish. 

7.      Stop and then restart the Distributed Transaction Coordinator service. 

8.      Stop and restart Microsoft SQL Server and SQL Server Agent

 

Step Two: Disable RPC Security for MSDTC Service on SQL Server

1.      Click Start, click Run, type in "Regedt32", and click OK.

2.      Select HKEY_LOCAL_MACHINE, then SOFTWARE, then Microsoft.

3.      Right-click on MSDTC, point to Add, then select DWORD Value.

4.      Rename the key from the default New Value #1 to TurnOffRpcSecurity.

5.      Double-click the new key and change the value to 1.

6.      Close the Registry Editor and restart the SQL Server

 

Step Three:  Enable MSDTC to allow the network transaction. 

1.      Start | Program Files | Admin Tools | Component Services

2.      In the Component Services window, expand Component Services, expand 
Computers, and then expand My Computer. 

3.      Right-click My Computer, and then click Properties. 

4.      In the My Computer Properties dialog box, click Security Configuration 
on the MSDTC tab. 

5.      In the Security Configuration dialog box, click to select the Network 
DTC Access check box. 

6.      To allow the distributed transaction to run on this computer from a 
remote computer, click to select the Allow Inbound check box. 

7.      To allow the distributed transaction to run on a remote computer from 
this computer, click to select the Allow Outbound check box. 

8.      Under the Transaction Manager Communication group, click to select the 
No Authentication Required option. 

9.      In the Security Configuration dialog box, click OK. 

10.  In the My Computer Properties dialog box, click OK. 

 

 

________________________________

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, March 21, 2007 3:48 PM
To: [email protected]
Subject: Re: MS SQL on Win 2k -> Win 2k3 issue

 

You need to restart the SQL server after turning off ANSI_WARNINGS. Forgot to 
mention that..
 

Joe

 

----- Original Message ----
From: "Opela, Gary L Contr OC-ALC/ITMA" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, March 21, 2007 4:26:30 PM
Subject: Re: MS SQL on Win 2k -> Win 2k3 issue

Well, I'm at a loss....


I've tried everything I can find on ARSList, Nabble, mattrienfelt.com, as well 
as MS website.



I have asked the DBA if he can check with a  server guy to see if the remote 
server has windows firewall running. One of MS's articles said the firewall 
blocks outgoing DTC traffic, which also seems that it could cause what I'm 
seeing.



For some reason, I'm doubting that this will resolve anything.



Oh, by the way, I opened my ticket with remedy 8 days ago, 7 days ago they 
asked me for log files, which I promptly sent them, and they've yet to respond 
to me, even though I've emailed them twice more since then... What great 
support. They can probably see that I'm working on it here, so they've put it 
on hold I'll bet...



Gary



________________________________

From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Joe DeSouza
Sent: Wednesday, March 21, 2007 3:14 PM
To: [email protected]
Subject: Re: MS SQL on Win 2k -> Win 2k3 issue



Try switching off ANSI warnings.. It may help..


Joe



----- Original Message ----
From: "Opela, Gary L Contr OC-ALC/ITMA" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, March 21, 2007 3:50:00 PM
Subject: Re: MS SQL on Win 2k -> Win 2k3 issue

** 

Wow, thanks. I can believe that, judging by the mass confusion of all of my 
DBAs.



Stephen has pointed out several other posts where users had similar issues. I’m 
going through and trying all of their different things right now that helped 
them. So far, no luck. I’ll look at the MS article below in a minute. I already 
sent one MS article I found on similar issues with DST to my DBA, and he tried 
configuring the DST service the same way that the article said, and that’s what 
got us to where we were. Before I started getting this error, my query would 
just hang.



I’ll keep you guys posted.



________________________________

From: Action Request System discussion list(ARSList) [mailto: 
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
<http://www.arslist.org/>  ARSlist:"Where the Answers Are"

 

 

________________________________

Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games. 
<http://us.rd.yahoo.com/evt=49936/*http:/videogames.yahoo.com> 

__20060125_______________________This posting was submitted with HTML in it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to