Slow performance during certain hours.

  • Thread starter Thread starter Cardin Smith
  • Start date Start date
C

Cardin Smith

Guest
We have a Terminal Server which at any given time can have 15 users connected
to it. During normal working hours everything runs fairly well, with no
performance issues. But at 7am and 5am (approximately), the system seems to
grind to a hault.. this isn't a heavy usage time, and it could be only a few
of the users experiencing this problem and not all of them.
The service is spread out over 3 sites, Head office and Small office A & B.
The following faults also appear in the Application event log:

Event ID:1053 - Windows cannot determine the user or computer name. (The
RPC server is unavailiable).
Event ID:1001 - Fault bucket 443141905 (Application Hang)
Event ID:1010 - Failed to set the users home directory.
Event ID:4193 - MS DTC started with the following settings....

Included in these errors are error messages from the Antivirus system
(Mcaffee Antivirus is running on the terminal server and in the terminal
clients) and that the main software the users use (a software called Gemini)
has hanged.


So to sum it up:
The Terminal Server services is being used by the main office (where the
server is) and the 2 smaller offices. In the main office there is a Windows
2003 Small business sever, which has a sites and services set up with the
servers at the smaller offices. The servers at the smaller offices are set to
replicate from the main server in the main office (strange enough the
terminal server isnt included anywhere in this list).
On any given day (although normally every day) the terminal server
performance slows down at around 7 am and 5 pm although usage around those
times are nominal compaired to during the peak times of the day. No back up
or antivirus scans are being done at this time.

Any ideas of what the problem could be.. as i've read that the "RPC" issues
can cause the server to slow down and time out. Or is there any way to
properly do a performance monitor of the server?
 
Re: Slow performance during certain hours.

The fixed times that the problem occurs would suggest to me that it
could be the site servers replicating with the servers in the main
office, thereby saturating the connection. Have you checked if and
when replication is scheduled to occur? This should also create
records in the EventLog on the servers who participate in
replication.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Q2FyZGluIFNtaXRo?= <Cardin
Smith@discussions.microsoft.com> wrote on 08 nov 2007 in
microsoft.public.windows.terminal_services:

> We have a Terminal Server which at any given time can have 15
> users connected to it. During normal working hours everything
> runs fairly well, with no performance issues. But at 7am and 5am
> (approximately), the system seems to grind to a hault.. this
> isn't a heavy usage time, and it could be only a few of the
> users experiencing this problem and not all of them. The service
> is spread out over 3 sites, Head office and Small office A & B.
> The following faults also appear in the Application event log:
>
> Event ID:1053 - Windows cannot determine the user or computer
> name. (The
> RPC server is unavailiable).
> Event ID:1001 - Fault bucket 443141905 (Application Hang)
> Event ID:1010 - Failed to set the users home directory.
> Event ID:4193 - MS DTC started with the following settings....
>
> Included in these errors are error messages from the Antivirus
> system (Mcaffee Antivirus is running on the terminal server and
> in the terminal clients) and that the main software the users
> use (a software called Gemini) has hanged.
>
>
> So to sum it up:
> The Terminal Server services is being used by the main office
> (where the
> server is) and the 2 smaller offices. In the main office there
> is a Windows 2003 Small business sever, which has a sites and
> services set up with the servers at the smaller offices. The
> servers at the smaller offices are set to replicate from the
> main server in the main office (strange enough the terminal
> server isnt included anywhere in this list). On any given day
> (although normally every day) the terminal server performance
> slows down at around 7 am and 5 pm although usage around those
> times are nominal compaired to during the peak times of the day.
> No back up or antivirus scans are being done at this time.
>
> Any ideas of what the problem could be.. as i've read that the
> "RPC" issues can cause the server to slow down and time out. Or
> is there any way to properly do a performance monitor of the
> server?
 
Re: Slow performance during certain hours.

Thanks for the reply Vera.

At the moment replication is set to occur continously throughout the day
using the following schedule:

Main Site - Small Office A = 4 times per hour, all day
Main Site - Small Office B = 2 times per hour, all day

Could it be that at the particular times during the day they are both
running with each other? The problem is there isn't much replication which
needs to take place, as i thought that with 2003 it only replicates exact
changes? New users aren't created every day. The only thing that happens is
the terminal server is used throughout the entire day.

"Vera Noest [MVP]" wrote:

