Hi All, Recently I have migrated my SharePoint BackEnd (Database) Server to new hard drive. The reason of migration was to deploy and configure real time database replication by Symantec Veritas. After migration activity I was getting following error message " cannot connect to the configuration database ". But when I execute following steps, this errors message gone and everything got fine 1. Enable Named Pipe from SQL Server Configuration Manager > Protocols for MSSQLSERVER 2. Restart SQL Server (MSSQLSERVER) service (Note: This service was already running and status was set to automatic ) and 3. Start SharePoint Configuration Wizard Now I need to know why every time I have to restart this service? When I turned on my sharepoint server machines in the moring I have to restart this service ( SQL Server (MSSQLSERVER) otherwise same error message appears (cannot connect to the configuration database). After restarting this service everything gets normal. Any help in this regard will be greatly appreciated.

It sounds like the service doesn't have rights to Log On as a service... Look in the Event log under security and see if that user ID is being blocked, this can happen via group policy. If so do the following... 1. On the SQL Server open "Local Security Policy 2. Local Policy and then expand "User Rights Assignment" 3. In the Policy Panel find "Log on as a service" 4. Verify the account running MSSQLServer is in the list of users allowed to Log On. This is where Windows can block the log on when you reboot, it will work withing the current session until reboot. If after that it works you're golden but it could be coming down from a Group Policy as well.. Here are some other links to look at as well.. http://technet.microsoft.com/en-us/library/ms143504.aspx#Configure_services Here is another thread on the same type of issue http://social.technet.microsoft.com/forums/en-US/sharepointadmin/thread/ade926a4-936d-4a00-a0fc-399f40ff7675 Let me know if this helps... Thanks Kris Wagner Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi Kris, Appreciate your help. Let me try your mentioned steps. I will let you know shortly. Regards,

You an reach me at kriswagner at gmail.com as well..Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog

Hi Kris, My problem has been resolved. I made MSSQLSERVER service dependent on another service (VERITAS DG Delayed Import Service). In this way SQL Server first waits for Vertias disk to come online. Regards.

Excellent..!Kris Wagner, MCITP, MCTS Twitter @sharepointkris Blog: http://www.sharepointkris.com/blog