Showing results for 
Search instead for 
Did you mean: 
Not applicable

Nintex Workflow 2013 - Product Update Process

Have you seen Product Update - What you need to know?

  1. Obtain an account with sufficient permissions. Ensure that the user account performing the installation and deployment (Windows user as well as user logged into Central Administration) is the Farm Installation account and that it is a Local Administrator on the server used for installation.
  2. Run the new installer (.exe file) for Nintex Workflow 2013.
    1. On the Confirm Installation page, at the prompt "Do you want to add the solution to SharePoint now?," select Yes. The installer will attempt to upgrade the solution in SharePoint.
    2. On the page that lists the Nintex Live installation option, select Install Nintex Live. This option installs the Nintex Live Framework, which is required to enable the Nintex Workflow - Nintex Live Catalog feature.
      After installation the Solution Management page appears.
  3. Refresh the Solution Management page until the installed Nintex solutions are listed as Deployed.

    The Nintex solutions installed by the Nintex Workflow 2013 installer are listed in the installation guide. See Installing Nintex Workflow 2013 and Nintex Forms 2013.

    Note: If the page lists the solution as Deploying with a timestamp, refresh the page until the solution is listed as Deployed. If the page says Service Unavailable, then IIS is restarting. Refresh the page until it displays.

    If any errors appear for installed solutions, then the solution package upgrade has failed. To resolve the error, click the solution and click Deploy Solution. In most cases, the solution is then deployed. If not, reset IIS (Start->Run->iisreset) before clicking Deploy Solution again. Resetting IIS resolves this issue as it releases all locks on the application files. After deploying manually, reset IIS on each front end server.
  4. If the release notes indicate that a database update is required, then do the following.
    1. In SharePoint Central Administration, in the Quick Launch menu, click Nintex Workflow Management.
    2. Click Database Setup.
      If a database update is available, it will be indicated in green with an option to “Update now” .
    3. Click Update now.

      Note: If you receive an error when attempting to access a Nintex Workflow administration page, ensure that nintexworkflow2013core.wsp is deployed globally and that nintexworkflow2013.wsp is deployed to the Central Administration web application. To view deployment status, on the Central Administration Home page, click System Settings, then click Manage farm solutions in the Farm Management section. For instructions on deploying solutions, see Installing Nintex Workflow 2013 and Nintex Forms 2013. (Note: The deployment option “All content web applications” does not include the web application.) No IISRESET is required for deployment to the Central Administration web application.
  5. Enable Nintex Live.
    1. In SharePoint Central Administration, in the Quick Launch menu, click Nintex Workflow Management and then click Live settings.
    2. In the Enable Nintex Live for Nintex Workflow section, click Enable and then click OK.
  6. Reset IIS (Start->Run->iisreset) on all SharePoint farm servers and then restart the SharePoint 2013 Timer:
    1. Open the Services Microsoft Management Console (MMC) snap-in.
      For instructions on accessing the Services Microsoft Management Console (MMC) snap-in, see the Microsoft article Services.
    2. Right-click the service and select Restart.

Note: If Nintex Workflow for Project Server 2013 is installed in the same environment, restart the "Microsoft Project Server Queue Service 2013" service and do a final IISreset on each server.

After any update, we recommend clearing temporary files stored by the browser so that cached JavaScript files are not used and no previous errors continue occurring.

Labels: (1)
Tags (1)
1 Reply
Nintex Newbie

Re: Nintex Workflow 2013 - Product Update Process

In my case the service unavailable HTTP 503 error showed up on all sites except for the search, which is obviously on a separate web application. Which made me think maybe this was related to web application/application pool level since IIS reset did nothing. I opened the IIS Manager and checked the application pool to find most of it to be stopped. Everything started to work after i started the application pools manually.

0 Kudos