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.
When deploying from Server A to Server B with Package & Deployment and referencing assemblies in K2 for Visual Studio - the below error will appear:
The assemblies are not present, in other words the assemblies were not added to the Global Assembly Path on the destination enviroment where you are deploying to.
To bypass this error on Package & Deployment, go to the K2 Visual Studio and check the referenced assemblies:
Next, the assemblies that are ticked need to be added to the destination environment Global Assemblies, by using the GAC Utility
Source location to copy from - Path : C:\Windows\assembly\GAC_MSIL
After copying the dll's files to the destination server, register them with the GAC Utility as below:
After completing the apply of the assemblies, you will be able to deploy your workflow process successfully to the destination environment.
Before apply the dll's on the enviroment please ensure that the DLL is not blocked.