Microsoft KB Archive/172557

= FIX: Lazy Writer Process May Cause an Access Violation =

Article ID: 172557

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q172557



BUG #: 17017



SYMPTOMS
If tempdb is in RAM, heavy tempdb usage may cause the lazy writer processes to have a handled access violation (AV). This will appear in the SQL Server errorlog as the following message:

Lazywriter: Process 2 generated access violation SQL Server is

terminating this process

This message may occur once or hundreds of times, and can also cause SQL Server to eventually stop responding.



WORKAROUND
To work around this problem, do either of the following:


 * Move tempdb out of RAM to a physical disk.

-or-
 * Reduce tempdb usage.



STATUS
Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem was corrected in the latest Microsoft SQL Server 6.5 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

  S E R V P A C K

Additional query words: hang hung freeze frozen stopped

Keywords: kbbug kbfix kbenv kbusage KB172557

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.