Nintex Automation K2 Updates & Fix Packs

Issue DescriptionWhen you have upgraded to K2 Five (5.5) November 2021 Cumulative Update, and you attempt to execute the PDF converter SmartObject an error occurs.Error Message:The following error occurs: “Could not load file or assembly 'System.Memory, Version = 4.0.1.0'.....”ResolutionThe fix is available in:K2 Five (5.5) November 2021 Cumulative Update Fix Pack 01. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you open the Viewflow from a K2 Workflow, you will notice at the top right-hand corner of the screen the user FQN displays incorrectly and does not display the logged in user.ResolutionThe fix is available in:K2 Five (5.5) November 2021 Cumulative Update Fix Pack 01. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you have a K2 Workflow that starts an inter-process communication or IPC, the IPC fails to start after a server reconfiguration resulting in an error.Error Message:The following error occurs: “K2IPC.CreateConnection","1 Send failed with error: An existing connection was forcibly closed by the remote host.”ConsiderationAfter the fix Pack has been applied you will need to re-deploy the K2 Workflow in question.ResolutionThe fix is available in:K2 Five (5.5) November 2021 Cumulative Update Fix Pack 01. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you Upgrade to K2 Five (5.4), ID numbers have a comma formatting in K2 Management site’s error log section, the format setting on the Error logs List view has the “Use 1000 separator” checked displaying commas after the 1000s.ResolutionThe fix is available in:K2 Five (5.5) November 2021 Cumulative Update Fix Pack 01. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you have a disabled Textbox control with default text on a Form with the theme set to Blue Void, the text cannot be seen when the form is opened on an iOS device in the Safari or Chrome browsers.ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 28. K2 Five (5.5) November 2021 Cumulative Update Fix Pack 01. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

 K2 Five (5.5) November 2021 Cumulative UpdatePRODUCTK2 Five 5.5K2 Five (5.5) November 2021 Cumulative UpdateImportant steps before installing the K2 Five (5.5) November 2021 Cumulative UpdateThe K2 Five (5.5) November 2021 Cumulative Update has been replaced with the K2 Five (5.5) March 2022 Cumulative Update. Please do not use the K2 Five (5.5) November 2021 Cumulative Update.Admin consent recommended before upgrading with Nintex K2 Five (5.5) November 2021 Cumulative UpdateMicrosoft is deprecating Azure AD Graph API in June 2022, and as of June 30th, 2020, stopped adding new features to the API. See these Microsoft articles for more information:Migrate Azure Active Directory (Azure AD) Graph apps to Microsoft Graph Azure Active Directory (Azure AD) Graph to Microsoft Graph migration FAQMicrosoft strongly recommends upgrading to Microsoft Graph API to access Azure AD APIs as well as APIs from other Microsoft services. K2 OAuth resources requiring access to the https://graph.windows.n

Issue DescriptionWhen you have adjusted existing system Validation patterns and you upgrade to another version of K2, there would have been no warning of the potential loss of their changes to existing System Validation patterns.ConsiderationA Warning Notice will be displayed that changed or adjusted System Validation patterns will be reverted after upgrades in the Edit Pattern Dialog when the customer edits existing System Validation Patterns. The warning will also indicate that it will be best to create a new Custom Validation pattern, rather than to edit existing System Patterns to avoid losing adjustments. Though we cannot limit the editing of existing System Validation patterns (this will prevent customers from adjusting patterns that may already have been edited), we can provide them with the information of the possible consequences of their actions so that they can make an informed decision. NB: During package and deployment, “Use Existing” should be selected for System Validati

Issue DescriptionWhen you have a view with controls in the toolbar and you add a Dropdown List control in the toolbar field, the Dropdown List control is incorrectly aligned. ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 53. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you are using LDAP, a user’s primary group is removed when the user containers are resolved if there are multiple objects with the same identifier returned (ex. Contact User). But added back when the group members are resolved. ConsiderationWhen the fix has been applied the user’s containers needs to expire before the fix will resolve the problem. ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 53. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix.

Issue DescriptionWhen you upgrade from K2 blackpearl (4.7) to K2 Five (5.5), and you have an existing OAuth configuration for an OData web service instance, as soon as the token needs to get created after authorizing the API, the step fails and an error occurs.Error Message:The following error occurs: “Authorization not successful. Exception details: OAuth Error: Code=unauthorized : Description=The format of value 'K2HostServer_OAuth:[Server Name]' is invalid.”ResolutionThe fix is available in:K2 Five (5.5) Fix Pack 09. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix.

Issue DescriptionWhen you have the Smartforms Rating control on a form with the Grey void theme applied, the control does not display the selected rating or becomes unreadable during runtime.ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 52 . K2 Five (5.5) November 2021 Cumulative Update Fix Pack 04. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you have an environment with an Azure SQL Database setup, running the K2 Fix Pack installer will fail on the K2 Server step and an error is logged in the InstallerTrace log.Error Message:The following error occurs: “Reference to database and/or server name in 'K2.Authorization.Class' is not supported in this version of SQL Server.”ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 51. K2 Five (5.5) Fix Pack 09. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix.

