Recipient does not receive a Task Notification when a Task is redirected to them

  • 16 February 2021
  • 1 reply
  • 21 views

Userlevel 5
Badge +20
 

Recipient does not receive a Task Notification when a Task is redirected to them

kbt181982

PRODUCT
K2 Five
BASED ON
K2 Five 5.3
TAGS
K2 Notification Event
Management Site
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.

Issue

New recipients do not receive a Task Notification for a task redirected to them by a Workflow Admin.

This is because the users' (the one redirecting from the K2 Management Task List but is not a K2 Server Admin) claim still flows through and a Workflow Server Admin rights check is done against the claim and fails. If a Server Admin performs a redirection from the Task List, then notifications are sent out.

Symptoms

When a Workflow Admin redirects the task from the Task List on K2 Management, you will see the errors below on the K2 host server logs:

User K2:{Domain}{UserName} does not have Administrator rights.

61007 Permanent failure sending message {Task Notification Subject}: System.FormatException: The specified string is not in the form required for an e-mail address.

Resolution

You may consider the following options to get around the issue:

  1. Enable/Fix the K2 Claims to Windows Token Service*
    1. Stop the K2 Service.
    2. Stop the K2 Claims To Windows Token Service.
    3. Go to .../K2/Token Service/Bin.
    4. Make a backup of the K2TokenService.exe.config.
    5. Edit this file on any text editor.
    6. Look for: <allowedCallers>
    7. If there are no users within <allowedCallers> please add (a) the K2 Service account (eg. DENALLIXK2Service) and also your Runtime Application Pool account (eg. DENALLIXK2WebService).
      <allowedCallers>
         <clear />
         <add value="DENALLIXK2Service" />
         <add value="DENALLIXK2WebService" />
      </allowedCallers>
    8. Save the file.
    9. Start the K2 Claims To Windows Token Service.
    10. Start the K2 Service.
  2. Redirect the task as a user with Server Admin rights
  3. Redirect the task from K2 Workspace or through a worklist control.

*This is only applicable to AD users on K2 Five. If you are on K2 Cloud, please follow either #2 or #3.

 


1 reply

We had the same issue.  One of our application testers did not receive emails when redirecting the task.  But the worklist showed the task was redirected.  Found the same 61007 error in server event logs.  Fix #1 resolved the issue, but only after the tester cleared the browser cache for the browser hosting the K2 Management page.  (Or it just started working after that extra delay.)


 


This article definitely helped.

Reply