deployed property of SPSolution object is not updated properly - sharepoint 2010 wsp deployment

Question

1)How come that SPSolution.deployed is set to true but the other fields are signaling that the deployment was unsuccessful?

here is the output after the deployment:

Farm                           : SPFarm Name=SP_Dev_Pil
Name                           : xxx.wsp
Deployed                       : True
DeployedWebApplications        : {xxx}
DeployedServers                : {pineapple1xb, pineapple2xb}
DeploymentState                : GlobalAndWebApplicationDeployed
SolutionFile                   : SPPersistedFile Name=xxx.wsp
ContainsGlobalAssembly         : True
ContainsCasPolicy              : False
ContainsWebApplicationResource : True
SolutionId                     : 5d2f55e9-b7e8-4912-b3c4-c4f58734a5f9
IsWebPartPackage               : False
LanguagePacks                  : {0}
Added                          : True
LastOperationResult            : DeploymentFailedFileCopy
LastOperationEndTime           : 10/17/2012 1:53:37 PM
LastOperationDetails           :

pineapple1xb : https://xxx/ : The solution was successfully deployed.

pineapple2xb : https://xxx/ : xxx : Error: The web.config is invalid on this IIS Web Site: F:\inetpub\wwwroot\wss\VirtualDirectories\xxx4432f415318-c4cc-45cc-9ab3-026a9892739d\web.config.
pineapple2xb : https://xxx/ : Successfully copied solutionfiles to IIS site xxx'.

JobStatus                      :
JobExists                      : False
CanSelectForBackup             : True
CanSelectForRestore            : True
TypeName                       : Microsoft.SharePoint.Administration.SPSolution
DisplayName                    : xx.wsp
Id                             : 5d2f55e9-b7e8-4912-b3c4-c4f58734a5f9
Status                         : Online
Parent                         : SPFarm Name=SP_Dev_Pil
Version                        : 194571
Properties                     : {}
UpgradedPersistedProperties    : {}

2) How come that once the deployment job is succeeded SPSolution.deployed property is still false. what are the other timer jobs we need to wait to?

Name                           : xxx.wsp

Deployed                       : False
DeployedWebApplications        : {}
DeployedServers                : {pineapple1xb}
DeploymentState                : NotDeployed
SolutionFile                   : SPPersistedFile Name=xxx.wsp
ContainsGlobalAssembly         : True
ContainsCasPolicy              : False
ContainsWebApplicationResource : True
SolutionId                     : 5d2f55e9-b7e8-4912-b3c4-c4f58734a5f9
IsWebPartPackage               : False
LanguagePacks                  : {0}
Added                          : True
LastOperationResult            : DeploymentSucceeded
LastOperationEndTime           : 10/3/2012 1:55:46 PM
LastOperationDetails           : pineapple1xb : https://xxx/ : The solution was successfull
                                 y deployed.
JobStatus                      :
JobExists                      : False
CanSelectForBackup             : True
CanSelectForRestore            : True
TypeName                       : Microsoft.SharePoint.Administration.SPSolution
DisplayName                    : xxx.wsp
Id                             : 5d2f55e9-b7e8-4912-b3c4-c4f58734a5f9
Status                         : Online
Parent                         : SPFarm Name=xxx
Version                        : 147279
Properties                     : {}
UpgradedPersistedProperties    : {}

wsp file contains webparts, gac assemblies, webapp resources etc and deployed farm wide

Answer 1

Hi xasm83,

For this issue, SPSolution.Deployed Property definition has an explanation about this, it returns a value indicating whether the solution is deployed to one or more web applications in the farm.

So, from the output of the deployment, the first one shows: DeployedWebApplications : {xxx}, and it is deployed to pineapple1xb successfully, for the second output, DeployedWebApplications : {}, it seems that the solution hasn’t deployed to any web application, so the status is false. And SPSolution.JobExists is false, based on my understanding, in your output, the deployed property value is correct.

More information, programmatically waiting on SharePoint solutions to deploy:
http://blog.krichie.com/2011/09/02/programmatically-waiting-on-sharepoint-solutions-to-deploy/

Thanks,

---

Qiao Wei

TechNet Community Support

Answer 2

thanks!