November Happy Hour will be moved to Thursday December 5th.

Installing Connect for Sharepoint Webparts error

Vote:
 

Hi,

I'm following the installation instructions for installing Connect for Sharepoint 2.2.

I'm doing the Sharepoint Solution deployment and following the deploysolution command i'm checking the status of the deploying process using the displaysolution command and this is returning the following status:

<Solution Name="connectforsharepoint2.2.wsp">
   <Id>44be5f4a-d561-4981-a318-95abc706364a</Id>
   <File>connectforsharepoint2.2.wsp</File>
   <Deployed>FALSE</Deployed>
   <WebApplicationSpecific>TRUE</WebApplicationSpecific>
   <ContainsGlobalAssembly>TRUE</ContainsGlobalAssembly>
   <ContainsCodeAccessSecurityPolicy>FALSE</ContainsCodeAccessSecurityPolicy>
   <SolutionDeploymentJob id="c00e8474-361b-4d8e-808d-1669807b22e6">
      <Title>Windows SharePoint Services Solution Deployment for "connectforshar
epoint2.2.wsp"</Title>
      <Type>Deployment</Type>
      <State>Failed</State>
   </SolutionDeploymentJob>
</Solution>
    

The installation guide states that if there is an error it will have an error code in the format DeploymentFailedXXXX where XXXX is the error. 

I can see that it's failed but don't know why...

 

#42052
Aug 06, 2010 13:43
Vote:
 

Turns out the problem was because the job was queued up and hadn't actually executed. 

The instalation documentation states that the Windows SharePoint Services Timer service needs to be running.

In order for the job to be executed either the Windows SharePoint Services Administration service needs to be running before you start the solution install or you can use the following to execute the admin service jobs now:

stsadm -o execadmsvcjobs

 

#42056
Edited, Aug 06, 2010 14:29
This thread is locked and should be used for reference only.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.