Symptoms

There is a parent and a child process. The IPC event is configured with the authentication method of "Impersonate Originator". Just before execution of the IPC event and child process, the originator account of the parent process was disabled in AD (and will no longer be active). Process rights was granted via groups and as the user had been disabled, this account cannot be found. An error is logged in the Error Profiles:

28042 IPC Failed to Start: 24417 K2:DOMAINusername does not have rights to Start Process ProcessName

Is there a way to either kill the process and remove it from the Error Profile, or a way to change the originator to be able to restart the workflow?
 

Diagnoses

One of the solutions below may meet your need:

A. Starting this 'ProcessName' process instance as a different user:

1. Create a database backup prior to attempting the step below
2. Take note of the 'Proc Inst ID' in the Error Profiles
3. Locate this row in the eServer].]IPC] table the 'Proc Inst ID' in the Error Profiles will equal the eSrcProctInstID] column in the eServer].]IPC] table
4. Locate the eDstUser] column for the process instance above this will contain this 'K2:DOMAINusername' user
5. Update this column to a valid AD user of your choice in the same format, make sure that this user of your choice also have 'Start' rights on the 'ProcessName' process
6. After making the above changes, Retry this process instance from the Error Profiles this should resolve this error and start this process instance as the user you had specified.

B. Starting this process instance as 'K2:DOMAINusername' and addressing it afterwards

1. Re-enabling this 'K2:DOMAINusername' user in AD, if this account had only been disabled
2. Re-adding this account to the 'ProcessName' process with Start Rights
3. Retry the error to start this child process
4. Address this process instance after it has been started by 'K2:DOMAINusername'
5. Disable this account in AD again
 

Resolution

Option A was used to resolve this error.