Store.exe / Registry change

[Guest]

Hello,

I will start with a breif history of our problem. We have a Windows server
2000 machine which had 1Gb Ram. Over the last month or so, the server would
just pratically hang for a few hours and then would be fine. While the server
would be extremely slow, the following event logs would appear.

EVENT # : 5444
EVENT LOG : Application
EVENT TYPE : Error
SOURCE : Perflib
EVENT ID : 1015
COMPUTER : 8XWXF0J
TIME : 06/06/2007 16:48:20
MESSAGE : The timeout waiting for the performance data collection
function "PerfOS" in the "C:\WINNT\system32\perfos.dll" Library to finish has
expired. There may be a problem with this extensible counter or the service
it is collecting data from or the system may have been very busy when this
call was attempted.

It seemed to relate to lack of memory.

It seemed that the Store.exe was taking up about 400mb of ram, but my
understanding is that the store.exe would use as much ram as there is
avaliable and the allocate this memory to something else as and when it is
needed.

We decided that it was time to upgrade the server with more ram. All memory
sticks were removed and replaced with four 512mb ram sticks. (Out with the
old, in with the new).

It seemed to be better, however the server still hangs every so often with
exactly the same message. The store is now using about 1.2Gb.

I may be wrong but I think that the store.exe is using as much ram as it
wants but is not giving the ram usage back when other programs need it. Hence
the slow system. This is because the hanging behaviour only happens during
working hours.

My boss thinks, that it could be a possibility that the one of the hard
drives are failing and there is something wrong with the page file.

I was wondering if there was any way that we could configure the registry so
that the store.exe process only takes up 1Gb of ram???

Please let me know your thoughts.

Many thanks,

Luke

 

[John John]

It isn't necessarilly saying anything as to wheter or not you have a
lack of or a memory problem. What it is saying is that you (or
something else) are using Perfmon to monitor Operating Systems objects
like Cache, Memory, Object, Paging File, Processor, System (PerfOS,
PerfOs.dll) and that perfmon is timing out before it can collect
information on the object(s).

Check here:

Collect Timeout
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/94221.mspx?mfr=true

The key to check is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance

NOTE: On Windows 2000, OpenProcedureWaitTime is global to all
performance extension DLLs. If the Open Timeout registry value, which is
performance extension DLL-specific, is not present, then the operating
system will use the global OpenProcedureWaitTime registry value, if it
is present. Similarly, if the Collect Timeout registry value is not
present, the operating system will use the global OpenProcedureWaitTime
registry value, if present. If the OpenProcedureWaitTime registry value
is not present, the default timeout value is 10,000 (milliseconds).

[end quote]

http://support.microsoft.com/kb/226494

John

 

[Luke Chalmers]

John,

After having a look at this further, I would say that the performance
library errors in the event log are an affect of what is going on. The CPU
maxes out at 100% during this period and in task manager the avaliable
memory just drops. The store.exe just stay at 1.2 ish Gb and I strongly feel
that this is the problem.

Do you think I am way off track here?

Luke

It isn't necessarilly saying anything as to wheter or not you have a lack
of or a memory problem. What it is saying is that you (or something else)
are using Perfmon to monitor Operating Systems objects like Cache, Memory,
Object, Paging File, Processor, System (PerfOS, PerfOs.dll) and that
perfmon is timing out before it can collect information on the object(s).

Check here:

Collect Timeout
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/94221.mspx?mfr=true

The key to check is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance

NOTE: On Windows 2000, OpenProcedureWaitTime is global to all performance
extension DLLs. If the Open Timeout registry value, which is performance
extension DLL-specific, is not present, then the operating system will use
the global OpenProcedureWaitTime registry value, if it is present.
Similarly, if the Collect Timeout registry value is not present, the
operating system will use the global OpenProcedureWaitTime registry value,
if present. If the OpenProcedureWaitTime registry value is not present,
the default timeout value is 10,000 (milliseconds).

[end quote]

http://support.microsoft.com/kb/226494

John

Hello,

I will start with a breif history of our problem. We have a Windows
server 2000 machine which had 1Gb Ram. Over the last month or so, the
server would just pratically hang for a few hours and then would be fine.
While the server would be extremely slow, the following event logs would
appear.

EVENT # : 5444
EVENT LOG : Application
EVENT TYPE : Error
SOURCE : Perflib
EVENT ID : 1015
COMPUTER : 8XWXF0J
TIME : 06/06/2007 16:48:20
MESSAGE : The timeout waiting for the performance data collection
function "PerfOS" in the "C:\WINNT\system32\perfos.dll" Library to finish
has expired. There may be a problem with this extensible counter or the
service it is collecting data from or the system may have been very busy
when this call was attempted.

It seemed to relate to lack of memory.

