We are working with a Nintex partner and they recently sent us an update fo their product along with an update to the core Nintex workflow exe. We went from running 3.1.3.0 to 3.1.8.0. We have had a number of issues as a result and I am wondering if it would not be a better practice to do a stepped upgrade of your engine rather than a leap across 5 versions?
Thanks
I've since spoken with Nintex Support and was advised that it is best to contact Nintex when upgrading 5 or more versions. An upgrade path can be provided and intermediary Nintex trial versions can be provided for use to make a stepped upgrade.
Our ULS logs began showing hundreds of "The input data is not a complete block. (Build:3180)" and "Padding is invalid and cannot be removed. (Build:3180)" appearing in the Nintex Workflow 2013 area of the logs. Additionally we found that an action which uses an impersonation accounts credentials to execute was failing and had to be removed and re-added to the workflow. One site (out of more than 30) began logging 'Error in task. Cannot find a corresponding human workflow task id for this task.' The PowerShell script used for creating our HNSC and adding workflows began failing to get a the Nintex Workflow Service proxy. Workflows appeared to be successfully added but could not be seen in the redesigned workflow gallery.
We are working with our provider and with Nintex Support on troubleshooting and resolving these issues. Hopefully we will not find ourselves making this kind of leap in the future.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.