Recently, I ran into a problem with SharePoint 2010 Enterprise (with Service Pack 1 and June 2012 Cumulative Update) when creating a new SharePoint farm.
The configuration wizard failed at step 3 when creating the configuration database; while the configuration database and the content DB for the central administration site have been created.
When analyzing the PSConfig log, it says the service SPAdmin (SharePoint 2010 Administration) failed to start.
Task configdb has failed with an unknown exception
Exception: System.InvalidOperationException: Cannot start service SPAdminV4 on computer ‘.’. —> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
— End of inner exception stack trace —
at System.ServiceProcess.ServiceController.Start(String[] args)
at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
at Microsoft.SharePoint.Administration.SPFarm.Join()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
After looking at this error on the Internet, the only things I found was related to SharePoint 2007 after applying a patch on existing farm; nothing about SharePoint 2010 neither when creating a new SharePoint farm.
I finally decided to test a solution provided for SharePoint 2007:
- Below the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- Create a new DWORD value called ServicesPipeTimeout and set his value to 60000 (decimal)
- Restart the server
- Et voilà, the new farm has been successfully created