Issue DescriptionWhen you deactivate a SharePoint site via Manage App Activations in the K2 App, the Sync Engine provider remains active.ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 27. K2 Five (5.4) Fix Pack 51. K2 Five (5.5) Fix Pack 09. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you have a calendar control, and you are in a time zone 10 hours before UTC for example and you only enter the time in the calendar control field for example 10:00, the date returned is for the current day but if it is after 10:00 the previous day is returned instead.ConsiderationThe date should be the local date of the browser when setting the time portion of the calendar control.ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 29. K2 Five (5.4) Fix Pack 51. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you have the Day Difference expression on 2 calendar dates, the day difference calculation is incorrect. For example, the day difference between 2020/12/21 and 2021/1/29 is showing 40 days when in fact it is 39 days.ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 29. K2 Five (5.4) Fix Pack 51. K2 Five (5.5) Fix Pack 09. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionA PDF Service Security vulnerability has been addressed.ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 51. K2 Five (5.5) Fix Pack 08. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you start a K2 Workflow via the REST API the workflow is by default started synchronously which has a large performance impact when said workflow is large with server-side actions.ConsiderationWithin the K2 Workflow REST API UI there is now an option marked as “sync” with a dropdown to select true or false, selecting false will run the workflow asynchronously. The default selection will be true which will run the workflow synchronously.ResolutionThe fix is available in:K2 Five (5.5) Fix Pack 08. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you attempt to enable to Odata API in the K2 Management site, a “false” message box is shown when saving the changes.Error Message:The following error occurs: A popup showing “false” text.ResolutionThe fix is available in:K2 Five (5.5) Fix Pack 08. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you have a SmartObject mapping to a Smartform parameter on a K2 Workflow user task, the reference is lost after clicking away from the user task and back on the user task. This resulted in the SmartObject mapping displaying as an empty green block in the Smartforms parameter field. Upon attempting to deploy the workflow an error occurs.Error Message:The following error occurs: “Missing reference at SmartObjectField  in Event 'Task' in Activity 'Task'. Error: While trying to resolve the following reference root.externalReferenceDefinitions[{"internalId":4}].methods[{"internalId":2}], an error occured: reference not found.. Stack Location : K2Process 'testWorkflow' >Activity 'Task' >ClientEvent 'Task' >ClientEventConfiguration >SmartForm >FormParameter >Expression > Stack End.”ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 26. Ensure you have the correct K2 version and/or Cumulative update installed. See

Issue DescriptionWhen you run a reconfigure with the K2 Setup Manager on an environment where a previous Fix Pack has been applied, the reconfiguration will fail and an error logged.Error Message:The following error is logged: “Logged Error: Error from controlutil output: RegisterControlTypes Failed: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.Could not load file or assembly 'Telerik.Web.UI, Version=2015.3.930.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. The system cannot find the file specified.”ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 26. K2 Five (5.4) Fix Pack 50. K2 Five (5.5) Fix Pack 07. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pac

Issue DescriptionWhen you attempt to install a Fix Pack on an environment with a non-default database name of K2, an error occurs.Error Message:The following error occurs: “Logged Error: Database 'K2' does not exist. Make sure that the name is entered correctly.”ResolutionThe fix is available in:K2 Five (5.3) November 2020 Cumulative Update Fix Pack 25. K2 Five (5.4) Fix Pack 49. K2 Five (5.5) Fix Pack 06. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix.

Issue DescriptionWhen you have upgraded from K2 Five (5.3), to K2 Five (5.4) Fix Pack 40, and you attempt to deploy a package which contains a legacy K2 Workflow that references a custom [DLLTitle].dll with Package and Deployment, an error occurs.Error Message:The following error occurs: "Deployment failed. No reason supplied by responsible deployment service. "ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 48. K2 Five (5.5) November 2021 Cumulative Update Fix Pack 02. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended close and open K2 Package and Deployment.

Issue DescriptionAn AngularJS client-side template injection security risk was addressed. ResolutionThe fix is available in:K2 Five (5.4) Fix Pack 48. Ensure you have the correct K2 version and/or Cumulative update installed. See KB001893 to see what Fix Pack level you have installed. Download the latest Fix Pack using the links in the table above for the version you require. Install the Fix Pack to apply the fix. It is recommended to clear browser cache and refresh the page.

Issue DescriptionWhen you are using Exchange online for sending emails, Exchange online has a limit of 30 email messages per account per minute. This is causing the K2 Server to continuedly retry sending the emails/ K2 Workflow email step. This builds up to the point where all K2 Workflow threads are exhausted resulting in not being able to connect to the K2 Workflow server anymore.ConsiderationsIf you are encountering this behavior where your K2 Workflow threads are exhausted because of excessive emails being sent through to Exchange online, we recommend that you specify the number of retries.And we also recommend you to check whether you would like the K2 Workflow to go into error state after the retries all fail or if you would like the K2 Workflow to continue.These settings are defined in the connection string for the EWS destination.Edit the ConnectionStringEditor.exe found in the Host ServerBin folder and then select ExchangeWebservicesDestination (username).ResolutionThe fix is

Issue DescriptionWhen you use OOTB identity versus sync legacy identity, the exact same FQN format is not given when you set the provider ID to UserPrincipalName and Name to SamAccountName.OOTB would have the FQN as Label:UserPrincipalName whereas legacy sync would use the provider name to set the FQN giving you Label:SamAccountNameConsiderationsOnce the Fix Pack is installed the following SQL scripts steps need to completed in SQL Management Studio Step 1Set @ProviderName to the one created, then execute to get the ProviderInstanceIDA provider can have more than one instance so one would need to know which one to choose when there is more than one result or encase both needs to be added step 2 needs to be performed for each.(Copy and paste below into new query for SQL against K2 DB) DECLARE @ProviderName NVARCHAR(20) = 'K2LDAP';select [P].[Name], [PI].ID as [ProviderInstanceID] from [K2].[SyncEngine].[Provider] as Pjoin [K2].[SyncEngine].[ProviderInstance] as [PI]on P.ID = PI.Provider