Workflows and Automation

Updating service account passwords in Nintex Automation (K2) is a standard maintenance task, typically handled by running the K2 Setup Manager and selecting the Configure option. However, a known bug can sometimes stall this process, specifically when the installer attempts to restart the K2 JavaScript Service Provider . The Symptom During the configuration process, the Setup Manager may fail with a System.InvalidOperationException . If you inspect the installation logs, you will see an error similar to this: The service did not start due to a logon failure Target failed to execute: Start K2 JavaScript Service Provider This happens because the Setup Manager attempts to start the service before the new credentials have been fully propagated to the Windows Service host, or it fails to override the old cached credentials during the automated start-up sequence. The Workaround If you encounter this error, don't worry—you don't need to roll back your entire installation. You can b...

If you’ve recently performed a K2 migration to Microsoft Graph or installed a cumulative update, you might have noticed your Azure Active Directory (AAD) Sync suddenly failing. The error log usually looks something like this: Error - {"odata.error":{"code":"Authentication_MissingOrMalformed", "message":{"lang":"en","value":"Access Token missing or malformed."}}} This occurs because the Sync Service is still trying to communicate using legacy protocols rather than the newly required Microsoft Graph provider type. To fix this, you need to manually transition the Sync Engine's provider type and register the OAuth Resource ID. The Fix: Transitioning AAD to Microsoft Graph The following SQL script automates the transition by updating the SyncEngine tables to use the MSGraph provider type and mapping the correct oAuthResourceId from your Security Label configuration. ⚠️ Prerequisite: It is highly recomm...

If you are running a scan with the Nintex K2 for SharePoint SPFx Migration Tool and hit a roadblock, you might encounter a specific exception during the PopulateUI method. This error typically surfaces when the tool attempts to call the GetContentTypes method but fails because it cannot find a specific SharePoint list. The Error Error Exception occurred in PopulateUI method: SmartObjectException occurred with Smartobject name: SharePoint_Integration_Workflow_Helper_Methods ,SmartObject method: GetContentTypes and Input properties: { K2_Int_SiteUrl: https://portal.denallix.com ListId: 9b841724-5d9c-4e8b-8a2a-7c91f1532f50 } containing error message: Thread 1: List does not exist.  Why is this happening? This error usually occurs when SharePoint libraries, lists, or sites have been deleted without first removing the associated K2 artifacts through the K2 Application. This leaves "orphaned" references in the K2 database that the migration tool tries to validate, resulting in ...

  If you encounter this error while running a scan with the Nintex K2 for SharePoint SPFx Migration Tool , please contact Nintex Support for assistance. The resolution steps depend on your environment: K2 Cloud: The Nintex team will need to perform a cleanup within your K2 Cloud database to resolve the issue. On-Premises: Support will help you identify and remove invalid records from the [Integration].[ProcessSharePointGeneralSetting] table.