KB001569: K2 Package and Deployment (4.13210.1.0) Known Issues List

UPDATED

Introduction

The following issues are currently known for K2 Package and Deployment (4.13210.1.0). Workarounds are included where possible.

Known Issues

The following issues are known for the K2 Package and Deployment (4.13210.1.0) release:

1. Processes cannot be ‘re-bound’ to an existing Form or View within a target environment, should the Target Form or View not have the same GUID as the Source Form or View. 
2. When deploying a workflow designed using K2 Designer that contains SharePoint events, deployment may fail due to the SharePoint URL not being updated.
3. When deploying a Process built on .NET 3.5 to a server running .NET 4.0 within certain environments, the target files are not placed in the correct location and the following error will be registered: 'error MSB4019: The imported project "c:WindowsMicrosoft.NETFramework64v3.5Workflow.Targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.'
   Workaround: Copy *Workflow.Targets* and *Workflow.VisualBasic.Targets* from  C:Program FilesMSBuildMicrosoftWindows Workflow Foundationv3.5 to: C:WindowsMicrosoft.NETFramework64v3.5 (or to the relevant folder if within an x86 environment).
4. SharePoint SmartObjects do not deploy.
   Workaround: When using SharePoint SmartObjects, ensure that:
   a) The relevant lists and libraries exist within the target environment, and
   b) The SharePoint site utilizes the same site template as the source environment.
5. Deselecting the root category node in order to de-select all artifacts comprising a solution, results in relevant items within the ‘Uncategorized’ node not being de-selected.
   Workaround: When de-selecting chosen artifacts, ensure that all relevant artifacts which may be present within the ‘Uncategorized’ node are manually de-selected.
6. When deploying a package under the following conditions:
   a) The package contains a process with a User or Group field part in the destination, and
   b) the field part’s security label does not exist on the target environment,
   An error is registered on the host server and the ‘Next’ button is not enabled.
   Workaround: Ensure that all security labels which are present on the source environment also exist on the target environment prior to package deployment.
7. Where K2 Package and Deployment is installed before installing K2 smartforms, deploying a package containing Views and Forms will result in missing references for the out-of-the-box controls.
   Workaround: Perform a repair of the K2 Package and Deployment installation after installing K2 smartforms.
8. Where workflows are deployed within Package and Deployment, the deploying user subsequently becomes the ‘owner’ of the relevant workflow and must enable ‘sharing’ prior to other users being able to see or edit the workflow. Should the SmartForms installation for that environment be configured to run Claims Authentication, the deploying (AD) user will not be able to log into the SmartForms site in order to grant sharing permissions after deploying the relevant package.
   Workaround: Should SmartForms be configured to run Claims Authentication, deploying packages as a ‘Claims’ user will enable the deploying user to see the workflows and grant relevant sharing permissions. Within the Package and Deployment tool, edit the server settings, ensuring that the 'Integrated Security' checkbox is not checked.
9. After repairing a K2 blackpearl installation, the Package and Deployment installation within the same environment does not function correctly, and an error stating ‘System.Configuration.ConfigurationErrorsException: The sourceCode.extensibility.primaryCatalog configuration section is missing…’ is given.
   Workaround: After repairing K2 blackpearl, the Package and Deployment ‘reconfigure’ option must be chosen from the K2 Package and Deployment Setup Manager.
10. When downloading a process containing SmartWizard events from Workspace, an object-reference error occurs when attempting to open the *.KPRX file.
    Workaround:
    a) Open the *.KPRX file in a text editor (such as Notepad). Locate the SmartWizard path node.
    b) Replace the value in the SmartWizard path node with the value which points to the wizard *.XML file on the machine (i.e. oINSTALLDIR]BinDesign TemplatesSmartWizards.Category]DWizard])
    Where:
    iINSTALLDIR] = C:Program Files (x86)K2 blackpearl
    ]Category] = CRM 2011
    bWizard] = Create CRM Entity Item
    c) Click ‘Save’.
    d) Re-open the *.KPRX file in K2 Studio or K2 Designer for Visual Studio. The wizards can now be edited.
11. When upgrading K2 blackpearl to version 4.6.5 from previous versions, the error messages for K2 Package and Deployment (4.13210.1.0) (stored in the HostServerLogging.config file) are not preserved. This issue may also occur when upgrading K2 smartforms to version 1.0.3 from previous versions.
    Workaround: Run the K2 Package and Deployment (4.13210.1.0) installer. Select the Reconfigure option in order to restore specific Package and Deployment error messages.
    This issue is not applicable where K2 blackpearl 4.6.6 is being used.
12. Where culture settings which affect decimalization vary between a source environment and target environment, the process fails to deploy and an exception which states that the input string is not in a correct format is generated.
    Workaround: Ensure that machines hosting source environments from which deployment packages originate, and machines hosting target environments to which the packages will be deployed, both use the same decimal culture settings. The K2Hostserver must be restarted wherever decimal culture settings have been changed.
13. If SmartForms categories include a back slash (i.e. ) or forward slash (i.e. /) in the category name, the associated SmartObjects, forms and views will not be visible within Package and Deployment. This is also accompanied by unexpected behavior within SmartForms (category names utilizing forward- and/or back-slashes will typically be re-grouped within an automatically-created sub-category called Category > -No Name-, rendering them inaccessible under their original path).
    Workaround: When naming SmartForms categories, best practise is to refrain from using forward slashes or back-slashes as part of the category name.

14. When deploying a Process containing ProjectReference(s) (i.e. where the Reference type is listed as 'Project' in the Process References window), the following error will be encountered during deployment:

    System.Reflection.TargetInvocationException: Value cannot be null. Parameter name: path2

    Workaround:

    a) In the Source environment, open the Project using K2 Designer for Visual Studio.
    b) Right-click on the process Start icon. Select Properties.
    c) In the Configuration menu, click on the Process References icon. The Manage Process References window will appear.
    d) Locate and make a note of all processes where the 'Type' is listed as 'Project'. Remove these Project Reference(s) by clicking on them and clicking the Delete button.
    e) Click the Add button in the Manage Process References window.
    f) The Add References window will open. Click on the .NET tab.
    g) Search for the previously deleted reference(s) in the Component Name column. Click on the correct reference(s) and click the Select button.
    h) Click OK. The reference(s) will be re-added as an Assembly Reference (i.e. listed as .NET).
    i) The reference(s) will now be visible in the Manage Process References window. Locate the reference(s), ensuring that it's Copy Local check box is checked.
    j) Recreate and redeploy the deployment package.