< class="prominent-subhead ">

Can not install K2 Workspace, fails with error'Sourcecode.Security.Window.WindowsTokenService has stopped working'

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

Installation of the K2 Workspace in server fails with the following error appearing: 'Sourcecode.Security.Window.WindowsTokenService has stop working'.

Image

Symptoms

After looking at the InstallerTrace file (located in C:\Program Files (x86)\K2 blackpearl\Setup\Log) the following error was found: 

"'Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.IdentityModel.WindowsTokenService, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. at SourceCode.Security.Windows.Program.Main(String[] args)' ConfigureBase.EnsureTokenService: 16:04:43: Stop service if it is started SourceCodeLog.LogMsg: 16:04:43: Logged Error: K2 Workspace error: Cannot open K2WTS service on computer '[ServerName]'." 

This error appears because the server doesn’t have the Windows Identify Foundation installed on the machine.  To resolve this issue, download and install or enable the Windows Identify Foundation:

Image

Troubleshooting Steps

1. Verify the Microsoft.IdentityModel.WindowsTokenService assembly on path (C:\Windows\assembly)

2. If it does not appear, enable the Window Identity Foundation feature

3. Reinstall the K2 Workspace component.