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.
If you have used SharePoint Template Packs (STPs) to move lists between sites on the same environment, a suppressed error occurs during deployment of a K2 pacakge to the list if the list lookups have not been configured.
When using STPs between sites on different environments, a K2 deployment exception error appears if the list lookup has not been configured. When moving between subsites, however, the service instance name remains the same and the SmartObject call is succesful, and the K2 deployment continues.
When adding an item to the deployed list, the "Sorry, something went wrong - An unexpected error has occurred" error message displays.
The following error message shows in the deployment log:
Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object.
at SourceCode.Categories.Client.CategoryServer.UpdateCategoryData(Category newCategory, CategoryData categoryData)
at SourceCode.Runtime.Services.SharePoint.DeploymentCollator.MoveCategoryDataInternal(CategoryServer categoryServer, CategoryManager categoryManager, Category deployedToCategory, Category newCategory, ComplexType complexType)
at SourceCode.Runtime.Services.SharePoint.DeploymentCollator.MoveCategoryData(CategoryServer categoryServer, CategoryManager categoryManager, Category deployedToCategory, Category newCategory, IEnumerable`1 objectList, List`1& unassociatedObjects)
at SourceCode.Runtime.Services.SharePoint.DeploymentCollator.DoPostDeploy(DeploymentPlan plan)
at SourceCode.Deployment.Runtime.ServerSession.AsyncDeploy() 00:00:00.1513582
Configure the lookups to the list, then redeploy the solution.