Low on system resource in terminal session

[Guest Wim van de Kruijs]

We have a Windows 2003 Terminal server (attached to SBS2003 server).

On it there are 15 to 20 clients. The server was initially installed with

Server 2003 standard and Office 2000. The server has Dual Xeon 2,8 Ghz, 4

Gbyte ram and 72 Gbyte HD Raid-1.

All the users are working on this terminal server, they have Windows 98

clients and there are 4 laptops with Windows XP.

Everything worked fine until I updated the server to SP2 and all the

security updates. I also upgraded Office 2000 to Office 2007 Standard. Also

Office 2007 is updated with the available updates from about 3 weeks ago.

 

The problem is now that some terminal sessions 'crashes'. Sometimes the user

sees a message that the system has no system resources. There are several

users who have this problem, but not all the users.

I have deleted the user profile and created a new one, this hasn't helped.

The same users have these problems. Other users do not have the problem. It

is possible that only the heavy users have the problem.

 

It seams that the problem occurs when they haven't accessed the PC for a

while. But there is no screensaver activated on the terminal server. I am now

trying to reproduce the problem but I have 2 few sessions open for more then

an hour now and I don't see the problem.

The users are not working at this time when I am writing this question

There are also no events which leed me to a solution.

 

Does anyone have any tips for me, please help me

[Guest Vera Noest [MVP]]

Re: Low on system resource in terminal session

 

Part of the cause is probably the upgrade from Office 2000 to 2007.

Have you checked both the System and the Application EventLog?

An error message on screen about a lack of system resources should

also create an Event in the EventLog.

 

As an example:

 

317249 - How to troubleshoot Event ID 2021 and Event ID 2022

http://support.microsoft.com/?kbid=317249

 

_________________________________________________________

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?V2ltIHZhbiBkZSBLcnVpanM=?= <Wim van de

Kruijs@discussions.microsoft.com> wrote on 17 mar 2008 in

microsoft.public.windows.terminal_services:

> We have a Windows 2003 Terminal server (attached to SBS2003

> server). On it there are 15 to 20 clients. The server was

> initially installed with Server 2003 standard and Office 2000.

> The server has Dual Xeon 2,8 Ghz, 4 Gbyte ram and 72 Gbyte HD

> Raid-1. All the users are working on this terminal server, they

> have Windows 98 clients and there are 4 laptops with Windows XP.

> Everything worked fine until I updated the server to SP2 and all

> the security updates. I also upgraded Office 2000 to Office 2007

> Standard. Also Office 2007 is updated with the available updates

> from about 3 weeks ago.

>

> The problem is now that some terminal sessions 'crashes'.

> Sometimes the user sees a message that the system has no system

> resources. There are several users who have this problem, but

> not all the users. I have deleted the user profile and created a

> new one, this hasn't helped. The same users have these problems.

> Other users do not have the problem. It is possible that only

> the heavy users have the problem.

>

> It seams that the problem occurs when they haven't accessed the

> PC for a while. But there is no screensaver activated on the

> terminal server. I am now trying to reproduce the problem but I

> have 2 few sessions open for more then an hour now and I don't

> see the problem. The users are not working at this time when I

> am writing this question There are also no events which leed me

> to a solution.

>

> Does anyone have any tips for me, please help me

[Guest Wim van de Kruijs]

Re: Low on system resource in terminal session

 

Thanks for the reply.

 

I do not see any events about it. No events 2021 or 2022 in the event log.

The only thing I see is an event that for example outlook.exe has generated

a problem in outlook.exe (something like this).

 

 

Wim

 

 

"Vera Noest [MVP]" wrote:

> Part of the cause is probably the upgrade from Office 2000 to 2007.

> Have you checked both the System and the Application EventLog?

> An error message on screen about a lack of system resources should

> also create an Event in the EventLog.

>

> As an example:

>

> 317249 - How to troubleshoot Event ID 2021 and Event ID 2022

> http://support.microsoft.com/?kbid=317249

>

> _________________________________________________________

> 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?V2ltIHZhbiBkZSBLcnVpanM=?= <Wim van de

> Kruijs@discussions.microsoft.com> wrote on 17 mar 2008 in

> microsoft.public.windows.terminal_services:

>

> > We have a Windows 2003 Terminal server (attached to SBS2003

> > server). On it there are 15 to 20 clients. The server was

> > initially installed with Server 2003 standard and Office 2000.

> > The server has Dual Xeon 2,8 Ghz, 4 Gbyte ram and 72 Gbyte HD

> > Raid-1. All the users are working on this terminal server, they

> > have Windows 98 clients and there are 4 laptops with Windows XP.

> > Everything worked fine until I updated the server to SP2 and all

> > the security updates. I also upgraded Office 2000 to Office 2007

> > Standard. Also Office 2007 is updated with the available updates

> > from about 3 weeks ago.

> >

> > The problem is now that some terminal sessions 'crashes'.

> > Sometimes the user sees a message that the system has no system

> > resources. There are several users who have this problem, but

> > not all the users. I have deleted the user profile and created a

> > new one, this hasn't helped. The same users have these problems.

> > Other users do not have the problem. It is possible that only

> > the heavy users have the problem.

> >

> > It seams that the problem occurs when they haven't accessed the

> > PC for a while. But there is no screensaver activated on the

> > terminal server. I am now trying to reproduce the problem but I

> > have 2 few sessions open for more then an hour now and I don't

> > see the problem. The users are not working at this time when I

> > am writing this question There are also no events which leed me

> > to a solution.

> >

> > Does anyone have any tips for me, please help me

>