We have been having problems with our file cluster. Users periodically lose
their ability to access files on their user directories on the file server.
When this happens, if you attempt to log on to the server you get a message
that states:
"Windows cannot load the user's profile but has logged you on with the
default profile for the system.
DETAIL - Insufficient system resources exist to complete the requested
service."
Once the desktop appears, attempting to open up Computer Management or any
other MMC based app gives the error:
"Failed to create emtpy document"
Viewing the event logs from a remote computer, the following error messages
also appear:
App log:
"Windows was unable to load the registry. This is often caused by
insufficient memory or insufficient security rights.
DETAIL - Insufficient system resources exist to complete the requested
service. for C:\Documents and Settings\username\ntuser.dat"
App log (after trying to execute a perfmon on the server):
"The service was unable to open the log file C:\PerfLogs\file.blg for log
file and will be stopped. Check the log folder for existence, spelling,
permissions, and ensure that no other logs or applications are writing to
this log file. You can reenter the log file name using the configuration
program. This log will not be started. The error returned is: Not enough
storage is available to process this command."
System log (this error appear numerous times):
"While transmitting or receiving data, the server encountered a network
error. Occassional errors are expected, but large amounts of these indicate a
possible error in your network configuration. The error status code is
contained within the returned data (formatted as Words) and may point you
towards the problem.
Data in words:
0000: 00040000 00540001 00000000 800007dc
0010: 00000000 c000023d 00000000 00000000
0020: 00000000 00000000 0000097a "
On the surface, from looking at the logs this would appear to be a disk
space issue, however there is over 30 gb available on the system partition,
and plenty of space available on all other drives as well. The node has 4 gb
or RAM, 2.5 of which is currently available, and the page-file is hardly
being used. I can't figure out the root of the problem.
Other items of note: If I reboot that node of the cluster or move the
resources to the other node, the problems go away for a period of time (a
week or two) and then begin to surface again.
Bookmarks