This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.
The following error is logged in the Event Viewer Windows Application log and Hostserver log every 5 seconds; creating disk space issues:
"24148 The User Manager 127.0.0.1 returned an empty queue with name K2:Project\Process\RoleName"
This error was due to the adding of Roles to a process from the K2 Management site:
K2 Management Site > Workflow Server > Workflows > Process Details > Roles
When doing so, the role is incorrectly added in the Identity Cache (appending the K2 label to the Role Name and resulting in an invalid entry); this is recognized as a bug 1.
The manual adding of the Role was prompted by (bug 2) in which a K2 Studio/K2 for Visual Studio workflow that is nested in a folder, did not list the Role under the process when deployed. However, the applicable row does exist in the database. The Role is listed if the workflow does not reside within a folder.
* Do not add the Role manually via the K2 Management site, as the Role configured for the task is correctly added to the database, but is just not displayed.
These bugs were logged to be addressed in a future update.
To resolve this issue, these invalid entries can be deleted from the [Server].[DestQueue] table.
Please log a support ticket for assistance. A database/table backup should be done prior to any data manipulation.