<{{Subtitle_Weight}} class="prominent-subhead {{Show_Subtitle}}"> {{Header_Subtitle}}

K2 activation fails with Oauth invalid_resource error

~~repeating-content.html~~
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

Attempting to activate K2 to a site collection may fail with one of the following errors:

SourceCode.Hosting.Exceptions.AuthenticationException: OAuth Error: Code=invalid_resource : Description=AADSTS50001: The application named https:/allixportal.sharepoint.com was not found in the tenant named {guid}.  This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant.  You might have sent your authentication request to the wrong tenant.

Or

Thread 1: OAuth Error: Code=invalid_resource : Description=AADSTS500011: The resource principal named https:/llixportal.sharepoint.com was not found in the tenant named {guid}. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.

Symptoms

1.  You are running K2 version 4.7.

2.  The protocol of the URL in the error stack trace appears to be missing a second forward slash; so it is https:/ instead of https://

Resolution

If you are experiencing either one of these errors, please apply at least the 4.7 March 2018 CU and the 4.7 March 2018 CU FP14 to resolve the issue.

As Fix Packs (FP) are cumulative, the latest 4.7 March 2018 Fix Pack can also be found at:

https://help.k2.com/kb002282