Symptoms

After the SharePoint content DB was restored from SharePoint production to SharePoint test the K2 integration stopped working. We need to get it working again - there are no productive K2 workflows in test - and we need to find a way how to refresh the SharePoint test environment without loosing the K2 integration.

 

Diagnoses

There are many errors in the K2 Host Server error log trying to reference the old PROD SP server name / site collection name but it doesn't work on DEV.
 

Resolution

The downloaded K2 Blackpearl installation package setup.exe has to be run on the SP server on DEV (where the content DB has been overwritten).

Then the K2 for SharePoint component has to either be re-installed (by selecting Modify) or a Repair should be run. After that, the K2 components should be re-deployed to the SP server after the installation (post deployment), following that the K2 features should be activated on all site collections that need to interact with K2.

After all the above has been done, K2 integration with SP has been restored.