After installing servicepack 4 on ts - reboots ts when I log user's off

[Henrik Demant]

Hi,

On a NT4 domain I have two W2K terminalservers that I every
week force the users off (log off via ts service manager) the terminal
server. After installing servicepack 4 the ts reboots in the same
moment I press log off to more than one user- this is a problem.
Before I had servicepack 2 installed without any troubles. The last
hotfix that are recommend by Microsoft is allso installed (that's why
servicepack 4 were installed).

They only do it when I use TS manger to log off users, and they do it
only on the TS server I log off the users. They havn't done it (reboot)
spontaneously. In event viewer there is the message that "the current shut
down was unexpected" and nothing else.

Do anybody know a soulotion for this problem?

Kind regards
Henrik

 

[Vera Noest [MVP]]

Can you configure the TS to *not* reboot on a critical error?
That might halt the system on a blue STOP error screen, which
gives you a little bit more information (the STOP error code +
parameters).

 

[Henrik Demant]

Hi Vera,

I have not been in front of the servers to see what happens, because I'm
controlling the TS servers (ts remotely) with administrator login on the
server. But
I loose connection to server (ping the IP address) immediately in the
moment I press log off - so - yes, They proberly show a blue screen and
the reboot automatically - but I will be in front of the servers next time I
have to log off the users and try to see what's going on.

I will put new information when it is posible.

Regards
Henrik

 

[Henrik Demant]

Hi

This is the information that is in the event viewer :

The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xa00b8eda, 0x00000000, 0x00000000).
Microsoft Windows 2000 [v15.2195]. A dump was saved
in: C:\WINNT\Minidump\Mini100903-01.dmp.

It is proberly not enough information - but here it is.

Regards
Henrik

 

[Vera Noest [MVP]]

STOP error 0x1E is a KMODE_EXCEPTION_NOT_HANDLED error.
That's unfortunately a very common STOP error.

There was no driver indicated on the BSOD information on the
screen, I presume? (the information on the screen contains
sometimes the name of the driver causing the crash, but this is
not echoed to the EventLog).

Have a look at the troubleshooting tips for this STOP error at the
MSDN Bug Check error code page at
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/ddtools/hh/ddtools/bccodes_763r.asp?frame=true

In "normal" cases, I would suggest following the tips there,
especially to run all hardware diagnostics software and have a
*very* hard look at your printer drivers, since 3th party drivers
are the main cause for this STOP error.

But since this started directly after installing SP4 and you can
produce the problem at will (and unrelated to printing), I would
think about making a call to Microsoft Support.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

Hi

This is the information that is in the event viewer :

The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xa00b8eda, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved
in: C:\WINNT\Minidump\Mini100903-01.dmp.

It is proberly not enough information - but here it is.

Regards
Henrik

Hi Vera,

I have not been in front of the servers to see what happens,
because I'm controlling the TS servers (ts remotely) with
administrator login on the server. But
I loose connection to server (ping the IP address) immediately
in the moment I press log off - so - yes, They proberly show a
blue screen and the reboot automatically - but I will be in
front of the servers next time I
have to log off the users and try to see what's going on.

I will put new information when it is posible.

Regards
Henrik


"Vera Noest [MVP]" <[email protected]> skrev
i en meddelelse

 

[Henrik Demant]

Hi Vera,

Unfortally It's only possible for me to try "dangerous"
things in weekend - So I have to wait to see what's
on the screen. But maybe the dumpfile shows the same?.

In the dumpfile I can see different kinds og drivers, but
the last one is an printer driver - can it be helpfull to
show you this file?
Henrik

-----Original Message-----
STOP error 0x1E is a KMODE_EXCEPTION_NOT_HANDLED error.
That's unfortunately a very common STOP error.

There was no driver indicated on the BSOD information on the
screen, I presume? (the information on the screen contains
sometimes the name of the driver causing the crash, but this is
not echoed to the EventLog).

Have a look at the troubleshooting tips for this STOP error at the
MSDN Bug Check error code page at
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/ddtools/hh/ddtools/bccodes_763r.asp? frame=true

In "normal" cases, I would suggest following the tips there,
especially to run all hardware diagnostics software and have a
*very* hard look at your printer drivers, since 3th party drivers
are the main cause for this STOP error.

But since this started directly after installing SP4 and you can
produce the problem at will (and unrelated to printing), I would
think about making a call to Microsoft Support.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

Hi

This is the information that is in the event viewer :

The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xa00b8eda, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved
in: C:\WINNT\Minidump\Mini100903-01.dmp.

It is proberly not enough information - but here it is.

Regards
Henrik

Hi Vera,

I have not been in front of the servers to see what happens,
because I'm controlling the TS servers (ts remotely) with
administrator login on the server. But
I loose connection to server (ping the IP address) immediately
in the moment I press log off - so - yes, They proberly show a
blue screen and the reboot automatically - but I will be in
front of the servers next time I
have to log off the users and try to see what's going on.

I will put new information when it is posible.

Regards
Henrik


"Vera Noest [MVP]" <vera.noest@remove- this.hem.utfors.se> skrev
i en meddelelse

.

 

[Vera Noest [MVP]]

Not really, but this sounds promising. Just uninstall any 3th
party printer drivers and map the printers to a native driver if
necessary, by editing ntprintsubs.inf. Check:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

Hi Vera,

Unfortally It's only possible for me to try "dangerous"
things in weekend - So I have to wait to see what's
on the screen. But maybe the dumpfile shows the same?.

In the dumpfile I can see different kinds og drivers, but
the last one is an printer driver - can it be helpfull to
show you this file?
Henrik

