Workspace Error: AcceptSecurityContext failed: The logon attempt failed

  • 16 February 2021
  • 0 replies
  • 91 views

Userlevel 5
Badge +20
 

Workspace Error: AcceptSecurityContext failed: The logon attempt failed

kbt130829

PRODUCT
K2 blackpearl
TAGS
K2 Workspace
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

When you are setting up a K2 Cluster environment, on the first server everything seemed fine. On the second server the installation is completed as normal but when going into Workspace you are presented with the following error: 24404 Authentication with server failed for accountname@domain.NET with Message: AcceptSecurityContext failed: The logon attempt failed" What could be the cause of this error.

Symptoms

The following error you see within Workspace and this can also be seen within the log files as well: "accountname@domain.NET with Message: AcceptSecurityContext failed: The logon attempt failed" can happen if you have a web site that uses Integrated Authentication and is hosted on IIS 5.1 or above.

 

This is per the Microsoft article below:

 

https://support.microsoft.com/en-gb/help/896861/you-receive-error-401.1-when-you-browse-a-web-site-that-uses-integrated-authentication-and-is-hosted-on-iis-5.1-or-a-later-version

Resolution

To resolve this issue please do the following:

 

To set the DisableLoopbackCheck registry key, follow these steps:

 

 

Set the DisableStrictNameChecking registry entry to 1. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

 

https://support.microsoft.com/en-us/help/281308/connecting-to-smb-share-on-a-windows-2000-based-computer-or-a-windows-server-2003-based-computer-may-not-work-with-an-alias-name

 

- Click Start, click Run, type regedit, and then click OK.

- In Registry Editor, locate and then click the following registry key:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa

- Right-click Lsa, point to New, and then click DWORD Value.

- Type DisableLoopbackCheck, and then press ENTER.

- Right-click DisableLoopbackCheck, and then click Modify.

- In the Value data box, type 1, and then click OK.

- Quit Registry Editor, and then restart your computer. You should be able to go into Workspace without seeing any errors.


0 replies

Be the first to reply!

Reply