It seemed that the Store.exe was taking up about 400mb of ram, but my
understanding is that the store.exe would use as much ram as there is
avaliable and the allocate this memory to something else as and when it
is needed.

We decided that it was time to upgrade the server with more ram. All
memory sticks were removed and replaced with four 512mb ram sticks. (Out
with the old, in with the new).

It seemed to be better, however the server still hangs every so often
with exactly the same message. The store is now using about 1.2Gb.

I may be wrong but I think that the store.exe is using as much ram as it
wants but is not giving the ram usage back when other programs need it.
Hence the slow system. This is because the hanging behaviour only happens
during working hours.

My boss thinks, that it could be a possibility that the one of the hard
drives are failing and there is something wrong with the page file.

I was wondering if there was any way that we could configure the registry
so that the store.exe process only takes up 1Gb of ram??? Please let me
know your thoughts.

Many thanks,

Luke

 

[John John]

Are any other error logged in the Event Log? The Exchange store will
take all the memory that you can throw at it, and then if it could it
would take all the memory out of the computer sitting next to it! That
is how it is designed. I am not an Exchange Server expert but it is
generally recognized that it is best to run Exchange on Windows 2000
Advanced Server or better and to use the /3GB switch if you have more
than 1GB RAM, if Exchange sees that there is more than 1GB RAM in the
machine it thinks it hit the jackpot and it will try to appropriate
itself of all the RAM on the machine. There are many articles about
Exchange and RAM usage on Microsoft.com, head over there and do some
searching and reading. There was a discussion about Exchange and memory
usage issues here not too long ago, you can read it here:

http://groups.google.com/group/micr...ae81c/eb59d43d81ba4c37?tvc=1#eb59d43d81ba4c37

There are links there to relevant Microsoft articles and to special
tools to help configure Exchange on machines with large amounts of RAM.

John

John,

After having a look at this further, I would say that the performance
library errors in the event log are an affect of what is going on. The CPU
maxes out at 100% during this period and in task manager the avaliable
memory just drops. The store.exe just stay at 1.2 ish Gb and I strongly feel
that this is the problem.

Do you think I am way off track here?

Luke

It isn't necessarilly saying anything as to wheter or not you have a lack
of or a memory problem. What it is saying is that you (or something else)
are using Perfmon to monitor Operating Systems objects like Cache, Memory,
Object, Paging File, Processor, System (PerfOS, PerfOs.dll) and that
perfmon is timing out before it can collect information on the object(s).

Check here:

Collect Timeout
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/94221.mspx?mfr=true

The key to check is:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfOS\Performance

NOTE: On Windows 2000, OpenProcedureWaitTime is global to all performance
extension DLLs. If the Open Timeout registry value, which is performance
extension DLL-specific, is not present, then the operating system will use
the global OpenProcedureWaitTime registry value, if it is present.
Similarly, if the Collect Timeout registry value is not present, the
operating system will use the global OpenProcedureWaitTime registry value,
if present. If the OpenProcedureWaitTime registry value is not present,
the default timeout value is 10,000 (milliseconds).

[end quote]

http://support.microsoft.com/kb/226494

John

Hello,

I will start with a breif history of our problem. We have a Windows
server 2000 machine which had 1Gb Ram. Over the last month or so, the
server would just pratically hang for a few hours and then would be fine.
While the server would be extremely slow, the following event logs would
appear.

EVENT # : 5444
EVENT LOG : Application
EVENT TYPE : Error
SOURCE : Perflib
EVENT ID : 1015
COMPUTER : 8XWXF0J
TIME : 06/06/2007 16:48:20
MESSAGE : The timeout waiting for the performance data collection
function "PerfOS" in the "C:\WINNT\system32\perfos.dll" Library to finish
has expired. There may be a problem with this extensible counter or the
service it is collecting data from or the system may have been very busy
when this call was attempted.

It seemed to relate to lack of memory.

It seemed that the Store.exe was taking up about 400mb of ram, but my
understanding is that the store.exe would use as much ram as there is
avaliable and the allocate this memory to something else as and when it
is needed.

We decided that it was time to upgrade the server with more ram. All
memory sticks were removed and replaced with four 512mb ram sticks. (Out
with the old, in with the new).

It seemed to be better, however the server still hangs every so often
with exactly the same message. The store is now using about 1.2Gb.

I may be wrong but I think that the store.exe is using as much ram as it
wants but is not giving the ram usage back when other programs need it.
Hence the slow system. This is because the hanging behaviour only happens
during working hours.

My boss thinks, that it could be a possibility that the one of the hard
drives are failing and there is something wrong with the page file.

I was wondering if there was any way that we could configure the registry
so that the store.exe process only takes up 1Gb of ram??? Please let me
know your thoughts.

Many thanks,

Luke