Re: Blue screen of death when closing connections
- From: Lefty Bigfoot <nunya@xxxxxxxxxxxxx>
- Date: Sun, 02 Oct 2005 22:35:10 GMT
Vera Noest [MVP] wrote
(in article
<Xns96E2D8AE6FB57veranoesthemutforsse@xxxxxxxxxxxxx>):
> I can't help you anymore with the STOP 0xab problem, except that I
> would phone Microsoft Support. You can get the 901150 hotfix from
> them, if you want to.
Understood, thanks.
> Do you have a testserver on which you can replicate the problem and
> test if the hotfix solves your problem?
No, it's a small non-profit with minimal budget for "extras".
Terminal Services was actually an extravagance in that light,
since they didn't realize when they bought it that MS had
non-profit discounts (heavy discounts) that they missed out on,
and blew a lot of what they did have available. I started
helping them out about a year ago as a volunteer, and it had
been bulletproof pretty much up until SP1 came out, and it's
been a nightware ever since. First, SP1 blew the virus software
out of the water, and that company was very late getting a patch
out the door, and also these bsod's started popping up.
> Regarding the "stale" sessions:
> I assume that they have a status of "disconnected"?
Correct.
> Have you checked in Task Manager to see which processes are running
> in these sessions?
Yes. Usually nothing besides outlook or one of the office
components, if anything.
> Is there anything in the EventLog?
I haven't been able to locate anything in the event logs that
seems to be directly related to the connection failures, or why
that the automatic disconnect settings in the user profiles get
ignored.
> Do the sessions get disconnected while the user is actively using
> the connection, or when the user tries to logoff from the session?
It seems to happen while they are idle. I.e., they go to lunch,
come back, and their session isn't logged out, it's
disconnected. When they try to connect back in, it will not
allow them to connect. Forceibly disconnecting their stale
session at this point is when the blue screen rears its head.
> Any warnings about printers or profiles which cannot be unloaded /
> deleted?
I have seen a message sporadically in the log about a particular
printer not being able to be set as the default printer. This
is a strange one, since nobody complains about that printer not
working, and it is used daily, so the error is a mystery. The
timestamps on these entries don't align with the above issue
though.
> Are you running a 24*7 hours business?
No, strictly 8-5, but at a couple different locations
(geographically close, but not in the same building).
> If not, have you considered
> a nightly reboot of the server to get rid of the disconnected
> sessions? Just as a workaround, until a real solution becomes
> available.
It could be done, but if it doesn't come back up cleanly, that
means I have to be standing at the door when they come in to
open the next morning (I don't work onsite, I mostly help out
remotely when they have issues). Currently, the only thing
going on at night is scheduled backups to external media.
--
_ __ _
| | ___ / _| |_ _ _
| | / _ \ |_| __| | | |
| |__| __/ _| |_| |_| |
|_____\___|_| \__|\__, |
|___/
All of God's creatures have a place..........
..........right next to the potatoes and gravy.
.
- References:
- Re: Blue screen of death when closing connections
- From: Lefty Bigfoot
- Re: Blue screen of death when closing connections
- From: Lefty Bigfoot
- Re: Blue screen of death when closing connections
- Prev by Date: Re: SP1 based terminal stops responding to RDP connections
- Next by Date: "screen saver timeout?"
- Previous by thread: Re: Blue screen of death when closing connections
- Next by thread: Re: Blue screen of death when closing connections
- Index(es):
Relevant Pages
|
