Actually I was trying to let you know that it is the actual physical console session on your Server that is running the screen saver causing the problem, not something you are logging into. I had to set my console screen saver to none, to free up th...
We had this issue and it turned out that the console was running the winlogon screen saver or another screen saver that was utilizing performance monitor, and performance monitor was locking files that belonged to Symantec processes.