6
Vote

Installation - Timeout Error

description

***** SOLUTION DEPLOYMENT *****
***** ERROR *****
Timeout error
CodePlex.SharePointInstaller.InstallException: Timeout error ---> CodePlex.SharePointInstaller.InstallException: Timeout error
at CodePlex.SharePointInstaller.InstallProcessControl.WaitForJobCompletionCommand.Execute()
--- End of inner exception stack trace ---
at CodePlex.SharePointInstaller.InstallProcessControl.WaitForJobCompletionCommand.Execute()
at CodePlex.SharePointInstaller.InstallProcessControl.TimerEventInstall(Object myObject, EventArgs myEventArgs)
***** SOLUTION RETRACTION *****
***** ERROR *****
Timeout error
CodePlex.SharePointInstaller.InstallException: Timeout error
at CodePlex.SharePointInstaller.InstallProcessControl.WaitForJobCompletionCommand.Rollback()
at CodePlex.SharePointInstaller.InstallProcessControl.TimerEventRollback(Object myObject, EventArgs myEventArgs)

comments

humenjo wrote Nov 16, 2008 at 7:42 PM

The following files were added:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\1033\Workflow\DPWorkflow.ACTIONS

GAC - DP.Sharepoint.Workflow - 0298457208daed83

humenjo wrote Nov 16, 2008 at 7:46 PM

The Execute method of job definition Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition (ID 1f0bb531-5d7e-4b3c-9798-f45c3fd8e4b8) threw an exception. More information is included below.

"dp.sharepoint.workflow.wsp" does not exist in the solution store.

humenjo wrote Nov 16, 2008 at 8:45 PM

Also, the following entries were added to the web.config
  <SafeControl Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow.InfoPath" TypeName="*" Safe="True" />
  <SafeControl Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow.Install" TypeName="*" Safe="True" />
  <SafeControl Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow" TypeName="*" Safe="True" />
  <authorizedType Assembly="DP.Sharepoint.Workflow, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0298457208daed83" Namespace="DP.Sharepoint.Workflow" TypeName="*" Authorized="True" />

wrote Jan 28, 2009 at 9:36 AM

cbranwell wrote Jan 28, 2009 at 11:12 PM

I am getting this same error. Has anyone found a resolution?

wrote Mar 19, 2009 at 7:14 PM

webhai wrote Jul 2, 2009 at 9:00 PM

Hi guys,
if you tried to deploy the wsp solution package on multiple frontend servers, this could be an answer to your problem:
The installer only checks the current Web Front-End server for Windows SharePoint Service Timer service and Windows SharePoint Services Adminstration service to confirm that they are started. However, it cannot check other WFE servers on the farm to confirm the status of those 2 services. If any of the services not started, the installation will time out and throw an error message.
Solution: Therefore, you MUST make sure that those two services are started before installing a Web Part.
(solution found on: http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2008/09/11/common-issues-during-bamboo-web-parts-installation.aspx)

feygirrl wrote Aug 11, 2009 at 2:29 PM

I get the same timeout error. The Windows SharePoint Service Timer and Windows SharePoint Services Adminstration services are started.

Has anyone figured out what the solution is? Does anyone know of another solution out there? I really need to be able to have a workflow copy items from document libraries from one site to another site (in the same site collection).

wrote Aug 11, 2009 at 3:21 PM

webhai wrote Aug 11, 2009 at 9:32 PM

Error Solution
In my case the timer service at the backend wasn´t started, so therefore the solution was to start, and then it worked to install the webpart. Check all the frontend servers and also the backend!
cheers
webhai

feygirrl wrote Aug 13, 2009 at 1:25 PM

Thanks for the tip webhai! I will let you know what happens...

CMAdmin wrote Apr 6, 2010 at 3:37 PM

We are receiving the timeout error. Both services are started on the server.

wrote Apr 9, 2010 at 1:45 PM

saber13812002 wrote May 10, 2010 at 5:08 PM

I am getting this same error. Has anyone found a resolution?

saber13812002 wrote May 10, 2010 at 5:08 PM

I am getting this same error. Has anyone found a resolution?

wrote May 10, 2010 at 5:09 PM

shepswife wrote Nov 28, 2012 at 4:23 PM

Hi! I am still having this same timeout issue. What else can I try? I have even gone into the SQL server and granted admin rights to my account that is used to login the Timer service. Please help?

wrote Feb 22, 2013 at 12:36 AM