From: Elgin on
Just purchased and deployed WSS 2003 R2 on a Dell PowerEdge 2900. I moved the
data from the old server to this one. None of the workstations or other
configuration has changed, but the WSS is getting the ID 2000 error when I
run a VB script in Excel on a workstation. This script has been running daily
for a few years accessing data on the old server with no ID 2000 errors. When
it began running against the data on the WSS, that's when I get the errors.

Specifically, I believe it may be related to a file renaming action ("Name"
statement in VBA). This statement actually is used to move a file to a
different folder on the same share.

Incidentally, this error coincides with an occasional MS Access connectivity
error.


"Mitch W" wrote:

> Our Univeersity recently had a number of machines infected with the
> Win32.Lokkest virus and other variants. While no machines that were infected
> attach to our servers directly they spewed out traffic to everyone. We still
> have machine left to be cleaned on campus, but since that infection started
> our Windows 2003 servers systems (which are fully patched) have recorded the
> following event in the log:
>
> Event Type: Error
> Event Source: Srv
> Event Category: None
> Event ID: 2000
> Date: 1/10/2007
> Time: 9:55:26 PM
> User: N/A
> Computer: WWW1
> Description:
> 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.
> Data:
> 0000: 00040000 00540001 00000000 c00007d0
> 0010: 00000000 80090302 00000000 00000000
> 0020: 00000000 00000000 15e6032c
>
> What is going on and how do we stop it, so far we can't see any adverse
> effects on the server, but we are concerned.
>
> thanks,
> mitch
>