Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

SQL Error 18452 state 1 and : Token-based server access validation failed with an infrastructure error

Posted on 2013-11-14
2
Medium Priority
?
870 Views
Last Modified: 2013-11-27
I have been researching this error for the SQL though I am a Sys Admin because he believes the error is not with his SQL despite the mounds of documentation I have presented him with including everything from UAC, SPN, SID, time differences, web config, invalid ID, password, check that database connection using Kerberos authentication etc.

His reasoning is the errors is not continual for the account identified. Meaning the account an App server uses to connect to the SQL Server and Database works most of the time but has thrown the 18452, 17806, along with "Login failed for user 'Domain\Services'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>])"

The issue occurs about twice a day without a routine and last only for a few minutes and then the connection is reestablished and all is well. The problem is if there is large data project going during the fail the project must be redone which is a severe impact on our clients and business.

Questions
1. Has anyone seen this error in the inconstant state we do?
2. Can someone please verify that this is not an AD issue but rather a SQL issue?
3. Any ideas?

Also, I will say I can not confirm he has tried all suggestions and even stated:
1.      Because we’re not open network we don’t use Kerberos explicitly, we make connectivity over TCP using NTLM & SQL authentication. Kerberos is good if you’re making connectivity in open network
2.      Also this error is not a continual error, we’re experiencing for few seconds or sometime few minutes, so obviously not the account lock or password error. These accounts are service accounts and configured for no lock mode.
3.      We are not using any local account, all application/service accounts are domain based account.
4.      Config file should not be an issue because these errors appears as a fluctuations for few minutes

Any help is more than appreciated. Please anyone so I can tell him this is an SQL or Network (maybe) issue and not AD.

Kry
0
Comment
Question by:kryanC
2 Comments
 
LVL 49

Accepted Solution

by:
PortletPaul earned 1500 total points
ID: 39650203
This all seems related to security, Are you also seeing error 18456?
(but, warning, this is NOT my specialty)

e.g.
that 17806 relates to "Security Support Provider Interface" (SSPI), possibly IIS not running under a domain account with access the SQL server or impersonating that

error       severity       description

17806       20       SSPI handshake failed with error code 0x%x, state %d while establishing a connection with integrated security; the connection has been closed. Reason: %.*ls %.*ls.

18452       14       Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.%.*ls

18456       14       Login failed for user ‘%.*ls’.%.*ls%.*ls

You probably do want to investigate the logs more carefully, those parameterized (%) values in the descriptions above  reveal more specific information.

I'd suggest you read this
Troubleshooting Login failed Error 18456
and then perhaps re-discuss with all related security folk in one room.
0
 

Author Closing Comment

by:kryanC
ID: 39681553
thanks we are now capturing the packets that generate the error and believe it is an App that runs daily. Hope to have a clear resolution soon.

Kry
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A procedure for exporting installed hotfix details of remote computers using powershell
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question