Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-12-17 : 08:16:02
|
| Steve writes "I am investigating the cause of deadlocks and have noticed that the 1205 error is not being logged to the SQL Server error log or the O/S application log. Is there a setting that I have missed or is this expected behavior?Further I have tried created two alerts (both an event alert and a performance condition alert) without success.I can create an entry for the 1205 error on my local machine (running XP Prof SQL Developer Edition). I am trying to have the 1205 error write to both logs on a W2K server SQL 2000 EE.When I run Profiler on my local machine I see the event log event taking place for the deadlock. I do not see it happening on the servers running the same trace.Any ideas would be appreciated,Thanks" |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2002-12-17 : 08:40:27
|
| You need to enable traceflag 3605 to get 1204 and 1205 to write to the SQL errorlog.HTHJasper Smith |
 |
|
|
|
|
|
Error 1205 Not Writing to Error/Event Logs