With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Comments:EventID.Net
This applies to all servers from NT4, NT4 Enterprise, W2K, W2K AS and W2K Dataceneter. As per ME304101:
"The two causes of this condition are related. The most common cause is listed first:
More files are open than the memory cache manager can handle. As a result, the cache manager has used up the available paged pool memory.
The backup program has tried to back up a file whose size is larger than the backup API can access on that version of the operating system. This has the same result (that is, the paged pool is used up).
Note that the resolution for each issue differs depending on whether you see the condition on Windows 2000 or Windows NT 4.0".
x
1