<{{Subtitle_Weight}} class="prominent-subhead {{Show_Subtitle}}"> {{Header_Subtitle}}

Task Notifications do not work after changing the K2 installation path

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.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


After changing the K2 installation path, users are not receiving task notifications. The following error message is logged in the K2 host server log:

"Error","EventBus","7008","Processing","EventQueueProcessing.ExecuteAssembly","7008 The following error occurred while executing policy for CustomEventInstanceID: NNNNNN : Could not load file or assembly 'SourceCode.EventBus.MessageBusRecorder.dll' or one of its dependencies. The system cannot find the path specified. : The system cannot find the path specified. (Exception from HRESULT: 0x80070003).

Only processes started/deployed before the upgrade are affected.


Mail Events and Client Events from newly created test processes do not have any issues, but task notifications for processes deployed/started before the upgrade are not being delivered.

This issue can be caused by a change of the K2 installation path (from "C:\Program Files (x86)\" to "D:\Program Files", for example) as there are references to the assemblies in K2Hostserver.config and in K2 database.

This specific error message ("7008 The following error occurred while executing policy") may appear when the K2 database still contains references to the old path in the following tables:



To resolve this issue, backup your K2 Database and correct the paths in the asmFullName columns of [EventBus].[EventPolicyMapping] and [EventBus].[LogEventPolicyMapping] using SQL REPLACE functionality.