|
|
You're in the
sql server clustering
group:MSDTC doesn't work on SQL 2k in W2k3 cluster environment
sql server clustering:
I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1 cluster server recently. After the move, I found two applications that use MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I didn't enable network DTC access on both nodes before I configured MSDTC and then installed the SQL server. To remedy this problem, I deleted the MSDTC resource in the cluster admin, and reconfigured it again after enable the network DTC access on both nodes. However, the MSDTC on the cluster still doesn't work. The installation sequence should configure MSDTC first, then install SQL2K. Does this sequence matter? Do I have to reinstall the SQL server to get MSDTC work? I use DTCTester and get following error: Initializing DTC Beginning DTC Transaction Enlisting Connection in Transaction Error: SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server Driver][SQL Se rver]MSDTC on server 'AWIDB1' is unavailable.' Error: SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid cur sor 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.
Never mind. it worked. I should restart the SQL server after re-configured
the MSDTC resource. Since this server has been in production already, I just wished that every changes would take effect dynamically. [quoted text, click to view] "Jack Zhang" wrote:
> Hi, > > I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1 > cluster server recently. After the move, I found two applications that use > MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I > didn't enable network DTC access on both nodes before I configured MSDTC and > then installed the SQL server. To remedy this problem, I deleted the MSDTC > resource in the cluster admin, and reconfigured it again after enable the > network DTC access on both nodes. However, the MSDTC on the cluster still > doesn't work. The installation sequence should configure MSDTC first, then > install SQL2K. Does this sequence matter? Do I have to reinstall the SQL > server to get MSDTC work? > > I use DTCTester and get following error: > > Initializing DTC > Beginning DTC Transaction > Enlisting Connection in Transaction > Error: > SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server > Driver][SQL Se > rver]MSDTC on server 'AWIDB1' is unavailable.' > Error: > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid > cur > sor 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. >
You are correct in that you should have followed the correct and documented
installation sequence; however, you should be able to do it after the fact. Also know that there is a COM 1.5 bug in Windows 2003. First, after reclustering the MSDTC, did you configure it within its own dedicated Cluster Resource Group? It will require the creation of this group, a dedicated SAN disk, IP, and Network Name cluster resources. Then, you will need to fail that resource back and forth between the nodes to get the resource registry entries to synchronize. You will then need to take the SQL Server IP resource offline, which should bring the resources in that group offline and then bring the group back online. In the SQL Server Error Log, you will see SQL Server attempting to connect to the DTC resource; if it opens the connection, there will be no additional messages. If it has a problem however, it will spit out a "Could not generate resource context" type of error message. That will tell you if this worked or not. If this process fails, one other option would be to run through the ADVANCED section of the SQL Server installation processes. This should verify/generate the necessary registry key dependencies without having to completely reinstall. If this too does not solve the problem, then before you uninstall/reinstall, I would seriously consider opening a Microsoft Product Support Services case, MS PSS. INFO: Availability of Windows Server 2003 COM+ 1.5 Rollup Package 1 http://support.microsoft.com/kb/821751/ You receive error messages when you perform a distributed transaction when you have a SQL Server 2000 virtual server in a Windows Server 2003 clustered environment http://support.microsoft.com/default.aspx?scid=kb;en-us;889706 How to rebuild or move MSDTC used with a SQL failover cluster http://support.microsoft.com/default.aspx?scid=kb;en-us;294209 How to configure Microsoft Distributed Transaction Coordinator on a Windows Server 2003 cluster http://support.microsoft.com/kb/301600/ How to enable network DTC access in Windows Server 2003 http://support.microsoft.com/kb/817064/ Good luck and be sure to let us know how it turns out. Sincerely, Anthony Thomas -- [quoted text, click to view] "Jack Zhang" <JackZhang@discussions.microsoft.com> wrote in message news:46C965C9-5431-460C-92ED-DE5873B57E2F@microsoft.com... > Hi, > > I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 SP1 > cluster server recently. After the move, I found two applications that use > MSDTC didn't work. I realized that I made a mistake when I setup the MSDTC, I > didn't enable network DTC access on both nodes before I configured MSDTC and > then installed the SQL server. To remedy this problem, I deleted the MSDTC > resource in the cluster admin, and reconfigured it again after enable the > network DTC access on both nodes. However, the MSDTC on the cluster still > doesn't work. The installation sequence should configure MSDTC first, then > install SQL2K. Does this sequence matter? Do I have to reinstall the SQL > server to get MSDTC work? > > I use DTCTester and get following error: > > Initializing DTC > Beginning DTC Transaction > Enlisting Connection in Transaction > Error: > SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server > Driver][SQL Se > rver]MSDTC on server 'AWIDB1' is unavailable.' > Error: > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server Driver]Invalid > cur > sor 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. > > Thanks in advance.
Did you set the security on MSDTC through the Component Services Applet?
That is a necessary step after all the steps you listed. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "Jack Zhang" <JackZhang@discussions.microsoft.com> wrote in message news:46C965C9-5431-460C-92ED-DE5873B57E2F@microsoft.com... > Hi, > > I have moved our cluster SQL 2k server from a W2k cluster to a new w2k3 > SP1 > cluster server recently. After the move, I found two applications that use > MSDTC didn't work. I realized that I made a mistake when I setup the > MSDTC, I > didn't enable network DTC access on both nodes before I configured MSDTC > and > then installed the SQL server. To remedy this problem, I deleted the MSDTC > resource in the cluster admin, and reconfigured it again after enable the > network DTC access on both nodes. However, the MSDTC on the cluster still > doesn't work. The installation sequence should configure MSDTC first, then > install SQL2K. Does this sequence matter? Do I have to reinstall the SQL > server to get MSDTC work? > > I use DTCTester and get following error: > > Initializing DTC > Beginning DTC Transaction > Enlisting Connection in Transaction > Error: > SQLSTATE=37000,Native error=8501,msg='[Microsoft][ODBC SQL Server > Driver][SQL Se > rver]MSDTC on server 'AWIDB1' is unavailable.' > Error: > SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server > Driver]Invalid > cur > sor 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. > > Thanks in advance.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |