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. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We're analysing a deadlock situation on a SQL Server 2005 database and have set the trace flags 1204 and 1222.

In the resulting logs we're seeing the following line repeatedly:

"Log Viewer could not read information for this log entry. Cause: Data is Null. This method or property cannot be called on Null values."

Can anyone tell me what's likely to be causing this? There's nothing particularly wrong with the queries that I can see (they're generated by Hibernate so are a bit messy and full of aliases but are fundamentally sound).

Is it something I need to worry about or something that can be ignored?

share|improve this question

Something wrong with the viewer (looks like the bug in SSMS), but you always can open ERRORLOG in any other viewer, such as notepad and get exactly the same info

share|improve this answer

Probably just a client (SSMS) issue rendering the error log.

xp_readerrorlog will make it easier to parse the deadlock entries from the error log and bypass the display bug.

share|improve this answer

Your Answer


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.