TSAdmin aborts and misfunctions

[Brad Smith]

We recently put 4 Win 2003 servers into production: an ADS server, a backup
ADS server as SQL server and TS server. They've been up for 10 days with
less than 10 TS users (but MANY more are planned).

We had an occurrence of TSAdmin on the TS just aborting when we selected the
TS server in the left pane. TSAdmin just disappeared and an App Event type
Error category 100 event id 1000 was generated with the description:

Faulting application tsadmin.exe, version 5.2.3790.0, faulting module
unknown, version 0.0.0.0, fault address 0x00000000.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

No matter what we did we could not get tsadmin to connect to the TS on the
TS.

During this period if we ran TSAdmin from the backup server and attempted to
connect to the TS in the left pane we got a message box:

Title:
Terminal Services Manager: tsadmin.exe - Application Error
Message:
The exception unknown software exception (0x0000409) occurred in the
application at location 0x00000000.

Rebooting all the systems fixed the problem.

All servers have all windows updates applied.

Any clue as to why this is happening?

Any general insight into how often we should plan on rebooting these servers
if that is the only to get tsadmin to work again?

We didn't bother to just reboot only the TS server so I don't know whether
that would have fixed the problem.

 

[Brad Smith]

Oh boy!!! I hope this doesn't reflect the quality and reliability of the
rest of Win 2003 terminal services.

There turns out to be a problem with tsadmin where it fails if a user that
has a 20 character user name is logged in to an RDP sesssion.

That is why this appeared to be an intermittent problem. Rebooting fixed it
until that user logged back in again.