asked
Cannot start msftesql service
I recently set up SQL Server 2005 Failover Cluster (64bit, Standard) on an active-passive environment running Windows Server 2008 R2. Installation was successful. The thing is, all services seem to be operating, apart from the MSFTESQL service. I tried to bring the service online though the Surface Configuration Area, the Management Studio, the Failover Cluster Manager, and the services console, but I get errors such as "the dependency service does not exist or has been marked for deletion" and "the operation could not be completed (WinMgmt)". I have not installed SP3 yet. Could you please help me out? Why cannot I start the FullText Sevice?
I would say to get sp3 onboard and then check if its still an issue. You never know ...
when you say you haven't installed SP3 yet, does that mean you are on SP2 or RTM?
Mine too, for what it's worth, hence a +1 to FatherJack's comment. Not that that gets him anything either.
This problem is explained in this [KB article][1]. It usually appears if you have an out of the box installation and did not apply at least SP2 yet. Unfortunately, despite what the KB article suggests, SP2 might not solve it either though SP3 might, but there is another workaround to get your fulltext service up and running: - Open your registry editor - Navigate to HKLM\\System\\CurrentControlSet\\Services\\msftesql - Remove the REG\_MULTI\_SZ item named DependOnService which has the value NTLMSSP (**do not** remove the REG\_MULTI\_SZ item named DependOnService which has the value RPCSS) - Restart the box Your fulltext service should start normally. Oleg [1]:
http://support.microsoft.com/kb/936302
Looks like you are trying to start a service from a previous version of SQL Server. Sql 2005 and 2008 use a different service account naming standard. What SQL Services are currently running? If you look in services.msc, they will all be listed as "SQL Server ..."
@CirqueDeSQLeil I believe that this is an out of the box name for the fulltext service (msftesql). It is just they accidentally left needless dependency in the registry, SP2 (or better) should take care of deleting it, but if it does not then the manual registry tweak should do the trick.
@CirqueDeSQLeil I see where the difference is coming from now, I apologize for unclear comment. The diplay name of the service in question is **SQL Server FullText Search (MSSQLSERVER)**, so you are correct saying that they all start from **SQL Server**. In a mean time it is still **MSFTESQL** service in the registry.
Yes. The actual service names would be a bit different than the display in services.msc. With it being fulltext, the KB article seems like the best resolution.