> The fixed times that the problem occurs would suggest to me that it
> could be the site servers replicating with the servers in the main
> office, thereby saturating the connection. Have you checked if and
> when replication is scheduled to occur? This should also create
> records in the EventLog on the servers who participate in
> replication.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?Q2FyZGluIFNtaXRo?= <Cardin
> Smith@discussions.microsoft.com> wrote on 08 nov 2007 in
> microsoft.public.windows.terminal_services:
>
> > We have a Terminal Server which at any given time can have 15
> > users connected to it. During normal working hours everything
> > runs fairly well, with no performance issues. But at 7am and 5am
> > (approximately), the system seems to grind to a hault.. this
> > isn't a heavy usage time, and it could be only a few of the
> > users experiencing this problem and not all of them. The service
> > is spread out over 3 sites, Head office and Small office A & B.
> > The following faults also appear in the Application event log:
> >
> > Event ID:1053 - Windows cannot determine the user or computer
> > name. (The
> > RPC server is unavailiable).
> > Event ID:1001 - Fault bucket 443141905 (Application Hang)
> > Event ID:1010 - Failed to set the users home directory.
> > Event ID:4193 - MS DTC started with the following settings....
> >
> > Included in these errors are error messages from the Antivirus
> > system (Mcaffee Antivirus is running on the terminal server and
> > in the terminal clients) and that the main software the users
> > use (a software called Gemini) has hanged.
> >
> >
> > So to sum it up:
> > The Terminal Server services is being used by the main office
> > (where the
> > server is) and the 2 smaller offices. In the main office there
> > is a Windows 2003 Small business sever, which has a sites and
> > services set up with the servers at the smaller offices. The
> > servers at the smaller offices are set to replicate from the
> > main server in the main office (strange enough the terminal
> > server isnt included anywhere in this list). On any given day
> > (although normally every day) the terminal server performance
> > slows down at around 7 am and 5 pm although usage around those
> > times are nominal compaired to during the peak times of the day.
> > No back up or antivirus scans are being done at this time.
> >
> > Any ideas of what the problem could be.. as i've read that the
> > "RPC" issues can cause the server to slow down and time out. Or
> > is there any way to properly do a performance monitor of the
> > server?
>
 
Re: Slow performance during certain hours.

Then that doesn't seem to be the cause of the problem, since it
would be happening during the daytime as well.
I think that you will have to perform both performance monitoring
of the server itself and the network during these hours to find out
what is going on.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Q2FyZGluIFNtaXRo?=
<CardinSmith@discussions.microsoft.com> wrote on 09 nov 2007 in
microsoft.public.windows.terminal_services:

> Thanks for the reply Vera.
>
> At the moment replication is set to occur continously throughout
> the day using the following schedule:
>
> Main Site - Small Office A = 4 times per hour, all day
> Main Site - Small Office B = 2 times per hour, all day
>
> Could it be that at the particular times during the day they are
> both running with each other? The problem is there isn't much
> replication which needs to take place, as i thought that with
> 2003 it only replicates exact changes? New users aren't created
> every day. The only thing that happens is the terminal server is
> used throughout the entire day.
>
> "Vera Noest [MVP]" wrote:
>
>> The fixed times that the problem occurs would suggest to me
>> that it could be the site servers replicating with the servers
>> in the main office, thereby saturating the connection. Have you
>> checked if and when replication is scheduled to occur? This
>> should also create records in the EventLog on the servers who
>> participate in replication.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?Q2FyZGluIFNtaXRo?= <Cardin
>> Smith@discussions.microsoft.com> wrote on 08 nov 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > We have a Terminal Server which at any given time can have 15
>> > users connected to it. During normal working hours everything
>> > runs fairly well, with no performance issues. But at 7am and
>> > 5am (approximately), the system seems to grind to a hault..
>> > this isn't a heavy usage time, and it could be only a few of
>> > the users experiencing this problem and not all of them. The
>> > service is spread out over 3 sites, Head office and Small
>> > office A & B. The following faults also appear in the
>> > Application event log:
>> >
>> > Event ID:1053 - Windows cannot determine the user or
>> > computer name. (The
>> > RPC server is unavailiable).
>> > Event ID:1001 - Fault bucket 443141905 (Application Hang)
>> > Event ID:1010 - Failed to set the users home directory.
>> > Event ID:4193 - MS DTC started with the following
>> > settings....
>> >
>> > Included in these errors are error messages from the
>> > Antivirus system (Mcaffee Antivirus is running on the
>> > terminal server and in the terminal clients) and that the
>> > main software the users use (a software called Gemini) has
>> > hanged.
>> >
>> >
>> > So to sum it up:
>> > The Terminal Server services is being used by the main
>> > office (where the
>> > server is) and the 2 smaller offices. In the main office
>> > there is a Windows 2003 Small business sever, which has a
>> > sites and services set up with the servers at the smaller
>> > offices. The servers at the smaller offices are set to
>> > replicate from the main server in the main office (strange
>> > enough the terminal server isnt included anywhere in this
>> > list). On any given day (although normally every day) the
>> > terminal server performance slows down at around 7 am and 5
>> > pm although usage around those times are nominal compaired to
>> > during the peak times of the day. No back up or antivirus
>> > scans are being done at this time.
>> >
>> > Any ideas of what the problem could be.. as i've read that
>> > the "RPC" issues can cause the server to slow down and time
>> > out. Or is there any way to properly do a performance monitor
>> > of the server?
 
Back
Top