I have two terminal servers using Windows 2008 Server SP2 that hang
randomly, sometimes once a day, and at least two or three times a week. When
it hangs, users can not close their sessions or can not open it, and
connected users can not work anymore.
For example : when the RDP session starts, the user is prompted for
credentials. Once the credentials are entered and user presses enter (or the
arrow), the RDP session displays "Welcome" with the rotating circle (to the
left), but the log on never gets any further. In this case, the only events
in event viewer consist of a chain of event id 7001, but they are not
explicit. The console is also hung, and the users already connected are
progressively hung too. I have to hard reboot the server, a classic restart
doesn't work at all.
As we are using an application with shared files, I have applied the
following Microsoft Hotfixes, http://support.microsoft.com/kb/972596 and
http://support.microsoft.com/kb/976674/ but I still have the problem (even if
it has worked a whole week).
Servers are almost up to date, they were installed on February 2010, the 8th.
I hope you will help me, and i you need i can give you more informations.
Kind Regards
Any good news yet?
OMourgues wrote:
Windows 2008 SP2 Terminal Server hangs
16-Mar-10
Hi,
I have two terminal servers using Windows 2008 Server SP2 that hang
randomly, sometimes once a day, and at least two or three times a week. When
it hangs, users can not close their sessions or can not open it, and
connected users can not work anymore.
For example : when the RDP session starts, the user is prompted for
credentials. Once the credentials are entered and user presses enter (or the
arrow), the RDP session displays "Welcome" with the rotating circle (to the
left), but the log on never gets any further. In this case, the only events
in event viewer consist of a chain of event id 7001, but they are not
explicit. The console is also hung, and the users already connected are
progressively hung too. I have to hard reboot the server, a classic restart
does not work at all.
As we are using an application with shared files, I have applied the
following Microsoft Hotfixes, http://support.microsoft.com/kb/972596 and
http://support.microsoft.com/kb/976674/ but I still have the problem (even if
it has worked a whole week).
Servers are almost up to date, they were installed on February 2010, the 8th.
I hope you will help me, and i you need i can give you more informations.
Kind Regards
Previous Posts In This Thread:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Featured Product / Service Review: TekPub
http://www.eggheadcafe.com/tutorials/aspnet/ae6e21fa-3443-4134-9d2e-39384482c80e/featured-product--servic.aspx
Since we do not use Citrix, we manage our users through the Microsoft
“Terminal Server Manager” snap-in on a management server. When this issue
occurs on the problem server, the snap-in stops responding on our management
server. This means we cannot determine who was on that server, send them a
message, or interact with them in any manner. We simply determine which
server is the culprit by attempting to logon to each server in the cluster
locally until we find the server that sits on “Applying user settings”.
Once we reboot this server, which kills all of the users logged onto that
server, the snap-in begins responding and all users can logon to the cluster
again.
Our environment is as follows:
Windows Server 2008 SP2 – (32 bit) [Completely Patched and Up-To-Date]
Office XP SP3
VMware vSphere (4.0)
I am astounded by the fact that Microsoft is taking this long to resolve an
issue of this magnitude. I am also shocked that the only resolution thus far
is to restart the server.
Please keep me informed of any updates on this issue. I will soon be opening
a ticket with Microsoft myself and will keep everyone informed if we make any
progress.
- Mike Sitler
http://support.microsoft.com/kb/980568
http://support.microsoft.com/kb/976674
http://support.microsoft.com/kb/956438
We have gone one week without any hangs and performance has improved
considerably. Hope this helps someone else.
"bugfixr" wrote:
> .
>
Has anyone else had success with this issue using these hotfixes?