-----Original Message-----
STOP error 0x1E is a KMODE_EXCEPTION_NOT_HANDLED error.
That's unfortunately a very common STOP error.

There was no driver indicated on the BSOD information on the
screen, I presume? (the information on the screen contains
sometimes the name of the driver causing the crash, but this is
not echoed to the EventLog).

Have a look at the troubleshooting tips for this STOP error at the
MSDN Bug Check error code page at
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/ddtools/hh/ddtools/bccodes_763r.asp? frame=true

In "normal" cases, I would suggest following the tips there,
especially to run all hardware diagnostics software and have a
*very* hard look at your printer drivers, since 3th party drivers
are the main cause for this STOP error.

But since this started directly after installing SP4 and you can
produce the problem at will (and unrelated to printing), I would
think about making a call to Microsoft Support.

Vera Noest

Hi

This is the information that is in the event viewer :

The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xa00b8eda, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved
in: C:\WINNT\Minidump\Mini100903-01.dmp.

It is proberly not enough information - but here it is.

Regards
Henrik

"Henrik Demant" <[email protected]> skrev i en meddelelse
Hi Vera,

I have not been in front of the servers to see what happens,
because I'm controlling the TS servers (ts remotely) with
administrator login on the server. But
I loose connection to server (ping the IP address) immediately
in the moment I press log off - so - yes, They proberly show a
blue screen and the reboot automatically - but I will be in
front of the servers next time
I
have to log off the users and try to see what's going on.

I will put new information when it is posible.

Regards
Henrik


"Vera Noest [MVP]" <vera.noest@remove- this.hem.utfors.se> skrev
i en meddelelse

Can you configure the TS to *not* reboot on a critical error?
That might halt the system on a blue STOP error screen, which
gives you a little bit more information (the STOP error code
+ parameters).



Hi,

On a NT4 domain I have two W2K terminalservers that I every
week force the users off (log off via ts service manager)
the terminal server. After installing servicepack 4 the ts
reboots in the same moment I press log off to more than one
user- this is a problem. Before I had servicepack 2
installed without any troubles. The last hotfix that are
recommend by Microsoft is allso installed (that's why
servicepack 4 were installed).

They only do it when I use TS manger to log off users, and
they do it only on the TS server I log off the users. They
havn't done it (reboot) spontaneously. In event viewer
there is the message that "the current shut down was
unexpected" and nothing else.

Do anybody know a soulotion for this problem?

Kind regards
Henrik

 

[Henrik Demant]

Hi Vera,

Thanks for your help - I will try to
follow your advice.

Regards from Henrik.

-----Original Message-----
Not really, but this sounds promising. Just uninstall any 3th
party printer drivers and map the printers to a native driver if
necessary, by editing ntprintsubs.inf. Check:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

[email protected]:

Hi Vera,

Unfortally It's only possible for me to try "dangerous"
things in weekend - So I have to wait to see what's
on the screen. But maybe the dumpfile shows the same?.

In the dumpfile I can see different kinds og drivers, but
the last one is an printer driver - can it be helpfull to
show you this file?
Henrik

-----Original Message-----
STOP error 0x1E is a KMODE_EXCEPTION_NOT_HANDLED error.
That's unfortunately a very common STOP error.

There was no driver indicated on the BSOD information

on
the

screen, I presume? (the information on the screen contains
sometimes the name of the driver causing the crash,

but
this is

not echoed to the EventLog).

Have a look at the troubleshooting tips for this STOP error at the
MSDN Bug Check error code page at
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/ddtools/hh/ddtools/bccodes_763r.asp? frame=true

In "normal" cases, I would suggest following the tips there,
especially to run all hardware diagnostics software

and
have a

*very* hard look at your printer drivers, since 3th party drivers
are the main cause for this STOP error.

But since this started directly after installing SP4

and
you can

produce the problem at will (and unrelated to

printing),
I would

think about making a call to Microsoft Support.

Vera Noest


Hi

This is the information that is in the event viewer :

The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000001e (0xc0000005, 0xa00b8eda, 0x00000000,
0x00000000). Microsoft Windows 2000 [v15.2195]. A

dump
was saved

in: C:\WINNT\Minidump\Mini100903-01.dmp.

It is proberly not enough information - but here it is.

Regards
Henrik

"Henrik Demant" <[email protected]> skrev i en meddelelse
Hi Vera,

I have not been in front of the servers to see what happens,
because I'm controlling the TS servers (ts

remotely)
with

administrator login on the server. But
I loose connection to server (ping the IP address) immediately
in the moment I press log off - so - yes, They proberly show a
blue screen and the reboot automatically - but I

will
be in

front of the servers next time
I
have to log off the users and try to see what's

going
on.

I will put new information when it is posible.

Regards
Henrik


"Vera Noest [MVP]" <vera.noest@remove- this.hem.utfors.se> skrev
i en meddelelse

Can you configure the TS to *not* reboot on a critical error?
That might halt the system on a blue STOP error screen, which
gives you a little bit more information (the STOP error code
+ parameters).



Hi,

On a NT4 domain I have two W2K terminalservers that I every
week force the users off (log off via ts

service
manager)

the terminal server. After installing

servicepack
4 the ts

reboots in the same moment I press log off to more than one
user- this is a problem. Before I had

servicepack
2

installed without any troubles. The last hotfix that are
recommend by Microsoft is allso installed

(that's
why

servicepack 4 were installed).

They only do it when I use TS manger to log off users, and
they do it only on the TS server I log off the users. They
havn't done it (reboot) spontaneously. In event viewer
there is the message that "the current shut

down
was

unexpected" and nothing else.

Do anybody know a soulotion for this problem?

Kind regards
Henrik

.