Symptoms

Issue: The client is getting the error below when trying to execute a smartobject created from worklist service broker: 24404 Authentication with server failed for someaccount@somedomain with message: AcceptSecurityContext failed: The logon attempt failed.
 

Diagnoses

Diagnosis: The client has a few issues also on their environment after running a repair on the environment. I have looked at the below K2 community post, they mentioned that the password might have been changed however the client has not changed the password: https://portal.k2.com/support/report/snapshot.aspx?id=53089 Also on a previous ticket they mentioned a repair has previously fixed the issue and the client tried to do a repair and it failed. Please attached installer trace logs and snapshots of the issue. ****Information**** It was found: - That the K2 Blackpearl Server Service with stuck in starting state. - K2hostserver.exe.config disappeared after running the repair. - Client could not access workspace or designer. What was Done: - Found the backup of the K2hostserver.exe.config - re-added it to the Hostserver Bin and renamed it to K2Hostserver.exe.config - Killed the K2 Blackpearl Service using cmd promp taskkill as per the following: https://technet.microsoft.com/en-us/library/bb491009.aspx https://community.spiceworks.com/how_to/312-stop-a-hung-service - Ran K2 Blackpearl Server in Console Mode - Change from Windows Authentication to Forms Authentication - Ran Reconfigure of K2 using installation media.
 

Resolution

Resolution: You must modify the "Impersonate Connection String" value. The default value is just a template. You have to fill in the domain, username and password of the account that has impersonate permissions on K2 Workspace. Refresh the Smart Object generated from the Service instance and it should work as expected. For further reference please see the attached doc "Worklist Service Broker"