How to resolve "Token-based server access validation failed with an infrastructure" error?
Hello,
On a regular basis in the Windows Application and SQL Server logs, I see these errors:
SQL Server Log:
Login failed for user 'domain\acct'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
Windows Log:
SQL database login for 'SharePoint_Config' on instance 'SERVER' failed. Additional error information from SQL Server is included below. Login failed for user 'domain\acct'.
I don't know what application is needing access, and I don't think what ever it is needs access.
Is there a way to tell what application is trying to access SQL Server and the IP address?
Thanks.
On a regular basis in the Windows Application and SQL Server logs, I see these errors:
SQL Server Log:
Login failed for user 'domain\acct'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
Windows Log:
SQL database login for 'SharePoint_Config' on instance 'SERVER' failed. Additional error information from SQL Server is included below. Login failed for user 'domain\acct'.
I don't know what application is needing access, and I don't think what ever it is needs access.
Is there a way to tell what application is trying to access SQL Server and the IP address?
Thanks.
ASKER
I am working with Symantec now on this problem. I will post a solution, once I have it resolved.
Hi PBIT,
Why Symantec?
Regards
David
Why Symantec?
Regards
David
ASKER
When I view the propertieis of a job in Backup Exec for a server, that error and 2 others occur in the Application Event Log on the remote server. We are just backing up the folders on the remote server, but Backup Exec is trying to access the SharePoint config database.
Hi,
Generally backup software should leavel the mdf and ldf files alone, unless you have the SQL Agent and are using that.
Now that you mention Backup Exec it makes sense that you are working with Symantec.
Regards
David
Generally backup software should leavel the mdf and ldf files alone, unless you have the SQL Agent and are using that.
Now that you mention Backup Exec it makes sense that you are working with Symantec.
Regards
David
ASKER
I wondering if I should close question. I can leave it open, but the problem is with Backup Exce.
Hi,
Is there a Backup Exec topic area that the moderators could help you add?
Regards
David
Is there a Backup Exec topic area that the moderators could help you add?
Regards
David
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I called Symantec and got some answers from them. Please close question. Thank you.
Hi PBIT,
1. Make sure the service account of the SQL instance being used is set to Local system account.
2. Logon as a Domain administrator which is also a 'sysadmin' (By default, the local administrators group is a member of the sysadmin server role on the SQL Server database.).
3. Restart the SQL Server service.
4. Retry the job.
1. Make sure the service account of the SQL instance being used is set to Local system account.
2. Logon as a Domain administrator which is also a 'sysadmin' (By default, the local administrators group is a member of the sysadmin server role on the SQL Server database.).
3. Restart the SQL Server service.
4. Retry the job.
If it is the same sort of errors I'm working through, it appears that the SQL Server service account doesn't have enough rights to read the Active Directory for the Sharepoint Account.
it is possible that SQL is NOT running under a Domain Account, which is best practice.
Fix - create domain account.
...
HTH
David