Hi there guys

I am having a problem with a clustered default instance.
During the process of changing the statup parameters with the intention of
moving the Master to a new LUN. The SQL service failed for an unrelated
reason, however the startup parameters at that stage were deleted (Blank, no
more ...).

Restarting the clustered service without these causes the service to fail,
obviously.

I have attempted to add the startup argument registry keys back to the
registry, however everytime I restart the service failes and the registry
keys are deleted.

I can add the keys and start a local instance of SQL from from the
commandline and it works, so the key values are correct.

Regards

Gary Hope
iSolve Business Solutions

News.telkomsa.net wrote:
As it should be, how about explicitly denying the cluster/sqlservice
service account to modify the startup key's and yust give them read rights?

--
Hans

The change you have implemented is not trivial to correct on a cluster.

1. You could uninstall and reinstall to the new location
2. Change the drive mapping on the new LUN to match the original location
3. Hack the registry to correct the pathing

There are risks involved with all of these options and I would suggest
opening a case with SQL Server product support to resolve the issue

Dave Whitney
SQL Support