Article ID: 245077 - View products that this article applies to.
This article was previously published under Q245077
This article has been archived. It is offered "as is" and will no longer be updated.
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.
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.
To resolve this problem, defragment the disk or allocate additional disk space.
Article ID: 245077 - Last Review: February 28, 2014 - Revision: 2.2