• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 715
  • Last Modified:

Terminal Server failling

Hi. I'm running a Windows 2003 standard edition with TS 5 licences. Since a couple of months, I have a problem of duplicate printers when some users log off (random pattern, no particular user). I was able to manually end the session via the management console (It may took 10-15 minutes to user to be really log off from the system). But now, it's getting worse. As soon as I open the manager, it shuts itself down in 1-2 seconds. Almost everytime I reboot, I'll have a TSADMIN.EXE error message. Here's the log :

Faulting application tsadmin.exe, version 5.2.3790.3959, faulting module tsadmin.exe, version 5.2.3790.3959, fault address 0x0000b33f.

I also have this error message and don't know if it's related that appears from time to time : Fault bucket 402460537.

Does this ring a bell to someone? Thanks in advance.
1 Solution

Funky print drivers can cause issues.  Can you use the drivers that come with Windows?  If so that's best.  Also, how beefy is your TS Server?  And are you up to date on SP's and patches.

But I think it could be the print driver issue.

Good Luck,

- gurutc
admin_onrAuthor Commented:
Hi. All the patches and updates have been applied. The drivers are the ones supplied by the printer manufacturer (network printer) and Windows don't have them natively. What should be the good way to do? Installing the printers again (fresh install) forcing the use of the new supplied driver and doing the same with my 5 users? But I failed to see how it's related by the management console shutting down itself. Should I try to replace TSADMIN.EXE with a new one from another server?
Hello. I agree that it might be due to print driver issues. You might want to take a look at applying a GPO to your terminal server for printing. Here are some things to look at. You can google for details on these settings. If you need further guidance, let me know.

Terminal Server\Printer Redirection
 - Do not allow client printer redirection

 - Do not set default client printer to be default printer in a session

 - Redirect only the default client printer

 - Specify terminal server fallback printer driver behavior

 - Use Terminal Services Easy Print printer driver first

You can also look here if you want to apply other settings for your terminal servers via GPO.

Hope this helps

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

If your users are exiting out of TS by just clicking the X then the session will be left open/disconnected. You may want to adjust the setting to end a disconnected setting after x minutes in TS Configuration, RDP Properties, Sessions.
If the session is left open/disconnected and the users are reconnecting, sometimes it starts a new session and that could cause dup printers.
Also, when you end the session in TS Manager, this sets it to a disconnected state, you then have to Reset the connection. This will speed up that 10 - 15 minutes to actually end the session.
admin_onrAuthor Commented:
About the long delay, I've already done this settings. And the users are well aware to not click on the 'X'. Very well aware (long story). It's clearly something else. I'll try what Emsed suggest and I'll also reinstall all the drivers on the 5 computers so everyone will be using the same driver for the same printer.
What was the solution and did anyone help you come to your solution?

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now