Re: tsshutdn causes TS to hang
- From: pstacks <pstacks@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 25 Sep 2006 06:26:02 -0700
Ad,
Are you still having the same problem? We have a similar, albeit smaller,
situation here where the software vendor suggests twice weekly shutdows. The
shutdown goes ok, the TS service is set to autostart, which it does. No one
however can connect. When we restart manually there is no problem. Did you
ever try the shutdown with the AT?
--
pstacks
"Ad van den Broek" wrote:
Hi Alex,.
Thanks for your response. We are managing 15 terminal servers at 12
different customer sites. At 11 sites also SBS2003 servers are running, 1
site has an SBS2000 server. So it's always 1 SBS plus 1 or 2 terminal servers
running Windows 2003 Server. We use this procedure for some years now because
we experience unexpected behavior from terminal servers if we don't reboot
them at regular times. Because all the customers have different needs in
business software and tools it's impossible for us to check all the software
they use for possible memory leaks and other inconveniences. Rebooting these
systems at night is a simple and proved stability enhancement.
The issue is that this procedure has been working fine for a long time. The
problems we are facing now only arise in the SBS2003 environments, the SBS2K
site is running smoothly.
The event we get is like this:
The attempt by user NT AUTHORITY\SYSTEM to restart/shutdown computer
<TS Name> failed
Data:
0000: 80 58 f9 77
I’ve seen more issues in the newsgroups with the same problem, but there’s
no answer yet. Again, I suspect one of the more recent MS Updates to cause
these problems. I found 2 servers that reboot nice every night. One is
Pre-SP1, the other one didn’t install any updates for a couple of months.
Regards,
Ad.
"Alex Balcanquall [MSFT]" schreef:
Why do you reboot every night?
There should be no need to reboot a server out side of patching and install
cycles and would indicate perhaps you have some other more serious issue
like a memory leak, if so it could cause strange issues such as you
describe. Have you tried scheduling using the AT command and the shutdown
command instead to see if that helps?
http://support.microsoft.com/default.aspx?kbid=835302
Alex Balcanquall
Microsoft
This e-mail is provided "AS IS" with no warranties, and confers no rights.
"Ad van den Broek" <AdvandenBroek@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:40DFB999-5EB9-48FD-B08A-0DA3B893CA55@xxxxxxxxxxxxxxxx
We have a SBS2003 server and a W2K3 TS. Both running SP1. The SBS has a
scheduled task for rebooting the TS every night with tsshutdn. This has
been
running fine for a long time. The last couple of weeks sometimes this
reboot
does'nt work anymore. The syslog shows event 1073/user32. No remote
connections to the TS are accepted anymore. Sometimes resetting the RDP
protocol in TS Manager helps, but not always. We are experiencing the same
problem at some of our customers sites, but also only the last couple of
weeks. Looks like some MS update is the cause?????
- Follow-Ups:
- Re: tsshutdn causes TS to hang
- From: Ad van den Broek
- Re: tsshutdn causes TS to hang
- Prev by Date: Re: cant connect to 2003 server in remote desktop for admin mode
- Next by Date: Re: EventID 1500/1508
- Previous by thread: Re: cant connect to 2003 server in remote desktop for admin mode
- Next by thread: Re: tsshutdn causes TS to hang
- Index(es):
Relevant Pages
|
