Symptoms
Activating the K2 for SharePoint app did not work as expected. It fails on the activation step.
Diagnoses
Client created a couple of groups and used one of those groups to assign permissions to in K2. After that was done, the SP group was deleted. When we tried to activate the new app, we looked for the SP group IDs, were not able to find them, and activations failed. We found the following in the SmartObject logs:
BrokerPackageIn ' ------------------------- 10/18/2016 7:24:04 PM <brokerpackage> <smartobject name="site_sharepoint_com_Management_Group" guid=" xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" version="x" resultname=""> <property name="GroupIds"> <value>100101</value> </property> <method name="GetGroupTitlesForIds" /> </smartobject> </brokerpackage>
BrokerPacakgeOut' ------------------------- 10/18/2016 7:24:04 PM <brokerpackage> <brokerpackage> <result successful="false"> <serviceinstances> <serviceinstance name=" site_sharepoint_com" guid=" xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx "> <messages> <message severity="Error">Group cannot be found.</message> </messages> </serviceinstance> </serviceinstances> </result> </brokerpackage> </brokerpackage>
Resolution
As a workaround, you can click the "Configure K2 Permissions link". When the list of groups loads, the "deleted" group will no longer be there and when you hit OK, K2 will update the entries in the internal lists, and this should not happen anymore. After all this is done, we were able to activate the K2 App without issue. (We have task logged in TFS to address this issue. This should be addressed in a future build of Appit/blackpearl.)
