Hello,
Recently some of our clients at our compnay have recently experienced Blank
Blue Screens when Alt Tabbing or closing an active terminal service window.
We have about 50 clients that use a Terminal Service based program. They all
run in "Full Screen" Mode, so they often Alt Tab to change between prorams.
Randomly though, a few clients a day (around 3-5) will experience a blank
blue screen when alt tabbing between the windows or even when trying to
closet he active session. It appears their session is locking up as you can
still navitage around the other programs or use the rest of the PC without
issue. But the terminal service window itself freezes.

We have contacted the tech support for the program itself but they are
stumped fully. I don't know if this is a Terminal Service bug. I'm actually
not too familiar with it.
We run Windows 2000 Terminal Services on a Server Running Windows 2000
Advanced Server.

Has anyone experienced a situation like this? Where they can't back out of a
terminal service window, or had random clients that couldn't backout, without
the window freezing up?

I used to get it all the time, it was the virus scanner, we finally had to
just remove it. With virus scanning on the mail server, and no internet
access on the TS, it hasn't been a problem.

Interesting...
We Run Symantec Antivirus Corp Edition 9.0, were you perhaps running the
same anti virus? I'll have to take that into a possibility as maybe a cause.
I didn't think of that before.

"Marvin P. Winterbottom" wrote:

> I used to get it all the time, it was the virus scanner, we finally had to
> just remove it. With virus scanning on the mail server, and no internet
> access on the TS, it hasn't been a problem.

We had McAfee. Also tried AVG freebee, but it tended to crash the server
when updating itself.

Hi All,

We run Symantec Antivirus Client edition 9.0 and don't seem to have any
issues.

Also, our users frequently would Alt Tab to change between different
applications.

Hope you find a fix.

Regards,
Sung

"Marvin P. Winterbottom" wrote:

> We had McAfee. Also tried AVG freebee, but it tended to crash the server
> when updating itself.

Of course, people run antivirus on TS all the time, with no problem, but in
some cases, on some clients, it causes this blue screen hang, I just wish
someone could figure out why, it seems to only happen with win2k server, but
now the world has moved on, so we will never know.

"Sung Duc" wrote:

> Hi All,
>
> We run Symantec Antivirus Client edition 9.0 and don't seem to have any
> issues.
>
> Also, our users frequently would Alt Tab to change between different
> applications.
>
> Hope you find a fix.
>
> Regards,
> Sung
>
> "Marvin P. Winterbottom" wrote:
>
> > We had McAfee. Also tried AVG freebee, but it tended to crash the server
> > when updating itself.

[shltech]

I had the same problem. I looked high and low for a solution, it took a while but here are my results.: Registry keys under CLSID that those sepcific users did not have access rights. In my case, it was an ACCPAC upgrade I did (tax table) which messed up the users which were not part of the ACCPAC group (because they did not use accpac) although ACCPAC was on that server. I had to add them to the ACCPAC group until I figure out exactly which keys need be remove from the 3 users registry that are not required.

I hope this helps.

J

I have the same problem (blue screen happens only sometimes), I'm running win
2003 server and I was running Symantec antivirus on it... I'll have to try to
remove it and see if it fixes it.

"shltech" wrote:

>
> I had the same problem. I looked high and low for a solution, it took a
> while but here are my results.: Registry keys under CLSID that those
> sepcific users did not have access rights. In my case, it was an
> ACCPAC upgrade I did (tax table) which messed up the users which were
> not part of the ACCPAC group (because they did not use accpac) although
> ACCPAC was on that server. I had to add them to the ACCPAC group until
> I figure out exactly which keys need be remove from the 3 users
> registry that are not required.
>
> I hope this helps.
>
> J
>
>
> --
> shltechPosted from http://www.pcreview.co.uk/ newsgroup access
>
>