I have a server running Windows 2003 Server R2 Enterprise (32-bit) with a fully-patched SP2, acting exclusively as a large file server, connected to a decent-sized Lefthand SAN. The Windows components installed include DFS, File Server Management, Storage Manager for SAN. Installed applications include Dell OpenManage, LeftHand Centralized Management Console and SAN/iQ DSM for MPIO, .NET 2.0 and 3.0 + SP1, and Sophos Anti-Virus. The hardware is a Dell PowerEdge 1850 (Dual dual-core CPU x 3GHz, 4GB RAM) with dual Intel PRO/1000 MT NICs. This server is acting as a central file server and hosting 10 DFS roots that get significant use, and that is it's only role.
The server periodically starts generating error events in the system event log. When it begins generating errors, it generates dozens to hundreds per second and filled the event log in well under a minute. The only event generated is:
Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2000
The server's call to a system service failed unexpectedly.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
0000: 00040000 00540001 00000000 c00007d0
0010: 00000000 c000010a 00000000 00000000
0020: 00000000 00000000 00bd0334
Once this error begins generating, server performance is degraded noticeably, but network services remain available.
I have already dug through at least a dozen links I found through Google, to no avail. I have already looked through EventID, the error code is not listed and potential suggestions listed did not help. The possible causes I have found elsewhere include removing Windows patches, which don't exist individually with SP2 installed. I have already checked the possible solution relating to both shared printers and DNS, and neither are the case, nor is Cheyenne Open File anything. Rebooting fixes the problem for a little while, but this server is a center-point for files on a global scale so reboots don't go over very well. The only thing I can think of that has not been done is re-installing SP2, which is not allowed until this weekend at the earliest due to the down time required (5-10 minutes downtime for a reboot requires blood). I will happily provide any and all additional information if it leads to a permanent fix to this issue.
Thanks in advance.