Post reply

Log Writer Error

  • July 10, 2002 at 10:44 am

    #173207

    I encountered a strange problem today, and have not been able to find much on the topic, so I will throw it out here...

    I got this message in my error log:

    LogWriter: Process 2 generated an access violation. SQL Server is terminating this process.

    SQL Server pretty much froze, as I would guess I would expect it to if the log writer went down. I was not able to find anything that would help, so I rebooted the server, and everything seemed to come up OK.

    I also got a few of these messages ( always in pairs ). Which I assume was SQL trying to tell me that it was stuck waiting for a log writer.

    WARNING: EC 54b754d8, 0 waited 2100 sec. on latch 42d233b0. Not a BUF latch.

    Waiting for type 0x4, current count 0xa, current owning EC/PSS 0x466994F8/0x466991E8.

    Anyone seen anything like this before? I am running SQL2K on WIN2K

    Is there any way to kick start a new log writer process? It has been a few years, but I seem to remember being able to do that in Oracle.

    Is there anything I should look at that might have caused this glitch?

    Thanks for any insight anyone may have!

    Curt

  • July 10, 2002 at 3:45 pm

    #432388

    Are you using AWE memory by chance?

    If so check this out:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q309093

  • July 10, 2002 at 3:47 pm

    #432390

    I found one more refrence to the error:

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q322379

  • July 10, 2002 at 4:06 pm

    #432393

    Thanks, no, I am not using AWE, and many of the resources I have found have dealt with those problems, more specifically the 2nd error messages I was getting.

    I believe ( and I could certainly be wrong ) that those were the result of the first message that said the logwriter had an error was stopped. I could not tell if the log writer actually was stopped, sp_who did show that it was there as spid 2, but that could have been misleading if it was hung up.

  • July 10, 2002 at 7:26 pm

    #432401

    Check out this KB article

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q310834

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • July 11, 2002 at 9:19 am

    #432485

    I saw that article, but I don't particularly like it.

    It almost like Microsoft created the article just to let us know that they really have no clue why the error is occurring. It never explains why changing your memory, or threading configuration might correct the issue.

    I had the same buffer latch issue on a box and no matter what memory configurations I used it still showed up every once in a while. The only way it was corrected was a complete rebuild on a different machine.

    Maybe you'll have better luck with it than I did.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply