Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

The failed job is a Litespeed transaction log backup, but also happens to fulls and diffs occasionally.

This same setup works on other servers without issue, and it's only a few times overnight that the error occurs, but it does happen every night at some point:

Error in SQL Server Agent Log:

"Logging on to SQL Server 'SQLFOO' with Windows Authentication TWideSafeCallErrorException - Timeout expired C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\slssqlmaint.exe"

Error in Litespeed log:

"Msg 49999, Level 19, State 1, Line 0 Failed to login to SQL Server".

Is there anything I can look for on the server that would give me a clue as to why there is an intermittent login error?

EDIT: More information - A scheduled query was discovered that runs across this time period for several hours, all the failures happen during this time period. The transaction log backups that do complete are taking 10 minutes compared to less than a minute to complete as they normally do.

EDIT2: No transaction log failures when the job isn't running. There is one update script that while running still causes the trxlog backup to fail with the logon authentication error. It's an update script that hits a ton of records, I guess it's time to put on my junior_dev hat.

share|improve this question
1  
I'd also check with the sysadmin to see if you can correlate your issues with things happening at the network or domain controller level. I had this happen in the past and it was because the domain controller was also the dns server and the timing was such that the SQL process was hitting at the time of DC failover during a maintenance reboot. Every month. Like clockwork. –  swasheck Jan 9 '13 at 3:14
add comment

2 Answers 2

up vote 3 down vote accepted

I've seen this happen both with network DC issues and also with a system that had too many connections and not enough memory.

share|improve this answer
    
I'll check into a way to track the connections. This is somewhat of a unique instance as it is being abused as a "hub" with linked servers to other instances for nightly data yanks. –  Alan Whited Jan 9 '13 at 19:50
add comment

There might be something useful in the SQL Server ERRORLOG file but probably not. It is probably a network timeout between the SQL Server and the domain controller.

share|improve this answer
    
ERRORLOG doesn't show errors, but did show that once the job failed on a particular database. Possibly a separate issue there. Researching how I can track the network timeout to DC. –  Alan Whited Jan 9 '13 at 19:47
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.