Microsoft KB Archive/245077

= Computer Stops Responding with Event ID 2022 =

Article ID: 245077

Article Last Modified on 2/21/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT 4.0 Service Pack 1
 * Microsoft Windows NT 4.0 Service Pack 2
 * Microsoft Windows NT 4.0 Service Pack 3
 * Microsoft Windows NT 4.0 Service Pack 4
 * Microsoft Windows NT 4.0 Service Pack 5
 * Microsoft Windows NT 4.0 Service Pack 6

-



This article was previously published under Q245077



SYMPTOMS
Your Windows-based server may become unresponsive. The server may recover on its own or you may have to restart it. The server's clients are disconnected or stop responding (hang), and Event ID 2022 is logged in the system event log.



CAUSE
This problem occurs because a request was made to grow a file and the disk is fragmented or is nearly full. This causes the free space search to take an extremely long time. This request holds system-level locks that are needed for other requests to complete. The Server service resource task is pended as well, which causes Event ID 2022.

To test this, you can use any application that can generate a disk file. Because file creation times are hardware-dependent and software-dependent, you typically look to compare expected behavor against the disk resource in question by trying to create a 1 gigabyte file on a known clean or empty partition of a disk on similar hardware.

For example, on the system partiton, the file creation may take less than a second whereas the file creation may take five seconds on the data partition. The difference in time indicates that you are experiencing this problem. Of course, you must run this test while users are not accessing this data partition.

This problem also occurs when you try grow an End Of File (EOF) to a large amount. This has been seen with .pst files.



RESOLUTION
To resolve this problem, defragment the disk or allocate additional disk space.

Keywords: kbnetwork kbprb KB245077

-

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

© Microsoft Corporation. All rights reserved.