Troubleshooting SharePoint 2013 Solution Deployments

Document created by emily.billing@nintex.com Champion on Jun 25, 2014Last modified by frank.field@nintex.com on Sep 22, 2015
Version 8Show Document
  • View in full screen mode

This troubleshooting deployments article is an excerpt from the Installing Nintex Workflow 2013 and Nintex Forms 2013

 

Troubleshoot Deployment

This section describes ways to narrow down deployment problems as well as resolutions for deployment issues that may come up.

 

Identify the problem

This section describes methods for narrowing down problems with solution deployment.

 

Deploy test solution packages

Deployment issues with the Nintex Workflow solution package (nintexworkflow2013.wsp) may indicate an issue with the SharePoint environment. If you suspect issues with the SharePoint environment, you can deploy test solution packages to determine if the deployment issues persist.

 

The following test solution packages are available from Nintex:

  • TestingSolutionGlobal.zip: This solution deploys globally; no URL needs to be specified. The solution creates the following file:

 

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\TestingSolutionGlobal.txt

 

Note: If you don't see the file in the above location, check the path for the SharePoint 2010 hive:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\TestingSolutionGlobal.txt

 

If Solution 1 does deploy correctly, then please try Solution 2 as well, which is slightly more advanced.

 

 

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\TestingSolutionForWebApps.txt

 

Note: If you don't see the file in the above location, check the path for the SharePoint 2010 hive:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\TestingSolutionForWebApps.txt

 

The solution also deploys a file called SimpleSolution.dll to the GAC and adds an entry to the web.config file for the web application as follows:

<SafeControl Assembly="SimpleSolution, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a10b52b9b77b11de" Namespace="SimpleSolution" TypeName="*" Safe="True" />

Note: The SimpleSolution.dll contains no code that executes.

   

To deploy test solution packages

    1. Download the test solution packages from the following URLs:

http://download.nintex.com/sl/supportfiles/TestingSolutionGlobal.zip

http://download.nintex.com/sl/supportfiles/TestingSolutionForWebApps.zip

   2. Run the following command to add the solutions to the solution store:

      

stsadm.exe -o addsolution -filename <path to wsp file>

 

For a mapping of Stsadm operations and their equivalent Windows PowerShell cmdlets, see the following Microsoft TechNet article: http://technet.microsoft.com/en-us/library/ff621081.aspx

 

   3. Deploy the test solution packages from Central Administration. For instructions, see "Steps for deploying solutions" 16 of the Installing Nintex Workflow 2013 and Nintex Forms 2013.

If deployment does not successfully complete with one or more of the test solution packages, the SharePoint environment may have an issue. We suggest contacting Microsoft for additional support with your SharePoint environment.

If deployment successfully completes with both test solution packages, contact Nintex Support.

 

Review SharePoint ULS log files

The SharePoint Unified Logging Service (ULS) log files may contain helpful information for troubleshooting issues with deployment of solution packages.

 

For example, the following error suggests a critical timer job error relating to internal SharePoint problems persisting objects to the database. These errors also mention 'update conflict' as experienced when attempting solution deployment. This underlying issue may be preventing solution deployment and should thus be resolved. Contact Microsoft directly for additional support.

 

Example:

“The Execute method of job definition Microsoft.Office.

Server.Search.Administration.IndexingScheduleJobDefinition (ID xxxxxxxxxxxx- xxxx-xxxx-xxxxxxxxxxxx) threw an exception. More information is

included below. An update conflict has occurred, and you must re-try this action. The object IndexingScheduleJobDefinition Name=Indexing Schedule Manager on servername Parent=SearchService Name=OSearch is being updated by DOMAIN\username, in the OWSTIMER process, on machine SERVERNAME. View the tracing log for more information about the conflict."

 

By default, ULS logs are located in the SharePoint hive. For example, the default location for SharePoint 2013 ULS logs is %ProgramFiles%\Common Files\MicrosoftShared\Web Server Extensions\15\Logs.

Note: For more information about ULS logging, see the following MSDN article.http://msdn.microsoft.com/en-us/library/office/ff595318(v=office.14).aspx.

 

In your review of the log files, search for logged information during the time range in which the solution was scheduled to be deployed.

 

