Skip to main content
Nintex Community Menu Bar
Question

K2 List Method Error

  • February 26, 2025
  • 4 replies
  • 27 views

Forum|alt.badge.img+2

As part of a database migration, I’ve created a new Service Instance to connect an existing form to a new server. The service account has been created and given full permissions. The connection is active, and the form can write to and read from the database.

 

However, when attempting to execute the List method, the below error occurs:

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

 

What is the cause of this and how can it be resolved?

Translate

4 replies

Forum|alt.badge.img+13
  • Scholar
  • 499 replies
  • February 26, 2025

How is your service instance configured for authentication? 

Translate

Forum|alt.badge.img+2
  • Author
  • Rookie
  • 5 replies
  • February 26, 2025

It’s set to service account, although I have tested with Static and Impersonate, which also produce this error only on the list method.

Translate

Forum|alt.badge.img+13
  • Scholar
  • 499 replies
  • February 26, 2025

I don’t have it in front of me at the moment but I think there is a setting of some kind like “on same SQL server” - try toggling that value to see if it makes a difference in the error message.

Translate

Forum|alt.badge.img+5
  • Nintex Employee
  • 46 replies
  • February 26, 2025

It looks like the issue is related to Kerberos authentication and how credentials are being passed from K2 to SQL Server. The error Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON' suggests that there is a double-hop authentication issue when executing the List method.

A few things to check:

  1. Service Instance Authentication: Since you've tested different authentication modes, confirm that the service instance is set to use Service Account and that the account has appropriate permissions on SQL Server.

  2. Delegation & Kerberos Configuration: If your K2 environment is using Kerberos, ensure that:

    • The K2 service account has "Trust this user for delegation" enabled in Active Directory.
    • The SQL Server instance has the correct SPNs registered (MSSQLSvc/<servername>:1433).
    • You are using Constrained Delegation if your K2 server and SQL server are on separate machines.
  3. K2 Service Account Permissions: Verify that the K2 service account has the necessary database permissions for executing the List method.

  4. "On same SQL Server" Option: As @tbyrne777 mentioned, toggling this setting in the service instance might help. If your SQL Server is on a separate machine, K2 may not be correctly handling authentication across machines.

  5. Check K2 Logs & SmartObject Tester: Try executing the SmartObject method using SmartObject Tester to see if the issue occurs outside the form as well. Additionally, check K2 host server logs for any additional details.

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings