Unable to activate K2 for SharePoint app after migration from to 2010 to 2013 - The remote server returned an error "(404) Not Found"

  • 16 February 2021
  • 0 replies
  • 49 views

Userlevel 5
Badge +20
 

Unable to activate K2 for SharePoint app after migration from to 2010 to 2013 - The remote server returned an error (404) Not Found

kbt152203

PRODUCT
K2 blackpearl 4.7
BASED ON
K2 blackpearl 4.7
TAGS
K2 for SharePoint (WSS)
Upgrading
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.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

You are unable to activate the K2 for SharePoint app for site collections with the following error appearing on the activation stage (logged in host server log):
"0 System.Exception: The remote server returned an error: (404) Not Found."

Symptoms

You migrated from SharePoint 2010 to SharePoint 2013 (15.0.50.47) and are unable to activate the K2 for SharePoint app for site collections with the error appearing on the app activation stage.

Resolution

To resolve this error it is necessary to delete the SharePoint 2010 web parts for K2 from the target site collection web part gallery. To access the web part gallery just add "/_catalogs/wp" to the site URL (e.g. http://portal.denallix.com/_catalogs/wp) to locate old K2 web parts and delete them.

There can be 2-3 of them, all containing "K2" in their name, e.g. "K2 Worklist.dwp" and "K2TaskList.webpart" and their deployment date should allow you to distinguish them from items installed along with the new version which should not be removed.


0 replies

Be the first to reply!

Reply