Monday, February 20, 2012

MSDTC and Full Text Indexing

Happy Christmas everyone,
I have just visited an active/active win2K(sp2) and SQL 2000(sp3a) cluster
that is not too happy. The virtual servers will not fail over between the
nodes as the MSDTC will not restart if moved. Full text indexing exists
only in one virtual server and needs to be on both instances.
I suspect that comclust wasn't run at installation but has been subsequently
run on one node only. Is there a safe way of now recreating the MSDTC or
reinstalling somehow without reinstalling SQL?
Thanks in advance.
Tim
I never wish I was not what I was not when I didn't wish what I was not was
not what I am not.
Hi Tim!
Yes, you can remove and reinstall MSDTC 'underneath' SQL.
However, the health of this cluster sounds pretty suspect!
I would caution you to BACK EVERYTHING UP before you do anything to this
cluster.
:-)
All system db's...everything.
If it's not moving, back it up!
Ok, with that said, you can follow this KB article on moving and rebuilding
the MSDTC resource:
294209 How to rebuild or move MSDTC used with a SQL failover cluster
There is also this article:
Microsoft Distributed Transaction Coordinator (MSDTC) Recovery Techniques
in Windows 2000 Cluster Server (243204)
Which is not really SQL specific.
As for the FTSearch issue...that is a little more complicated.
Generally there are two reasons FTS doesn't work in a cluster.
1. Search setup was not successful
2. You have missing registry keys.
For number 1, you will need to do some detective work.
First collect the most recent sqlstp#.log from both nodes.
Look for the searchsetup.exe section.
Any errors? If there is an error number, go to a cmd prompt, type net
helpmsg <errornumber>
What's the error? This will be important. At that point you should engage
PSS to rebuild FTS, as it's tricky at best.
For number 2, follow this article to confirm you have the correct registry
entries for FTS:
http://support.microsoft.com/default...B;EN-US;810056
INF: You Must Use Resource-Specific Registry Keys for SQL Server Cluster
Resources (810056)
If missing, put them in there. If that doesn't fix it, again, call PSS,
you probably have more at play than just missing registry keys.
Hope your sickly cluster recovers!
Thanks!
Donna Lambert
SQL Server Product Support

No comments:

Post a Comment