Error in step 5 - Sharepoint 2010 Configuration Wizard
-
Monday, November 23, 2009 7:28 PMI can't proced througt the step 5 of the configuration wiz.
I have installed in a VM.
Please, i need some help..
The error:
After installing the Sharepoint Search Server in the wizard. Gives the following exception.
Failed to register SharePoint services. An exception of type System.ServiceProcess.TimeoutException was thrown. Additional exception information: Time out has expired and the operation has not been completed. System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName) at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start() at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start) at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision() at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run() at
Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
AOM
All Replies
-
Monday, November 23, 2009 8:12 PMThis error is likely to appear when you don't have enough memory. How much did you give to the VM? And can you check memory usage? Is SQL Server (Express) also on the same VM?
-
Tuesday, November 24, 2009 12:39 PM
I gave 4Gb Ram. And the SQL server was installed with the Pre-Requisites, in the same machine.
Do you have any idea?
AOM
Maia -
Tuesday, November 24, 2009 3:14 PMSame issue for me !
2Gb Ram in a standalone installation
Task services has failed with an unknown exception
Exception: System.ServiceProcess.TimeoutException: Le délai d'attente a expiré et l'opération n'a pas été terminée.
à System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
à Microsoft.SharePoint.Win32.SPAdvApi32.StartService(String strServiceName)
à Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Start()
à Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
à Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Provision()
à Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject)
à Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject)
à Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo)
à Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run()
à Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask() -
Tuesday, November 24, 2009 3:40 PM
I think the minum is 4GB.
But i have 4Gb and the problem is still the same.
Any Help?
Maia -
Tuesday, November 24, 2009 9:53 PMI am running into the same issue on Windows Server 2008 R2 box, with all pre-requisites, hot fix running as a DC. The machine has 4GB of RAM.
-
Wednesday, November 25, 2009 8:40 AM
The min memory is not 4GB when you put SQL Server on the same box. We don't have a hard limit that block you from install, in some scenarios it will work. But, there are some scenarios SQL eating too much memory and leave SharePoint/IIS to die. My suggestion is, restart the machine, don't run anything else before you start the setup, and run the wizard again.
-
Wednesday, November 25, 2009 2:22 PM
Is it possible to set the timeout value to a different time?
Thank you
Maia -
Wednesday, November 25, 2009 2:52 PM
I had the same problem when I installed the standalone version. I removed the Sharepoint 2010 Add / Remove Programs and installed again with the way complete (not remove SQL Server 2008). I run the Configuration Wizard and it worked perfectly.
Wesley Dias -
Wednesday, November 25, 2009 3:25 PM
I installed the Sharepoint 2010, not in a single server mode, and it worked. I installed Sharepoint and SQL Server 2008 in a VM with 4 GB.
Is the SQL Built in not working?
Maia -
Wednesday, November 25, 2009 4:04 PM
I follow this topic : http://blogs.msdn.com/opal/archive/2009/11/16/installation-notice-for-sharepoint-2010-public-beta.aspx
And it works perfectly.... for the moment.
I think all hotfix mentionned in the topic is necessary.
For information, i've installed SharePoint 2010 on Windows 2008 R2 VMWare with :
- 2Gb RAM
- SQL Server 2008 Ent SP1 and cumulative update May 2008 (KB976761)
- Proposed As Answer by Paul AndrewMicrosoft Employee Thursday, November 26, 2009 1:41 AM
- Marked As Answer by Mike Walsh FIN Thursday, November 26, 2009 7:23 AM
-
Wednesday, November 25, 2009 10:36 PMFirst min RAM should be 4GB, although I have done SP2010 install with 2Gb.
Also for step 5, maybe this post which involves registry changes may help.
http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/ec0239c1-4451-46dc-ac3a-baffa006c024/
See how you go with this.
Blog: Alpesh Nakar's Blog | Twitter: Follow Alpesh on Twitter |SharePoint Resources: Just SharePoint Resource Center | Follow Just SharePoint updates on Twitter -
Thursday, November 26, 2009 7:25 AM>For information, i've installed SharePoint 2010 on Windows 2008 R2 VMWare with :
Just to make this quite clear, either say SharePoint *Server* 2010 or SPS 2010.
"SharePoint 2010" could mean either 2010 SharePoint product and installing SPF 2010 on 2GB wouldn't be so surprising.
(Moderator)
FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
Complete Book Lists (incl. foreign language) on each site. -
Tuesday, December 08, 2009 8:40 PMI also got this error and following these instructions
"restart the machine, don't run anything else before you start the setup, and run the wizard again"
It worked! I have 3 gig memory on Windows Server 2008 R2.
bob -
Friday, December 11, 2009 5:32 AMHi,
I also learned quite a bit from installing SharePoint, aspecially when trying to install a 64bit OS Virtual Machine (VM) on a 32bit host.
I only allocate 2gb ram...all works fine
You are welcome to look at the following post to see what worked for me: http://johanolivier.blogspot.com/2009/12/dive-into-sharepoint-2010.html
Hope it works !!
Johan -
Thursday, December 17, 2009 11:54 AM
I am running into the same issue on Windows Server 2008 R2 box, with all pre-requisites, hot fix running as a DC. The machine has 4GB of RAM.
Hi there
Ive followed on different VM-Installations all possible configuration-steps, but always getting error system.serviceprocess.timeoutexception
Have VMware / Win2008R2 / SQLexp
Is there a final document (all in one), which really works?
Or, is there already a VM-File?
Getting really deperate... -
Monday, January 04, 2010 4:06 AM
I got the same error and fixed it...- Proposed As Answer by Raymond Mitchell {iwkid} Monday, March 01, 2010 7:35 PM
-
Monday, January 04, 2010 4:09 AMHi Jie,It seems like it is happening because of the service account. I was trying to do this on my virtual machine's DC, and it got stuck since it was pointing to Local Service account. The moment I changed it to Local System, the configuration zipped through. I tried the same thing twice, and it worked fine both the times. So, the trick is to run the PSConfigUI.exe and the moment you get to the SharePoint Search service, switch back to the Services console, change the user to Local System, and restart the service. The installation succeeds after that.Thanks,Rahul
-
Saturday, February 27, 2010 2:09 AMThanks for the writeup, Rahul. This was helpful and fixed my problem.
Blog: blog.beckybertram.com | RSS: RSS | Twitter: @beckybertram -
Thursday, March 04, 2010 1:51 PMHi,
i had the same problem.
It's because the Sp configuration Wizard change the Log On As of the SP Server search 14.
Change it to Local System and start the service while Wizard waiting for timeout.
Paolo -
Tuesday, April 27, 2010 8:03 AM
Hi everyone,
I have the same problem (SearchServiceInstance & TimeoutException). I tried starting the service as Local System, but the service still takes too long to start up and the wizard still reports the Timeout error. The service does start eventually - does anyone know of any way of increasing the timeout value that the config wizard is using? Or perhaps discovering why the service takes so long to start?
(This is with the RTM version, btw, and Server 2008 R2 with 8GB memory!)
Steve.
Steve Biggs -
Tuesday, April 27, 2010 8:33 AM
Looking a bit further (usng Process Monitor), it appears starting the service causes it to completely recreate the registry hierarchy under
HKLM\SOFTWARE\Microsoft\Office Server\14.0\Search\Applications\<GUID>
That is, it is deleting the registry keys that are present then recreating them. This is taking so long, that even if I start the service via the Services Manager it times out!
This seems to be *very* odd behaviour!
Steve.
Steve Biggs

