Symptoms
You may experience one or more of the following symptoms when you access files in a network drive.
| • | A Windows server that is configured as a file and print server stops responding and file and print server functionality temporarily stops. |
| • | You experience slow performance when you open, save, close, delete, or print files that are located on a shared resource. |
| • | Delays occur when you use a program over the network. It may slow down for approximately 20 to 30 seconds. |
| • | You experience a delay when you perform file copy or backup operations. |
| • | Windows Explorer stops responding when you connect to a shared resource or you see a red X on the connected network drive in Windows Explorer. |
| • | When you log on to the file server, after you type your name and password in the Log On to Windows dialog box, a blank screen appears. The desktop does not appear. |
| • | A program that uses remote procedure call (RPC) or uses named pipes to connect to a file server stops responding. |
| • | The server temporarily stops responding and one or more event ID messages similar to the following messages appear in the System log on the file server: Event ID: 2022 Source: Srv Type: Error Description: Server was unable to find a free connection <number> times in the last <number> seconds. Event ID: 2021 Source: Srv Type: Error Description: Server was unable to create a work item <number> times in the last <number> seconds. Event ID: 2020 Source: Srv Type: Error Description: The server was unable to allocate from the system paged pool because the pool was empty. Event ID: 2019 Source: Srv Type: Error Description: The server was unable to allocate from the system nonpaged pool because the pool was empty. Event ID: 2510 Source: Server Event Type: Error Description: The server service was unable to map error code 1722. 1722 = RPC_S_SERVER_UNAVAILABLE = RPC Service is unavailable. Additionally, the following event appears in the System log on the client computer: Event ID: 3013 Event Type: Error Event Source: MrxSmb / Rdr Description: The redirector has timed out a request to Computer Name. |
| | |
| • | You receive an error message similar to one of the following messages when you try to connect to a shared resource:Error message 1 System error 53. The network path was not found. Error message 2 System error 64. The specified network name is no longer available. |
| • | You are intermittently disconnected from network resources, and you cannot reconnect to the network resources on the file server. However, you can ping the server, and you can use a Terminal Services session to connect to the server. |
| • | If multiple users try to access Microsoft Office documents on the server, the File is locked for editing dialog box does not always appear when the second user opens the file. |
| • | A network trace indicates a 30 to 40 second delay between an SMB Service client command and a response from the file server. |
| • | When you try to open an Access 2.0 database file (.mdb file) in Microsoft Access 97, in Microsoft Access 2000, or in Microsoft Access 2002, you may receive an error message that is similar to the following: Disk or network error. |
| • | When you try to open a Microsoft Word file, you may receive the following error message: Word failed reading from this file file_name. Please restore the network connection or replace the floppy disk and retry. |
Additionally, the following event may be logged in the System log on the client computer:
Type: Warning
Source: MrxSmb
Event ID: 50
Description: {Lost Delayed-Write-Data} The system was attempting to transfer file data from buffers to \Device\LanmanRedirector. The write operation failed, and only some of the data may have been written to the file.
Causes:
- The server has a backup software running.
- A ant-virus software is scanning on the server.
- A backup software agent or Open Transaction Manager is installed on your computer.
- The server has RAID 5/10 and one of Hard Disks is failed.
- The server has a hardware issue.