I am currently having issue with MSDTC.
I have two servers, one running win2k3 server and the other running win2k
advanced server. Both are also running MSSQL2k.
I have a script that runs on the win2k3 server, that updates one of it's
tables, based on information accessed through a linked server to the win2k
machine. No updating is done to the win2k machine, only selection. All
updates occur to the data on the win2k3 machine, which is were the script is
running.
When I execute this script, I get the following error.
"New transaction cannot enlist in the specified transaction coordinator"
When both machines are win2k, this works without any problem.
Both servers have a linked server connection to each other. All other
scripts that work across this link work fine, as long as they are not in a
transaction.
I am running out of ideas on how to get this working, does anyone have any
ideas. Any assistance would be greatly appreciated.
Thank you
Clint Colefax
I would say it is pretty likely DTC is turned off on the Win2003 machine but
here are some things that come up in the KB search:
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> I am currently having issue with MSDTC.
> I have two servers, one running win2k3 server and the other running win2k
> advanced server. Both are also running MSSQL2k.
> I have a script that runs on the win2k3 server, that updates one of it's
> tables, based on information accessed through a linked server to the win2k
> machine. No updating is done to the win2k machine, only selection. All
> updates occur to the data on the win2k3 machine, which is were the script
is
> running.
> When I execute this script, I get the following error.
> "New transaction cannot enlist in the specified transaction coordinator"
> When both machines are win2k, this works without any problem.
> Both servers have a linked server connection to each other. All other
> scripts that work across this link work fine, as long as they are not in a
> transaction.
> I am running out of ideas on how to get this working, does anyone have any
> ideas. Any assistance would be greatly appreciated.
> Thank you
> Clint Colefax
|||Thank you for your response.
DTC is running on both servers, that was the first thing I checked. The 3
three knowledge base article below I have tried, most of these settings were
already set, or in the case of the win2k machine, do not exist. Many of the
security settings for DTC were added Win2k3. But I have read article stating
that this security is ignored if one of the machines is detected as Win2k.
I will look into the 3rd article.
If you have any other idea, they would be greatly appreciated.
Thank you
Clint Colefax
"Andrew J. Kelly" wrote:
> I would say it is pretty likely DTC is turned off on the Win2003 machine but
> here are some things that come up in the KB search:
> http://support.microsoft.com/default...&Product=sql2k
> http://support.microsoft.com/default...&Product=sql2k
> http://support.microsoft.com/default...&Product=sql2k
> http://support.microsoft.com/default...&Product=sql2k
>
> --
> Andrew J. Kelly SQL MVP
>
> "Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
> news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> is
>
>
|||Sorry those would have been my guess. If no one else pipes up you might
want to give MS PSS a call. Even if it isn't a bug it might be worth the
$250.00 or so to get the systems up as soon as possible.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:0AEBF2EC-9455-47B1-BB30-56F41CB100D0@.microsoft.com...
> Thank you for your response.
> DTC is running on both servers, that was the first thing I checked. The 3
> three knowledge base article below I have tried, most of these settings
were
> already set, or in the case of the win2k machine, do not exist. Many of
the
> security settings for DTC were added Win2k3. But I have read article
stating[vbcol=seagreen]
> that this security is ignored if one of the machines is detected as Win2k.
> I will look into the 3rd article.
> If you have any other idea, they would be greatly appreciated.
> Thank you
> Clint Colefax
>
> "Andrew J. Kelly" wrote:
but[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
message[vbcol=seagreen]
win2k[vbcol=seagreen]
it's[vbcol=seagreen]
win2k[vbcol=seagreen]
script[vbcol=seagreen]
coordinator"[vbcol=seagreen]
in a[vbcol=seagreen]
any[vbcol=seagreen]
No comments:
Post a Comment