Console Logon Issues with WSS 2003 R2

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I have an HP Ai0600 server (ML370 really) running WSS 2003 R2, up to
date. I've had a problem since I got this box that occurs somewhat
randomly that HP hasn't been able to fix.

I manage the box remotely via RDP console session (as I do for all of
my sessions). After a while I will be unable to logon remotely -- the
RDP client connects and drops. Sometimes I'm able to fix this by
logging on at the physical console and logging off the session there.
Sometimes I can connect via VNC as well to do this. Sometimes however
(like today) when I attempt to logon at the physical console I see
this error:

Logon Connect Failed - "Error connecting to existing session for user
Administrator (ID 0). The operation completed successfully".

I try resetting the console session via Terminal Services Manager on
another server, so there are no user sessions, but nothing works.
Restarting WinVNC gives me a grey desktop screen but no WinLogon
prompt.

Last night I saw this:

EVENT # 32404513
EVENT LOG System
EVENT TYPE Error
SOURCE VolSnap
EVENT ID 39
COMPUTERNAME FOOBAR
TIME 7/18/2007 12:57:28 AM
MESSAGE When preparing a new volume shadow copy for volume C:, the
shadow copy storage on volume E: could not be located in non-critical
space. Consider using a shadow copy storage volume that does not have
any shadow copies.

Rebooting the server fixes the problem of course. Sometimes it fixes
itself after a day or so.

Yesterday I made a change to backups to include Shadow Copy Components
in BackupExec, and I was going to logon today to move the shadow copy
storage for C: to F:, but I can't since I can't logon at all.

I've seen some posts suggesting a relationship between VSS and console
logon issues, but no real answers. HP made some noises about Symantec
Antivirus client being a potential culprit.

What's going on here and how can I fix this?

.

Relevant Pages

  • Re: TS / RDP / Citrix Events
    ... and remote connections to the console session (EventID 628 in stead ... Logon at physical console: ... Logon with normal TS session: ...
    (microsoft.public.windows.terminal_services)
  • Re: TS / RDP / Citrix Events
    ... and remote connections to the console session (EventID 628 in stead ... Logon at physical console: ... Logon with normal TS session: ...
    (microsoft.public.windows.terminal_services)
  • Re: RDP into Small Business Server 2003
    ... There is software that knows when it's in a TS session, and won't function or is blocked from functioning. ... One common example is the Trend Micro command-line installation of the security client. ... RDP is a terminal services session, so it's not exactly 'at the console'. ... On a server I admin I need to logon and then lock the server (a LOB ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Shadowing for Non-Adminsitrators
    ... attempting to shadow a console session must be a member of the ... > Does anyone know a way to grant console shadowing through Remote ... > I have setup TCP-RDP permissions to allow members of a domain group ...
    (microsoft.public.windows.terminal_services)
  • Re: Console Logon Issues with WSS 2003 R2
    ... On the server that I managed, I'm also having the same issue when I log on to the console. ... I might not be able to offer you a solution, but you should be able to log on non-console and reset your console session using Terminal Services Manager. ... MESSAGE When preparing a new volume shadow copy for volume C:, ...
    (microsoft.public.windows.server.general)