STORE.EXE using up memory

<3763F9F2.798F @phxint.glasnet.ru-nomail0plea­se->...



SQL Server 6.5 was having performance problems, and Microsoft reccomended
using this setting to ensure that Exchange was releasing the memory.  This
server also has about 20 gig of file shares, with about 20 or so users
maintaining connections.

Me <khol @hotmail.com> wrote in <OUWIQZdt#GA.233@cppssbbsa03>:

        So your Exchange server is doing other things besides Exchange.  This
makes a difference.  In that scenario, you might want to (or have to) limit
Exchange's use of memory.  The "default" assumption is that Exchange is
running on a machine by itself, therefore it doesn't need to share.

You have to understand WHY it uses all avail to it memory:
InfoStore tries to cache access to DBs. It allocates memory from OS and uses it
as buffer for data in order to minimise disk access. It does not use standart
disk cache of the OS for this purpose.

Why? Do you have some other services running on this box that need memory or you
just love to see that you have 1.5GB of avail (unused for anything usefull)
memory?

Very simple to do - run PerfOpt, do not relocate DBs but near the end of the
wizard set an option of limiting memory usage.
The only practical reason for this - you have other services on the same box and
do not want them to starve for the memory (and with ExchServ55 store will give
memory back to whoever needs it).

We have 2 gig of memory in our exchange server, and STORE.EXE will use it
all eventually.  There is a way to limit the amount of memory that exchange
can use, and we set ours to 500 MB.  I can't remember the details, but we
found it on technet.

<37632EB9.9C8DF @phxint.glasnet.ru-nomail0plea­se->...

Sorry, silly of me.

Here goes:

Event ID: 3120
Source: MSExchangeMTA
Cat.: Resource
Type: Warning
Desc.: A resource limit has been reached when attempting to open an
association. Number of sessions configured: 30. [XAPI MAIN BASE 47 91] (14)

Event ID: 9316
Source: MSExchangeMTA
Cat.: Interface
Type: Warning
Desc.: An RPC communications error occurred. No data was sent over the RPC
connection. Locality table (LTAB) index: 239. Windows NT error: 9317. The
MTA will attempt to recover the RPC connection. [BASE IL INCOMING RPC 47
522] (12)

Event ID: 9215
Source: MSExchangeMTA
Cat.: Operating System
Type: Warning
Desc.: A sockets error 0 on a connect() call was detected. The MTA will
attempt to recover the sockets connection. Control block index: 2. [BASE IL
TCP/IP DRVR 8 262] (12)

Whether all of the above is related to STORE.EXE using up memory, I'm not
sure. The system haven't crashed yet, but Outlook Client connections running
very slow, when only 5-10 MB memory left. When this happen, after about
12-18 hours, I reboot the system and the picture starts over.

We have X.400 connections via ISDN link to 7 other Exchange servers. 5
running Exchange 5.5 and 2 Exchange 5.0. Also we have one 1MB Internet
connection.

Jan

Kirill S. Palagin <kpala @phxint.glasnet.ru-nomail0plea­se-> wrote in
message

Store.exe WILL use all avail to it memory. By design.
You may wish to run PerfOpt (make backup first) to better tune your
installation.

The resource limit when we've seen it has been amenable to adjustment via
registry changes. Microsoft Technet has complete details. These resources were
not adjustable on 5.0 and earlier versions, but in 5.5 you can adjust how many
buffers Exchange will use, and other limits as well. I don't know if these have
anything to do with Store.exe, however.

Our experience has been that Store.exe can do that after an upgrade. Never have
seen it after a fresh install. We have the luxury of having been able to add an
extra server to our site when upgrading, thereby avoiding any actual "upgrades"
of existing installations. Otherwise a file level database backup and restore
to the new server might work, but I'm not sure.
Steve

Full info from event please (ID, Source, Description, Categ and Type).