Skip to main content

Hello!


I'm struggling with the K2blackpoint - VPC I have. I'm trying to get a very simple workflow running.


 I created a new list "Expenses" with a few columns. When I create a new item i want a task assigned to a user which has to desicde whether its approved or declined. If its approved, i set the "Flag" to yes, if not, i set it to "No". Pretty simple.


 However, when I start the workflow it seems to start (is in progress) but doesn't create the task. I searched a while and checked everything. I believe I did everything like its done in the manual... still it doesnt work at all. In the error logs I can find an error for every time I tried. It sais:


 Unable to modify workflow: The request failed with HTTP status 401: Unauthorized.


 Does anyone know what I forgot?


 I created a new webapp on the VPC-Server, I deployed all the solutions and created the new process with k2 studio...


 Edit: I just created another, even more simple process: Startet on a list item, it just changes the "Flag" to "Yes".. However this throws a similar error on the list item event:


 The request failed with HTTP status 401: Unauthorized.


 Thanks for your Help


Big Harry


 

There is a 99.99% chance this is related to Kerberos.  Have you created the SPN's(Service Principal Names) for your different accounts?  If not, you will need to specify SPN's  for each of the services that are in use.  Typically the services involved are HTTP, K2Server, and K2HostServer.  Different SPN's will need to be created for the K2 Service Account, K2 Web Services Application Pool account, and the SharePoint application pool account.  Delegation will also need to be set up in AD as well.  You can find more information regarding Kerberos in the documentation under the installation guide.

Such an old thread...


I came across this thread searching for an answer to the same issue. Since this thread doesn't have a solution, I'll share how I solved it.


Added the K2 service account to the site collection administrators group.


Mine was a standalone install, so I don't believe Kerberos was the issue for me.


Thank you for sharing. Great to see when an issue gets solved!


Reply