Introduction

After installing or upgrading to K2 4.5 RTM, the K2 Designer for SharePoint solution for example may not display a “Deployed” status. The K2 for SharePoint - Web Designer.wsp is a large solution and may not complete the deployment on a slow environment. An error is displayed in the Configuration Analysis Tool and is written to the installation log.

Error Scenario

Install or upgrade to 4.5 RTM. Certain solutions may not display the “Deployed” status after installation or upgrade.

Error Messages

Error displayed in the installation log:

04:31:57","Error","15","15002","ERROR","SourceCode.ProcessDesigner.Configuration.Config","15002 The following solutions could not be repaired automatically:","anonymous","0.0.0.0","blackpearl","14333","038a73c9590743729ef1fa07f677f928",""

"14334","2010-04-10 04:31:57","Error","15","15002","ERROR","SourceCode.ProcessDesigner.Configuration.Config","15002 K2 for SharePoint - Web Designer.wsp","anonymous","0.0.0.0","blackpearl","14334","3027eb0e690d4df88f336c2f13f4b409",""\

Error Resolution

This Hotfix is contained within the latest K2 Update. Install the update package to resolve the error. 

The Configuration Analysis Tool now offers the option to repair solutions which were not completely deployed upon installation. The repair should be run on each Web Front End server in the Farm to ensure that the status is set to “Deployed”. The repair button for the task is only available if the current machine is in the list of machines that are in deploying state. A link is provided at the bottom of the task for more information on how to fix these “deploying” machines.

Following is an image which shows the behavior of the Configuration Analysis Tool when a solution has been detected as being in deploying state.