Symptoms

Getting these type of errors in host server log files:

"16:42:06"
"Error"
"IdentityService"
"64005"
"ResolvingException"
"IdentityService.ProviderCacheIdentity:RoleProvider.GetGroup"
"64005 Failed to resolve 'K2:USO3228': The specified account does not exist. Resolving User:USO3228."
"anonymous"
"0.0.0.0"
"W0982EWEBV0494:D:Program Files (x86)K2 blackpearlHost ServerBin"
"358528274"
"e9e15f3b961c47b7a4a3a5c1743b4c71"
"358528275"
"2015-03-16

No workflows were kicking off IPC processes, and were stuck in a "Waiting" state.
 

Diagnoses

Server.IPCAsync table empty, preventing any processes started in the Server.IPC table from actually starting.
 

Resolution

- We looked at the HostServer log and saw that it was resolving users and groups that no longer exist in Active Directory, and was doing so constantly. There is a coldfix available for this behavior, so it was provided and applied, which resolved most of the errors (although not all of them, which means they are probably referred to in some artifact that K2 is using)

- After doing this, we saw that the log was filling up with deadlocks when trying to access the Server.Async table, as well as the Server.DestQueue table, and the processes were not starting
- We attempted to reduce the Async thread count in the K2Server.Setup file to 1, and restarted the service, but this did not have any effect.
- We returned the Async thread count to 5, and saw a couple items get processed from the Server.Async table (which had over 17000 items), but the IPC processes still did not start.
- We looked at the Server.IPCAsync table, and found no entries. This means that the processes that should have started in the Server.IPC table would not start, as there was nothing to tell K2 to start them.
- We ran through a test process, and the child process started correctly