Symptoms
Transported K2 application and Web Parts in SharePoint keeping the app url of the source environment.
When we transport SharePoint site and nested K2 applications in our Central farms, we notice that both the K2 application in Site contents and the K2 WebParts in the SharePoint site pages keeps the url of the apps of the source / sandbox environment.
Usually we:
1) transport SharePoint site collection (with restore)
2) enter it and add the SharePoint and K2 service accounts as site collection administrators
3) we remove the K2 app from site contents
4) we re-add the K2 app and trust it
5) we run the registration wizards of the K2 app > pointing to the K2 farm of central farms
6) we synchro the SharePoint groups
7) we deploy the K2 package
After this, both the K2 app than the K2 web parts point to the correct K2 farm, but their url is still the one of the app in the sandbox. This starts a prompt for credentials that is very annoying until we don't put the url in the IIS binding (but it is not what we want, as it is an url not correct for the environment)
Diagnoses
We recommended the client test with our recommended steps as this is the correct and safest way to migrate their environment.
Step 1 ? Create a new Site Collection on your QA SharePoint server.
Step 2 ? Create List/Library Templates from Development Server and deploy to QA Server.
*Step1B and 2B ? Create Site Template from Development and deploy to QA ? This should work as well, however I do not know your entire setup. But a site template should work, instead of creating a new site and using doc/list templates. If this does not work. Please use the recommended procedure above.
Step 3 ? Add the K2 app and run the registration ? use a Global Admin account as per our documentation.
Step 4 ? Deploy Package (using PandD) from Dev to QA.
Points to note. Please do NOT refresh, add, change, or edit the SharePoint Service instance, or SharePoint SmartObject through the SmartObject tester tool. For any management please use the K2 App in SharePoint itself
Resolution
Client went through the recommended steps and confirmed the issue no longer occurs.
