Every SQL job fails that's associated with an NT account we setup called 'SQLServices'. It's been in production and working fine for the past year.

The account is used by MSSQLSERVER and SQLAgent services. They work fine. I can successfully login to a server or database with the login but anytime we run a job it receives the message: "Could not obtain information about Windows NT group/user 'SENTARA\SQLServices'."

Further research revealed that it was issuing a State 25 which means: "An error occurred when the SQL Server engine queried the Windows operating system to retrieve information about a Windows account name."

My systems people are suggesting that we drop the NT login then re-add it. Anybody got a better solution?

Sidney Ives
Database Administrator
Sentara Healthcare.