Workflows and Automation

URL Differences: When using Azure Government instead of Azure Commercial, your login and portal URLs will typically end in  .us  instead of  .com . For example: Azure Government login:  https://login.microsoftonline.us Azure Government portal:  https://portal.azure.us K2 Compatibility: K2 integrates with both Azure Government and Azure Commercial, but requires K2 version 5.6 or later for Azure Government's Cloud Computing High Security (GCC) environment. Integration Effort: Integrating K2 with Azure Government is slightly more involved compared to Azure Commercial. More details on the manual process are available here:  https://help.nintex.com/en-US/k2five/icg/5.6/Content/Configure/AzureNatCloud/GCCH/GCC-overview.htm

After reconfiguring K2 using the Setup Manager, your K2 websites might encounter an "HTTP Error 500. 19 - Internal Server Error. " This is normal if you applied a Cumulative Update or Fix Pack before the reconfigure and haven't reapplied it afterwards. Why this happens: From Fix Pack 17 onwards, K2 requires reapplying the latest Cumulative Update or Fix Pack after running a reconfigure if you previously installed it. If you skip this step, users won't be able to access K2 Designer, Manager, Workspace, or Runtime, and you'll see the "HTTP Error 500.19" message. How to fix the error: Simply reinstall the latest Cumulative Update or Fix Pack after successfully completing the reconfigure. This will resolve the issue and allow users to access K2 again. Additional information: You can find more details about this behavior in the Nintex documentation here: https://community.nintex.com/nintex-automation-cumulative-updates-and-fix-packs-16/k2-five-5-6-fix-packs-...

Managing SyncEngine.RunHistory Table Size for Identity Service Key Point: The SyncEngine.RunHistory table can significantly grow without automated cleanup, potentially impacting performance. Recommended Actions: Regularly Delete Old Data: Use this query to retain only 30 days of logs: SQL DELETE FROM [SyncEngine].[RunHistory] WHERE [SyncEnd] < GETUTCDATE() - 30 Automate with SQL Job: Create a scheduled job to execute this query regularly. Consider Performance and Disk Space: Stop K2 Service: Temporarily pause K2 services during cleanup to minimize impact. Ensure Adequate Disk Space: Verify sufficient space on the SQL server for transaction logs, especially for large deletions. Additional Tips: Customize Retention Period: Adjust the '-30' value in the query to match your desired log retention period. Monitor Table Size: Regularly check the table size to ensure it's within acceptable limits. Explore Alternative Cleanup Methods: If manual or ...

Resolving K2 Designer Site Performance Issues: Addressing Invalid Form.Peer Entries Key Points: Invalid entries in the Form.Peer table can contribute to performance slowdowns in the K2 Designer site. Regularly checking and removing these entries can significantly improve performance. Steps: Identify Invalid Entries: Run the following SQL query to list all entries in the Form.Peer table: SQL SELECT * FROM [Form].[Peer] Carefully examine the results for any outdated or invalid data. Delete Old/Invalid Values: Proceed with deleting the identified invalid entries from the Form.Peer table. Important: Exercise caution and consider taking a database backup before making any deletions. Additional Considerations: Identify Root Causes: If performance issues persist after cleanup, explore other potential causes, such as: Server hardware limitations Network latency K2 software configuration Large forms or workflows Seek Further Guidance: Consult K2 documentation or suppo...

Frequent "UMEmptyQError" in Hostserver Log: Troubleshooting Steps Understanding the Error: The error "Error","General","24148","UMEmptyQError","K2DestQueue.RunDestQueue","24148 The User Manager 127.0.0.1 returned an empty queue" indicates an issue with empty destination queues in K2 workflows. Troubleshooting: Invalid Role Entry: Check for invalid roles: SQL SELECT * FROM [Server].[DestQueue] WHERE [Name] NOT IN ( SELECT [Name] FROM [ Authorization ].[Role]) Delete invalid entries: Remove any invalid roles found in the [Server].[DestQueue] table. Valid Role with Empty Membership: Identify roles with empty membership: SQL SELECT * FROM [Server].[DestQueue] WHERE [ID] NOT IN ( SELECT DISTINCT [QueueID] FROM [Server].[DestQueueUser]) Add users to empty roles: Assign at least one valid user or placeholder user to each empty role. Additional Considerations: Deletion Order: If a role was recently deleted, ...

K2 Upgrade Error: Service Startup Failure Due to Missing Certificate Error Message: You'll encounter this error during a K2 upgrade if a required certificate is missing: Application: SourceCode.Configuration.Api.exe ... Exception Info: System.InvalidOperationException: Certificate not found: CN=k2.denallix.com.com (CN=K2 On Premise Root, O=K2) in LocalMachine/My Resolving the Error: Validate and Repair Certificates: Navigate to the K2 installation folder. Run  CertificateManager.exe . Press  v  to validate certificates and identify issues. If issues are found, press  r  to repair them. Recover Upgrade Process: Rerun the K2 setup. Choose the Recover option to resume the upgrade process. Additional Tips: Review K2 Documentation: Consult the official K2 documentation for more detailed troubleshooting steps if the error persists. Contact K2 Support: Seek assistance from K2 support for complex scenarios or further guidance. Other Upgrade erro...

Can you use the Odata endpoint with MFA? It depends it would seem... From the documentation, it looks like you have to disable MFA when granting consent: Turn off Multi-Factor Authentication before granting consent. You can then turn MFA back on once consent has been granted. This is because the underlying code was created before Microsoft's latest MFA implementation and therefore the consent loop will not work unless MFA is disabled. Note that the consent loop does not affect runtime authentication. Once the app is consented, you can enable MFA again and the runtime authentication will operate as expected. In other words, disabling MFA is only required while you are granting consent. https://help.nintex.com/en-US/k2cloud/userguide/current/Content/K2-Management-Site/Integration/APIs.htm But afterwards, if you try to use Basic Authentication in PowerBI or Excel you will still see an error.  This is because there is another caution at the bottom of the page that states...