To aggregate all log files from SharePoint servers

  • Use the Merge-SPLogFile cmdlet in a SharePoint Management Shell window.

 

Issues

This section provides guidance for resolving common issues related to deployment.

 

Solution package is stuck in deployment

Symptom

The Nintex Workflow solution package (nintexworkflow2013.wsp) is stuck in deployment.

 

Cause

The solution may not have been deployed correctly.

 

Resolution

Cancel and restart the deployment.

    1. Run the following stsadm command to list the job identifiers for all deployments in progress.

 

stsadm -o enumdeployments

 

For a mapping of Stsadm operations and their equivalent Windows PowerShell cmdlets, see the following Microsoft TechNet article: http://technet.microsoft.com/en-us/library/ff621081.aspx

 

    2. Note the job identifier for the stuck Nintex workflow deployment job.

    3. Cancel the deployment, using the following stsadm command:


stsadm -o canceldeployment -id "your job id string here"


The solution management page in Central Administration updates the status of the solution to "not deployed." You can now deploy the solution again.

 

    4. Redeploy the solution by doing one of the following:

              

               stsadm.exe -o deploysolution -n nintexworkflow2013.wsp -allcontenturls -immediate -allowgacdeployment

 

If the deployment is stuck again, analyze the SharePoint ULS log files to determine what is causing the failure. For more information, see "Review SharePoint ULS log files" on page 30 of Installing Nintex Workflow 2013 and Nintex Forms 2013.

 

Solution package is listed as error

Symptom

The Nintex Workflow solution package (nintexworkflow2013.wsp) is listed as error.

 

Cause

The solution may not have been deployed correctly.

 

Resolution

    1. Confirm that the SharePoint Administration service is running. See "Ensure services are running" on page 8.

    2. Run the following stsadm command:

      

        stsadm.exe -o execadmsvcjobs

 

         For a mapping of Stsadm operations and their equivalent Windows PowerShell cmdlets, see the following Microsoft TechNet article:                       http://technet.microsoft.com/en-us/library/ff621081.aspx

 

     3. Redeploy the solution by doing one of the following:

               stsadm.exe -o deploysolution -n nintexworkflow2013.wsp -allcontenturls -immediate -allowgacdeployment

 

If the solution package is still in error, check the solution information page for potential information about error causes. To view the solution information page, go to the Central Administration Home page, select System Settings, click Manage farm solutions, and click the link for the solution of interest.

You can also analyze the SharePoint ULS log files to determine what is causing the failure. For more information, see "Review SharePoint ULS log files" on page 30 of Installing Nintex Workflow 2013 and Nintex Forms 2013.

 

 

Nintex icons missing from Central Administration

 

Symptom

Nintex icons are missing from Central Administration.

 

Cause

This indicates that for some reason the Central Administration Feature was not activated. It's possible that the Nintex Workflow or Nintex Forms solution was deployed to the front-end web servers but not to the server hosting SharePoint Central Administration.

 

Resolution

To resolve this issue, deploy the Nintex Workflow and Nintex Forms solutions to the Central Administration Web application; if needed, activate the relevant Nintex features manually using Stsadm commands.

 

To deploy the solutions to Central Administration

  1. On the Central Administration Home page, click System Settings.
  2. In the Farm Management section, click Manage Farm Solutions. The Solution Management page appears. Solution deployment status is indicated in the Status column; the Web applications to which the solutions are deployed are indicated in the Deployed To column.
  3. Deploy the Nintex Workflow and Nintex Forms solutions to the Central Administration Web application:
    1. Display the Deploy Solution page: Click the solution that you want to deploy and then click Deploy Solution.
    2. In the Deploy When? section, select Now.
    3. In the Deploy To? section, select the URL for the Central Administration Web application.
    4. Click Ok.

 

To activate Nintex Workflow features on Central Administration

Run the following command, where http://centraladminurl:port is replaced with the URL and port for the Central Administration Web application.

 

stsadm.exe -o activatefeature -name nintexworkflowadmin -url http://centraladminurl:port

 

To activate Nintex Forms features on Central Administration

Run the following command, where http://centraladminurl:port is replaced with the URL and port for the Central Administration Web application.

 

stsadm.exe -o activatefeature -name NintexFormsAdminWeb -url http://centraladminurl:port

Attachments

    Outcomes