Link to home
Start Free TrialLog in
Avatar of mkaishar
mkaishar

asked on

Windows 2003 Terminal Server frequent unexpected shutdown and reboot (on a daily basis)

I have 3 Windows 2003 Terminal Servers that seem to always shutdown and reboot almost on a daily basis and the problem mostly seems to occur when people are logging off their session and the system is releasing the printer sessions.

Event Viewer Log Info:
"Printer Okidata ML 320-IBM (from ANNIELAO) in session 1 was deleted."
"Printer hp1320@wh on photo (from KENNY) in session 3 was purged."
"Printer OKI320@SALES on salesprintserve (from KENNY) in session 3 was deleted."


All these warnings and then:
The previous system shutdown at 5:55:10 PM on 2/21/2007 was unexpected.

Thanks,
Mark
Avatar of and235100
and235100
Flag of United Kingdom of Great Britain and Northern Ireland image

Do you have the latest updates and hotfixes?
SOLUTION
Avatar of and235100
and235100
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of mkaishar
mkaishar

ASKER

Yes systems are patched and up to date.

From what I can see regarding latest printer drivers, yes they are current, because I go into Server Properties under the Printer section and I see only Windows 2000, 2003 drivers, nothing old or showing NT in there.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Good idea, will check and report back...sometimes I overlook the simple solution.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Well after a few days of testing I am still not close to a solutions...but...unluckynelson I tried your option of disabling logoff timeouts for user sessions.

Once I did that the servers seemed to stay online, but once I logged in as admin and logged off the disconnected user sessions, the server crashed.

So option 2 is to contact Microsoft this week and get a kernel patch...this is just too bizarre.

BTW, I checked the version of the printer drivers and they are all current...I even installed 2 new terminal servers, set them up as a test environment in vmware and they still crashed after some usage.

I don't understand why Microsoft doesn't post the info about this...I presume it is a bug with after the installation of SP1.

I will post more info after contacting Microsoft.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
unluckynelson: Did you contact Microsoft and get the kernel patch? Has it been working for you?  

When you disable logoff timeouts on user sessions and restrict users to a single session has that worked for you?

Which route did you go?



SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
One other issue I forgot to ask...are you using roaming profiles? I am with this one client who's having problems.

But I have two other clients with a single w2k3 terminal server with no roaming profiles and they are not having any kind of issues.

Wonder if it is the roaming profiles that are causing part of the problems?

SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I have some concern about installing a kernel patch from Microsoft that has not been regression tested. I don't want to patch something to resolve one issue and then break something else.

So for now I am going to monitor things for then next 3-4 days with the config you provided me.

On another side note...my brain is thinking about something else now...

My plan is to have half the users on TS1 as primary and TS2 as backup and vice-versa for the other half the users on TS2 as primary and TS1 as backup, and eliminate roaming profiles, some of these users have over 4GB profile and they complain about poor TS performance.

They're running GigE with data stored on iSCSI and it works well performance wise if a user is not in roaming profile.  But stick 60+ users on a network with other services running, it does seem to slow things down.

Anyhow...I'll post updates on the primary problem after a few days of monitoring.

Thanks,
Mark
unluckynelson:

How do you deal with people that disconnected from the terminal server, but did not log off? If I go into the Terminal Services Manager I see half a dozen people disconnected, if I try to log off their session the server crashes.

I can see that the sessions are active (Outlook, Winword, etc...) I presume when they login the next day to one of the other terminal servers they will encounter problems?

I was able to use the Task Manager and end the tasks for those users's sessions, then I logged them off the TS, but this is not really feasible, I don't want to login every night and make sure their open resources are killed and then log them off.



SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Well it's been a while since I responded or reviewed this problem...I have had to deal with some other major problems.

So here's an update:

I completely disabled all Group Policies within the AD, reconfigured users from Roaming to Local and I still seem to see Folder Redirection notifications in Event Viewer.

And at some point when users log off the terminal servers do crash, even when I go into TS Manager and log off those disconnected users.

Unluckynelson I am accepting your solution because it did help me out, even though some problems still exist, my other option is to rename each users profile on each terminal server and have them re-login, this should clean up any lingering issues with the old roaming profiles.

Right now there are too many terminal servers on the network and I plan to consolidate.

Thanks,
Mark
Glad I could assist. I am sorry I wasn't of more help.