Re: MSDTC - Cluster Resource = Not
From: Mike Rosado [MSFT] (mikeros_at_online.microsoft.com)
Date: 03/06/05
- Next message: John Toner [MVP]: "Re: MNS Cluster Removal"
- Previous message: Rodney R. Fournier [MVP]: "Re: SQL and exchange"
- In reply to: mu: "Re: MSDTC - Cluster Resource = Not"
- Next in thread: Mike Rosado [MSFT]: "Re: MSDTC - Cluster Resource = Not"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 6 Mar 2005 11:14:36 -0600
Mike,
You can use the following syntax from a command prompt window for the errors
and status codes a good majority of the times:
net helpmsg x (x=number)
The [CP] lines are checkpoint files that SQL is trying to write out to the
Quorum disk. One thing I would check, is to ensure if there is an
anti-virus installed on the nodes to exclude the scanning of the whole
Quorum disk and the C:\%windir%\Cluster folder. Or only as a test, try to
completely uninstall the ant-virus just to see if it makes any difference.
You can also try to do an "msdtc -resetlog" (without quotes) from a command
prompt window as indicated in the following article:
243204 Microsoft Distributed Transaction Coordinator (MSDTC) Recovery
http://support.microsoft.com/?id=243204
Or follow the steps outlined in the following article of doing and
"msdtc -uninstall", making sure to delete all the appropriate registry keys
mentioned in the article, then doing an "msdtc -install".
294209 How to rebuild or move MSDTC used with a SQL failover cluster
http://support.microsoft.com/?id=294209
-- Hope this helps, Mike Rosado Windows 2000 MCSE + MCDBA Microsoft Enterprise Platform Support Windows NT/2000/2003 Cluster Technologies ==================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ==================================================== This posting is provided "AS IS" with no warranties, and confers no rights. <http://www.microsoft.com/info/cpyright.htm> -----Original Message----- "mu" <mu@discussions.microsoft.com> wrote in message news:1E9FCAB8-8D37-4ACD-B1F5-914C7209C7F6@microsoft.com... > Thanks a million Mike. I guess I should hav mentioned I am running 2003 and > SQL 2000. > I had already found several mistakes on the NIC cards and those have been > changed but there was nothing that looked extremely bad. > When trying to move a group, the logs consistantly show Q: drive failed > (cluster group) and S: drive failed (shared group). The sqlclstr.log is only > on the one node's local drive, never on the shared drives or other node. I > have sqlstpX.log on both nodes and all the install logs say it was > successful... > Typical errors are: > sqagtres QueryServer Sataus failed status 6 > [CP]... unable to create directory Q:\MSCS\1010\.... error 21 > [CP]... unable to create directory Q:\MSCS\1010\.... error 87 > Physical Disk <Disk Q> Online volumes not ready error 258 > Physical Disk <Disk S> Online volumes not ready error 258 > tcpip is not boound on adapter d61...... > SQLNetworkName(Wookie)>: unable to read resourceData Param error 2 > > Where can I go to get information on the named errors and error codes? Is > there a reference somnewhere? > > > > "Mike Rosado [MSFT]" wrote: > > > Hi Mike, > > > > The problem of any groups not being able to failover has nothing to do with > > MSDTC not configured as a resource or the fact the it may be missing as a > > resource from the dropdown menu. We're talking about 2 totally different > > problems. The only times you would want to configure the Cluster for MSDTC, > > is if you're installing Exchange or SQL on a Cluster or some other > > application requires it. > > > > To resolve the issue of MSDTC, it's going to depend on the version of OS > > you're using. Typically I've been able to help customers resolve their > > problems with MSDTC by simply doing the following syntax from a command > > prompt window on either Windows 2000 or Windows Server 2003: > > > > msdtc -uninstall > > msdtc -install > > > > You will not get any indications if it completed successful or not, it will > > just return to the command prompt. Then if you check Services in the > > Administrative Tools, you should see "Distributed Transaction Coordinator" > > set to Manual. > > > > Once you've completed the uninstall and install of MSDTC on Windows Server > > 2003, you should be able to go in to Cluster Administrator to add a new > > resource and see MSDTC in the dropdown menu. > > > > If it you're on Windows 2000 Advanced Server, once you've completed the > > uninstall and install of MSDTC then you would have to run a utility called > > COMCLUST to configure it for Cluster Administrator. > > > > If uninstall and install of MSDTC doesn't resolve your issue in conjunction > > with articles ID: 301600 or 290624, then you would probably will have to go > > to the extreme of using article ID: 243204 listed below. > > > > 301600 How to configure Microsoft Distributed Transaction Coordinator on a > > http://support.microsoft.com/?id=301600 > > > > 290624 How to configure MSDTC in a Windows 2000 cluster environment > > http://support.microsoft.com/?id=290624 > > > > 243204 Microsoft Distributed Transaction Coordinator (MSDTC) Recovery > > http://support.microsoft.com/?id=243204 > > > > In order to help you resolve the other problem of why any group is not able > > to failover to the other node, we're going to nee a lot more details of what > > you're seeing in the System Event Logs of each node and details of the > > Cluster Logs from both nodes to determine root cause and provide you a > > resolution. > > > > -- > > Hope this helps, > > Mike Rosado > > Windows 2000 MCSE + MCDBA > > Microsoft Enterprise Platform Support > > Windows NT/2000/2003 Cluster Technologies > > > > ==================================================== > > When responding to posts, please "Reply to Group" via your newsreader so > > that others may learn and benefit from your issue. > > ==================================================== > > > > This posting is provided "AS IS" with no warranties, and confers no rights. > > <http://www.microsoft.com/info/cpyright.htm> > > > > -----Original Message----- > > > > "mu" <mu@discussions.microsoft.com> wrote in message > > news:47DE40C3-5C46-4835-8E43-C1EAA7492861@microsoft.com... > > > > > > Please pardon my ignorance once again. I have a cluster that will not > > > failover and I can not move any groups to another node. I have also > > noticed > > > that there is no cluster resource for MSDTC. (No resource, no IP , etc.) I > > > assume the people that built the cluster did not take care of this, but I > > do > > > not know for sure. > > > > > > Questions: > > > > > > 1) Do you have to have MSDTC as a cluster resource, always, on every > > cluster? > > > > > > 2) Can it be fixed without re-installing the cluster from scratch? > > (Please, > > > please say yes, here!) > > > > > > Regards, > > > mike > > > > > >
- Next message: John Toner [MVP]: "Re: MNS Cluster Removal"
- Previous message: Rodney R. Fournier [MVP]: "Re: SQL and exchange"
- In reply to: mu: "Re: MSDTC - Cluster Resource = Not"
- Next in thread: Mike Rosado [MSFT]: "Re: MSDTC - Cluster Resource = Not"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
