SharePoint On-Premise – Deployment issues

Posted 30 July 2018 12:00 AM by Ivan Diaz, SharePoint Developer @ ClearPeople

Have you ever had any issue updating a package of your solution in a SharePoint farm? Was the deployment an endless process? In this post, we are going to review these kind of issues and find a solution to finally get a successful deployment of the package.

First, we need to identify the root of our issue. In our case we are trying to update an existing deployment package (wsp file). This can be done easily through PowerShell. Basically, this process involves uninstalling the current package, remove it from the farm, add it again and install it for the different web applications.

These commands should work for all the packages that you have already installed in your farm. However, for some reason, sometimes the deployment process is scheduled and the timer job that manages this process never ends. Well, the job actually finishes, but not the deployment. So, we cannot see our package deployed and we cannot use its features in our solution.

solutionmanagement
 
(The status never changes)

If this happens once, we will not be able to run a successful deployment. So, our first possible fix is to restart the services “SharePoint Administrator” and “SharePoint Timer Service” in all the servers in the farm. Then, we can try the deployment process again.

solutionmanagement2

 
In most cases, this will solve the issue. Nevertheless, there will be other cases where it will not be deploying the package yet. At this point, as the job is finishing, it seems like a problem deploying the new package, so we are going to check what it is the last updated content in the different servers in the farm. To do this, we need to access to this folder path:

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\FEATURES

In this folder, there will be a folder for each feature that has been deployed in that server. So, you need to check the features of the package you are trying to deploy and verify what it is the last modified date. If you follow this process through all the servers in the farm, probably you will find a server where the features are not being updated.

Why is this happening if this was working before?

Despite the server is already included on the farm (you can double check it in SharePoint Central Admin), the job that deploys the package is not able to contact the server and update the content for the features. 

If we are at this point, the only solution is to remove the affected server from the farm and include it again. To avoid this process, it is possible to run a command that allows you to restart a service related with the belonging of the servers to the farm. So, if you restart this service, the farm will detect the server again.

To run this command, it’s required to use STSADM console. To find it, go to this path in one of the servers in the farm:C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN
Open the file STSADM.EXE and run these commands:
stsadm -o provisionservice -action stop -servicetype spwebservice
stsadm -o provisionservice -action start -servicetype spwebservice
Repeat the process for all the servers in the farm.

Once you finish, update your package again and this time it will finish successfully, showing your package as deployed in the farm.

solutionmanagement
 

Share:

Add your comment

 
 

 

Archive

Tagcloud

intranet Modern SharePoint teamwork employee engagement digital workspace SharePoint JavaScript Windows Azure Digital Transformation staff satisfaction productivity Microsoft Teams Office 365 Yammer cms content management system agile GDPR Microsoft Graph collaboration Microsoft sharepoint 2016 upgrade migration SharePoint Online 2016 Tech Trends Digital Disruption Context marketing marketing SharePoint 2010 SharePoint 2013 TFS Git security kentico Analytics jquery QA Quality Assurance testing content management websites Sitecore sitecore marketplace sitecore module cloud Microsoft Cloud Storage digital strategy technical consulting sitecore modules Experience database Sitecore 7 Sitecore 8 support account management customer experience Data Storage cms integration front end front end development prototype Cloud Storage StorSimple Front-end Development Layout SharePoint 2013 colour palette UI design website design log viewer sitecore cms website Azure big data business-critical sharepoint accessibility android apple chrome clear people clearpeople debug emulator ios mobile testing opera resize adobe desktop flash ie10 internet explorer 10 metro windows 8 bcsp Advanced System Reporter reporting framework ControlMode form control master page placeholder publishing console SharePoint 2007 SharePoint error search search results search values software testing testing scenario audit content information architecture retention schedules PowerShell QuickLaunch scripts SharePoint server 2010 business solutions metalogix replication replicator storagepoint stena technet UK Technet picture library slideshow web part RTM released to manufacturing caml caml query MOSS 2007 query infopath