This one had me going for a while. I was getting a Failure Audit entry in the Application event log every minute, looked a bit like this
Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Date: 5/25/2007
Time: 1:57:00 AM
User: TNG\TNG-SQL_Service
Computer: SHAREPOINT
Description:
Login failed for user ‘System’. [CLIENT:
I started, stopped, restarted etc. all SQL related service. Changed passwords… nothing helped.
Inspetcing the SQL server logs, I soon found some errors, in particular “Cannot open database “SharedServices1_DB” requested by the login. The login failed.
Well that makes sense, seeing as my SSP is running on SharedServices2 – there used to be a SharedServices1 but I had deleted it when it got a bit confused over its identity. What stumped me then was what on earth was still trying to access the old database? Looked all through SSP admin, Central Admin.. until, there in SQL Server Agent Jobs was a job to clear up expired sessions. Must be created automagically when you create a new SSP, but cunningly doesn’t kill the job when an SSP gets deleted.
Needless to say, killing that job and my event log is now just full of errors, as opposed to the bloody annoying failure audits.
Leave a Reply