10-17-2005 06:33 AM - edited 03-13-2019 10:53 AM
Has anyone else come across this problem?
It is possible that winlogon.exe was the process that was caused the high utilisation. we have checked this file with our AV and it shows clean.
Any ideas or suggestions greatly appreciated
10-17-2005 06:42 AM
Do you have the recommended memory of atleast a gig or more on the server ?
Does any service (Under Services <- Control Panel) crash, also check Event viewer to find the root casue.
10-17-2005 07:36 AM
Hi,
Are there any entries in the DrWatson log file on the Publisher? Could you post it?
Cheers
Andy
10-17-2005 08:58 AM
We have 4Gb of memory.
We couldnt access the server to find out if any service had crashed. There was no blue screen or any microsoft message on the console screen and the Event viewer was showing no important errors.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: