Having trouble installing Nintex products? We have included a list of things you might want to check while troubleshooting an unsuccessful Nintex installation.
Have you temporarily disabled Anti-Virus and Malware Applications?
Ensure that all antivirus and malware (AV) software is disabled/suspended on all servers in the farm.
Is User Account Control (UAC) disabled?
While UAC is enabled, it can affect Nintex Workflow installing successfully. Ensure that UAC is disabled on the server you are running the installation files from. Before disabling, take note of the default settings, so you can reconfigure once you have completed the installation.
Navigate to Start > Control Panel > User Accounts > User Accounts > Change User Account Control Settings > Never Notify Me.
Note: Once you have installed Nintex Workflow, you’ll want to make sure that you enable UAC and reconfigure these settings.
Is SharePoint Timer Service (OWSTIMER) running on all servers in the farm? (Check this in Windows Services).
Navigate to Start > Run > Type Services.msc. Scroll down to the ‘SharePoint 2010 Timer’ service and verify that it is configured to start automatically and that it is started.
Is SharePoint Admin Service running on all servers in the farm? (Check this in Windows Services).
Navigate to Start > Run > Type Services.msc. Scroll down to the ‘SharePoint 2010 Administration’ service and verify that it is configured to start automatically and that it is started.
Are you running the installation as the Farm Installation account? Verify the Farm installation Account has local administrator rights
Ensure the user account that is performing the Installation/Deployment (Windows user as well user logged into Central Administration) is the Farm Installation account and that it is a Local Administrator on the Server you are installing on.
Navigate to Start > Run > Type MMC > From the MMC Snap-in console click File > Add or Remove Snap-ins > Local Users and Groups > Add > Finish > OK. Expand the Local Users and Groups and click the group’s folder. Double click the ‘Administrators ‘ group and verify whether the farm account is listed. If not, click the ‘Add’ button to add the account as a local administrator. Click ok to finalize.
Note: Make sure to remove the farm account after the installation is complete. If you do not do so, the SharePoint Health Analyzer with report warnings that the Farm account is configured as a local administrator later on.
Are the appropriate Web Application Pools running in IIS?
Navigate to Start > Run > Type inetmgr. From the IIS 7 or IIS 8 Management Console, expand the plus symbol for your server and click the application pools’ link. Verify the application pools for the appropriate web applications are started.
Investigate the SharePoint ULS Log Files for Additional Information
Please check the SharePoint ULS logs for the timeframe of the installation which should provide additional information about the behavior occuring. You can use the Merge-SPLogFile cmdlet from a SharePoint Management Shell window which will gather the logs from each of your SharePoint servers and create a single aggregated log file.
Additional information about this cmdlet can be found here: http://technet.microsoft.com/en-us/library/ff607721(v=office.15).aspx
Issue with deploying the Nintex Solution Package
If you have successfully run the Nintex installer but are experiencing issues with deploying the Nintex solution package, please refer to the following article Troubleshooting SharePoint 2013 Solution Deployments.
After an Installation has failed
If you’ve made it this far, and your installation has failed, you’ll need to perform a couple steps before trying to install again.
1. Perform an IIS Reset on All Web Front End (WFE) Servers
Perform an IIS RESET on all servers in the farm to ensure Nintex assemblies are not write-locked. Make sure this has been completed after a failed installation of the installer package.
2. Try Retracting and remove Nintex solutions from the farm
Retract and remove Nintex solutions from the farm (you will need to do this more than once as the first removal will be for content web applications and the second will be for Central Administration).