Application Troubleshooting

This topic discusses how to troubleshoot various issues across the K2 Mobile app.

Issue: When you tap a new task notification to open it in K2 Mobile, the new task is not shown on the task list. The notification also does not disappear when you close the app

Resolution: To correct the issue, change the Windows authentication provider from NTLM to Negotiate in the K2API application in IIS Manager (located in the K2 site). Contact your administrator if you do not maintain the K2 server.

Issue: The default K2 task pages for SharePoint Workflow Integrated (SPWI) processes are not enabled for mobile rendering in SharePoint.

Resolution: To bypass the SharePoint mobile rendering engine and open the K2 task forms directly on your device, you must disable the SharePoint Mobile Redirection System. For more information see, http://social.technet.microsoft.com/Forums/en-US/sharepointgeneralprevious/thread/c71cc609-aea5-44f7-9945-8ba9dd85e099/. Note that Custom, and Default Client Event forms work as expected.

Issue: When authenticating with AAD on the K2 Mobile app, the following error is displayed: Sorry something went wrong and the K2 server logs show a Data at root level is invalid. Line 1, position 1 message. This is due to the Intregrated= value in the K2API's web.config file being set to the default value.

Resolution: Ensure that the Integrated value is set to False in the connection strings section of the K2API's web.config file. For more information see Authenticating with AAD topic.

Issue: After logging in to the K2 Mobile app, the following error is displayed: Sorry, something went wrong and the following error in the K2 server log is: Primary Credentials Not Authenticated.

Resolution: To resolve this issue, ensure that the K2API's application pool for the Designer and Runtime sites is the same as the SmartForms application pools.

Issue: When you view your tasklist via the K2 Mobile app, an empty tasklist is returned. This is due to the double hop issue in distributed environments.

Resolution: To resolve this issue, set up and use Kerberos authentication for the K2API service.