June 16, 2008 at 9:55 am
The following error keeps occurring every 30 minutes in error logs. "The specified user account has expired".
Has anyone ever come across this error message?
June 16, 2008 at 10:09 am
Is it a domain account? If so, most likely it's a scheduled job that's using a domain account to connect to your server, and that account has expired within Active Directory.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 16, 2008 at 10:32 am
It is a domain account but it is not a scheduled job and also the account has not expired in Active Directory.
June 16, 2008 at 10:46 am
I haven't seen this. Is there anything strange about the account? I'd run profiler and see what's using this account, what it's doing. that might help clue things in.
June 18, 2008 at 8:06 am
Is there a particular message within the profiler to look at or should I look out for an error message?
June 18, 2008 at 9:23 am
I have the exact same problem. The event error is being generated from the System account, but it is complaining that the service account running my SQL services has expired. This is not the case because those services are still running and SQL itself is working.
June 18, 2008 at 9:38 am
If the service account is expired, you might not have an issue until the SQL service restarts. It is running and like a live user, it doesn't necessarily get kicked off. But if it does something that needs rights checked, it might fail.
I'd schedule a SQL Server restart and be sure the account is set to never expire.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply