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.
The objective is to provide additional information with regards to setting up an environment that fits the description of multiple K2 servers pointing to one SharePoint Farm.
Before You Begin
Before you begin, read and implement the following: How to allow multiple K2 Servers to use the same SharePoint 2013 Farm.
Run the registration wizard, and if you hit a 401 then iterate through the "how-to-steps".
- Run the following query on both boxes:
SELECT * FROM [HostServer].[Configuration] WHERE VariableToken = '[SHAREPOINT_HIGHTRUST_ISSUER_ID]'
- The 'VariableValue' should jibe across environments. If not, this is the root of the issue and an UPDATE script will need to be run against the second K2 machine using the 'VariableValue' from the first machine.
UPDATE HostServer.Configuration SET VariableValue = 'VALUE FROM FIRST BOX' WHERE VariableToken = '[SHAREPOINT_HIGHTRUST_ISSUER_ID]'