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]
Showing posts with label msdtc. Show all posts
Showing posts with label msdtc. Show all posts
Wednesday, March 21, 2012
Error on MSDTC on win2k3 to win2k
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 ColefaxI 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.aspx?scid=kb;en-us;816701&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&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.aspx?scid=kb;en-us;816701&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&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
>
>|||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.aspx?scid=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
> 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.aspx?scid=kb;en-us;816701&Product=sql2k
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
> >
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&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
> >
> >
> >
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 ColefaxI 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.aspx?scid=kb;en-us;816701&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&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.aspx?scid=kb;en-us;816701&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&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
>
>|||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.aspx?scid=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
> 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.aspx?scid=kb;en-us;816701&Product=sql2k
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
> >
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&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
> >
> >
> >
Error on MSDTC on win2k3 to win2k
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 ColefaxI 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/defaul...1&Product=sql2k
http://support.microsoft.com/defaul...5&Product=sql2k
http://support.microsoft.com/defaul...2&Product=sql2k
http://support.microsoft.com/defaul...7&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 b
ut
> here are some things that come up in the KB search:
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;816701&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&Product=sql2k[/ur
l]
>
> --
> 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/defaul...id=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/defaul...1&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...5&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...2&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...7&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]
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 ColefaxI 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/defaul...1&Product=sql2k
http://support.microsoft.com/defaul...5&Product=sql2k
http://support.microsoft.com/defaul...2&Product=sql2k
http://support.microsoft.com/defaul...7&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 b
ut
> here are some things that come up in the KB search:
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;816701&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&Product=sql2k[/ur
l]
>
> --
> 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/defaul...id=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/defaul...1&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...5&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...2&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...7&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]
Error on MSDTC after a SQL Server fail-over
Hello
I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
NODE2) with two SQL Server instances (SQL1 and SQL1\2).
Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
MSDTC is configured on a exclusive group and it is running on NODE1.
The Cluster Group also is running on NODE1.
I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
just fine.
I had a problem last night with NODE1, and all the resources (Cluster, SQL1
and MSDTC) failed to NODE2.
After the failover I started getting the error below when trying to execute
a distributed transaction from SQL1\2 to SQL1.
Error: 8510, Severity: 20, State: 2
Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
The error happened during the failover and also after the finish of the
failver.
On SQL1 error log I notice that there was no error messages when it
initialize the MSDTC. Below is the message from the ErrorLog.
"Attempting to initialize Distributed Transaction Coordinator."
To solve the Error I brought up NODE1 back on-line (it failed because of a
network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
procedure I was able to use distributed transactions between SQL1 and SQL1\2.
I would like to know why that problem happened?
I suposed that MSDTC was able to work on cluster and that the MSDTC should
work after a failover.
I would like your help to understand the problem. If you need more
information just let me know.
Regards.
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
Hi Carlos
MSDTC has to be running when SQL is starting. So it's a timing problem. To
be certain, check the log in SQL, and look for messages about finding the
Transaction "Server". It probably states that is was down. SQL will not retry
it afterwards.
If the MSDTC resource was in the same group as the SQL Virtual Server, you
could make SQL dependant of MSDTC, but unfortunately this is not the case.
Chau chau,
Pascalos
"Carlos Selonke" wrote:
> Hello
> I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
> NODE2) with two SQL Server instances (SQL1 and SQL1\2).
> Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
> MSDTC is configured on a exclusive group and it is running on NODE1.
> The Cluster Group also is running on NODE1.
> I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
> just fine.
> I had a problem last night with NODE1, and all the resources (Cluster, SQL1
> and MSDTC) failed to NODE2.
> After the failover I started getting the error below when trying to execute
> a distributed transaction from SQL1\2 to SQL1.
> Error: 8510, Severity: 20, State: 2
> Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
> The error happened during the failover and also after the finish of the
> failver.
> On SQL1 error log I notice that there was no error messages when it
> initialize the MSDTC. Below is the message from the ErrorLog.
> "Attempting to initialize Distributed Transaction Coordinator."
> To solve the Error I brought up NODE1 back on-line (it failed because of a
> network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
> also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
> procedure I was able to use distributed transactions between SQL1 and SQL1\2.
> I would like to know why that problem happened?
> I suposed that MSDTC was able to work on cluster and that the MSDTC should
> work after a failover.
> I would like your help to understand the problem. If you need more
> information just let me know.
> Regards.
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org
I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
NODE2) with two SQL Server instances (SQL1 and SQL1\2).
Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
MSDTC is configured on a exclusive group and it is running on NODE1.
The Cluster Group also is running on NODE1.
I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
just fine.
I had a problem last night with NODE1, and all the resources (Cluster, SQL1
and MSDTC) failed to NODE2.
After the failover I started getting the error below when trying to execute
a distributed transaction from SQL1\2 to SQL1.
Error: 8510, Severity: 20, State: 2
Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
The error happened during the failover and also after the finish of the
failver.
On SQL1 error log I notice that there was no error messages when it
initialize the MSDTC. Below is the message from the ErrorLog.
"Attempting to initialize Distributed Transaction Coordinator."
To solve the Error I brought up NODE1 back on-line (it failed because of a
network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
procedure I was able to use distributed transactions between SQL1 and SQL1\2.
I would like to know why that problem happened?
I suposed that MSDTC was able to work on cluster and that the MSDTC should
work after a failover.
I would like your help to understand the problem. If you need more
information just let me know.
Regards.
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
Hi Carlos
MSDTC has to be running when SQL is starting. So it's a timing problem. To
be certain, check the log in SQL, and look for messages about finding the
Transaction "Server". It probably states that is was down. SQL will not retry
it afterwards.
If the MSDTC resource was in the same group as the SQL Virtual Server, you
could make SQL dependant of MSDTC, but unfortunately this is not the case.
Chau chau,
Pascalos
"Carlos Selonke" wrote:
> Hello
> I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
> NODE2) with two SQL Server instances (SQL1 and SQL1\2).
> Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
> MSDTC is configured on a exclusive group and it is running on NODE1.
> The Cluster Group also is running on NODE1.
> I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
> just fine.
> I had a problem last night with NODE1, and all the resources (Cluster, SQL1
> and MSDTC) failed to NODE2.
> After the failover I started getting the error below when trying to execute
> a distributed transaction from SQL1\2 to SQL1.
> Error: 8510, Severity: 20, State: 2
> Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
> The error happened during the failover and also after the finish of the
> failver.
> On SQL1 error log I notice that there was no error messages when it
> initialize the MSDTC. Below is the message from the ErrorLog.
> "Attempting to initialize Distributed Transaction Coordinator."
> To solve the Error I brought up NODE1 back on-line (it failed because of a
> network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
> also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
> procedure I was able to use distributed transactions between SQL1 and SQL1\2.
> I would like to know why that problem happened?
> I suposed that MSDTC was able to work on cluster and that the MSDTC should
> work after a failover.
> I would like your help to understand the problem. If you need more
> information just let me know.
> Regards.
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org
Subscribe to:
Posts (Atom)