< class="prominent-subhead ">

Unable to activate site error raised on SharePoint Broker step

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.
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.


When Activating a SharePoint site, K2 raised an error: 
"The remote server returned an error: (502) Bad Gateway. "


The 502 bad gateway was raised because the K2 App url that was used, was incorrect and was not updated to the new App url.


The URL used for the K2 App Activation on SharePoint sites can be found in the [Integration].[ProcessSharePointGeneralSetting] for type AppSiteUrl and AppCatSiteUrl.

If this issue is observed, please log a support ticket. K2 support will assist in changing this.