- A Windows-based file server that is configured as a file and print server stops responding. Then, the file and print server functionality temporarily stops.
- You experience a long delay when you open, save, close, delete, or print files that are located on a shared resource.
- You experience a temporary decrease in performance when you use a program over the network. Typically, performance is slow for approximately 40 to 45 seconds. However, some delays may last up to 5 minutes.
- You experience a delay when you copy a file copy or when you perform backup operations.
- When you connect to a shared resource, Windows Explorer either stops responding or you see a red X on the connected network drive.
- A program stops responding that either uses remote procedure call (RPC) or that uses named pipes to connect to a file server.
- The server temporarily stops responding and one or more event ID messages that resemble 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.Additionally, the following event may appear 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 <ComputerName>.
- You receive one of the following error messages when you try to connect to a shared resource: System error 53. The network path was not found. (ERROR_BAD_NETPATH)System error 64. The specified network name is no longer available. (ERROR_NETNAME_DELETED)
- 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 that there is a 30 to 40 second delay between a server message block (SMB) Service client command and a response from the file server.
- In Windows Server 2003 and Windows 2000 Service Pack 4 (SP4), the server may stop responding arbitrarily.
- When you try to open a Microsoft Access 2.0 database file (.mdb) in Microsoft Access 97, Access 2000, or Access 2002, you may receive an error message that resembles the following:Disk or network error.
- When you open Microsoft Excel, you may receive the following error message: file has not been saved.
- When you open Windows Explorer, you may receive the following error message: Cannot access <path and file name> .The session was canceled.
- When you open a Microsoft Word file, Word may fail. Then, 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, after you restore the network connection and you click OK, you receive the following error message:Word has lost data because of a bad network connection or missing floppy. Documents relying on this data will be saved and then closed.
- The version of Symantec Event Handler driver (Symevent.sys) is outdated. Therefore, two or more threads are deadlocked in the Symevent.sys driver in the Symevent_GetSubTask function.
- There is a Computer Associates (CA) INO_FLTR.SYS OpLock interoperability problem with the Srv.sys file.
Note The SymEvent.sys file version 126.96.36.199 has a bug that can make some servers restart arbitrarily. For information about your hardware manufacturer, visit the following Web site:
The following antivirus driver versions can also cause servers to stop responding:
- The problem is known to occur when the following driver versions are installed on the file server. These versions that are installed with Symantec Antivirus 9.0.
Name Company Version Date Description Symevent.sys Symantec Corporation 11.4:0.6 05-Mar-2004 Symantec Event Library Symtdi.sys Symantec Corporation 5.3:6.13 23-Dec-2004 Network Dispatch Driver
The following Web page on the Symantec Web site (Symantec Document ID: 2005062909055948 ) describes how to update the Symevent files:
- The problem is known to occur when the following CA eTrust Antivirus/InoculateIT File System Filter Driver versions are installed on the file server. The following Web page on the Computer Associates Web site references the problem:
Name Company Version Date Description Ino_flpy.sys Computer Associates 5.0:6100.106 19-Jun-2003 CA eTrust Antivirus/InoculateIT File System Mounting Filter Driver for Windows 2000/XP/.Net Ino_fltr.sys Computer Associates 5.0:6100.136 08-Aug-2004 CA eTrust Antivirus/InoculateIT File System Filter Driver for Windows 2000/XP/2003
15:28:14 client -> server SMB Read AndX Request, FID 0x0002
15:28:14 server -> client TCP [ACK]
15:29:05 client -> server TCP [FIN ACK]
15:29:05 server -> client TCP [FIN ACK]
Article ID: 923360 - Last Review: Jul 22, 2009 - Revision: 1