Hot-fix for CMS Client Event that inadvertently triggers additional K2 Process instances to be generated
LEGACY/ARCHIVED CONTENT
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.
A CMS client event submit will cause any workflow that improperly triggers on a CMS submit to launch another process instance.
| How to Reproduce the behavior: Run the K2.net 2003 Integration assistant from CMS to K2-enable the CMS channel's submit event. Submit a posting in this channel. The K2 process will be started. Using a CMS Server event in the K2 process, submit the posting. This will trigger the start of a new K2 process, orphaning the current process. Symptoms: A second process has started even though no secondary CMS-driven event has occurred. Workaround: | |||||
| 1. | Obtain the new hot-fix binary files from the K2 Support team: | ||||
| |||||
| 2. | Copy the attached binary files from the mail to the following location on your system: C:Program FilesMicrosoft Content Management ServerServerIIS_CMSK2v3 [Enter] | ||||
| 3. | From the Visual Studio Command Prompt, type: gacutil /i "C:Program FilesMicrosoft Content Management ServerServerIIS_CMSK2v3CMSK2EventModuleCMSK2EventModule.dll" /f [Enter] | ||||
| 4. | From the Visual Studio Command Prompt, type: gacutil /cdl [Enter] | ||||
| 5. | Stop and restart the IIS service (or type IISReset from the Windows command prompt).
| ||||
