Troubleshooting - Task actioning when there are multiple System Accounts

When installing and working with the K2 for SharePoint components you must provide credentials for several different accounts. Using the incorrect Account may result in errors while using those components.The following links describe the accounts that are used to install, configure, and run the various K2 for SharePoint components:

Example: Actioning a task with multiple System Accounts

Consider the following example. User A is a Farm Administrator and has been set as the destination user. User B is a Farm Administrator and has been set as the SharePoint Application Pool Account of the current Web Application. When User A logs in and opens his task he receives an error because the program does not consider him to be the destination user, instead it expects User B to be the destination user.

Problem:

The problem in this case is because the user logging in to Workspace is the SharePoint\System or the Application Pool Account, which SharePoint logs in as SharePoint\System Account automatically. Because both accounts will display as System account, SharePoint cannot tell the difference.

Solution:

It is bad practice to use an actual User account as the Application Pool Account, however, a workaround is available in the event where this cannot be prevented.

Use the stsadm command line utility that ships with SharePoint to run the command stsadm -o updatefarmcredentials -identitytype NetworkService.

This will change the identity type to NetworkService Service Account. The Application Pool Account will stay the same.