Gary, 
 
With Win Server 2003, there are some post-installation (or post-upgrade)
configuration changes needed to get this to work.  
 
There are several threads on the List that detail resolutions.  Check
out the post from March 12 entitled "MS SQL -> Oracle ... Distributed
Transaction failed ?" for a quick list of threads.
 
 
Stephen

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Opela, Gary L Contr
OC-ALC/ITMA
Sent: Wednesday, March 21, 2007 1:26 PM
To: [email protected]
Subject: Re: MS SQL on Win 2k -> Win 2k3 issue


** 

Okay, so, my DBA changed something on the server, I'm not sure what yet,
but we now are getting closer. I asked him about DTC, he said he had
already checked it. I am wondering if maybe he had found a configuration
was off or something, a colleague and I had found some documentation
that seemed to document issues similar to mine and sent it off to him.


We now get the following error:

 

ARERR [552] Failure during SQL operation to the database : The ROLLBACK
TRANSACTION request has no corresponding BEGIN TRANSACTION. (SQL Server
3903)

 

Do I have something configured incorrectly on my side?

Thanks,


Gary

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen
Sent: Wednesday, March 21, 2007 10:03 AM
To: [email protected]
Subject: Re: MS SQL on Win 2k -> Win 2k3 issue

 

Has DTC been enabled and configured on the Win 2003 server?

 

Stephen

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Opela, Gary L Contr
OC-ALC/ITMA
Sent: Wednesday, March 21, 2007 10:57 AM
To: [email protected]
Subject: MS SQL on Win 2k -> Win 2k3 issue

** 

Environment:

 

Local Server:     Windows 2k

                        MS SQL 2k

                        Remedy 6.3 no patch

 

Remote Server:

                        Windows 2k3

                        MS SQL 2k

            

 

Every since the server guys upgraded the remote server to 2k3, it has
broken my functionality to connect to it via a linked database using
remedy. It works just fine when using SQL Query Analyzer, it just
doesn't work with Remedy. The DBAs can see my connection come through,
just not the query.

 

I know I've already posted on this, but I have new data in that I've
found out what was upgraded, Windows 2k server -> Windows 2k3 server.

 

This upgrade is the only thing that changed, and then my linked database
stopped working.

 

I was wondering if anyone out there has gone through the same process
and had similar results?


Thanks

            

__20060125_______________________This posting was submitted with HTML in
it___

__20060125_______________________This posting was submitted with HTML in
it___ __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