pandeyk

Tips for Upgrade of Nintex Workflow

Blog Post created by pandeyk on Feb 20, 2015

To complete the upgrade from the previous version of Nintex, ensure that you still have a valid license; otherwise this upgrade will not be possible.

 

Navigate to “Add/Remove Programs” on the server hosting Nintex Workflow 2010 and remove it.

 

(This will not affect the programs functionality in SharePoint 2010)

 

Do not retract the solutions from the Solutions Management, as this will disrupt users that are currently using the product.

Once this has been done, run the new installation “setup.msi” for Nintex. When it prompts to add the solutions, select “Yes”. This will attempt to automatically upgrade the WSP’s that are currently installed on your solution.

 

Once the installation has been completed, it will show the solutions page, with the status of “Deploying (timestamp of when this was initialized)”

 

This is where I ran into an issue, although everything in the supplied upgrade document stated that this will show up as deployed after a while, it was not the case.

 

After about 25minutes, the 2 solution files were still showing as deploying, with the same timestamp as when the software installation finish. I cancelled both “deployments”, both these files now showed as deployed, but with no Last Operation Time in either.

 

How to fix this?

 

Reset IIS, Start -> Run -> iisreset

 

This will release any threads that are holding onto the WSP files.

 

Make sure that the SharePoint 2010 Administration service is running, Start -> Run -> services.msc

 

You will now need to manually upgrade the solutions files.

 

Start the SharePoint 2010 Management Shell as an Administrator.

Update-SPSolution –Identity nintexworkflow2010.wsp –LiteralPath “nintexworkflow2010.wsp” –GacDeployment 
Update-SPSolution –Identity nintexworkflow2010enterprisefeatures.wsp 
–LiteralPath “nintexworkflow2010enterprisefeatures.wsp” –GacDeployment

This will deploy your solutions correctly and add the needed DLL’s to the Global Assembly Cache.

 

 

You can also try below steps:

 

  1. Install the Nintex using Nintex setup
  2. Retract the deploy WSP
  3. Now use PowerShell scripts for installation of WSP
  4. Enable-SPFeature -Identity "NintexWorkflowAdmin" -Url "weburl"
  5. Install-SPSolution –Identity nintexworkflow2010.wsp –WebApplication "Weburl" -GACDeployment
  6. Repeat same steps for all web application you can also
    enable the features using Nintex admin section

Outcomes