Hello, experts!
On Sunday, as part of routine maintenance, we had to shut down our clustered servers. When we tried to bring them back up, they would not recognize our array unless we disabled the cluster service. It was agreed that we should disable the cluster service (it's caused nothing but problems due to poor implementation and vendor software support), but now we're having difficulties with SQL Server. We're having several "small" problems (i.e. unable to remove our old instance of SQL Server), but the main issue is that our client cannot connect to our server. They are able to ping us and connect to our development database (not affected by the failure), but cannot connect to the production database. Currently, the most obvious difference between production and development is that development displays a green icon (running) for both Distributed Transaction Coordinator and Full-Text Search in Support Services (Enterprise Mgr), whereas production has a red (stopped) icon for both. Also, we previously identified that MSDTC was not running and that it was inaccessible in Component Services, so we uninstalled and reinstalled. We were then able to access MSDTC in Component Services. That said, when I attempt to start DTC or Full-Text Search in Support Services, I receive the following error message:
An error 1722 - (The RPC server is unavailable) occurred while performing this service operation on the MSDTC service.
I've troubleshot this error message and verified that both RPC and DTC are started in the Services menu, that both services are set to start automatically and that both are using "Network Service" login. At this point, I have no idea what could possibly be causing this problem or if this could even be related to our client's inability to connect to our SQL database. We're running SQL Server 2000 SP4 on Win Server 2003 Dell machines. Any assistance is much appreciated.
Thanks!
Can you discuss what steps you took to disable the cluster service? Also, was this MSCS, Veritas Cluster or other?
When an instance is installed as clustered, the configuration is set up to only run under the cluster. This may be causing some of the troubles.
|||Hi Kevin,
Thank you for the response. We're using MSCS. We disabled the Cluster Disk Driver in Device Manager, then disabled the Cluster Service in Services.
How would we go about utilizing a previously clustered server in a non-clustered capacity? Would we have to rebuild the server with a clean install of Windows Server and SQL Server?
|||Did you cluster MS DTC? If not, that is most likely your issue. On a clustered implementation, DTC needs to be clustered as well. It's done at the OS level.
Try this: http://support.microsoft.com/kb/294209/ or http://support.microsoft.com/kb/243204/en-us
No comments:
Post a Comment