The purpose of writing this blog post is to help developers fix an issue that arise during the deployment of a custom WSP package in a SharePoint server 2013 Farm.
We created a custom SharePoint Timer Job that takes care of content database creation process dynamically based on a list values. The deployment process seamlessly happened in Development environment. When we deployed the same package in the Staging environment using PowerShell commands the solution package got struck in “Deploying”.
This issue can possibly occur only on the following conditions
1. If the timezone settings of SharePoint Server and SharePoint Central Administration are different
2. If “SharePoint Timer” service under windows server is stopped or struck.
3. If there are any problems in the WSP package itself.
In this case, none of the above three were the cause.
The actual cause of the issue is that the “SharePoint Configuration Cache” was not cleared. To clear this “SharePoint Configuration Cache” navigate to “C:\ProgramData\Microsoft\SharePoint\Config\”. After clearing the cache cancel the deployment and deploy the solution again.
For Career Opportunities:
Tell us a bit about you