Errors in Event Log

[Jerry Dubuke]

Hi everyone,
I just got 4 events in succession in my application log. Not sure what they
mean - they are new to exchange 2K3 I think. No other errors around it, no
alerts, and no errors around that timeframe in the other logs either.
Pentium Xeon processor with 1 gbyte RAM
Memory in use 803 MBytes
plenty of free space on disks
top process is store with 291MBytes used

help?!??

Time: 14:59:56
Source: MSExchangeAL
Category: Address List Sychronization
Event ID 8144
The service threw an out of memory exception

Time: 14:59:56
Source: MSExchangeAL
Category: Address List Sychronization
Event ID 8331
The service threw an unexpected exception which was caught at
f:\titanium\dsa\src\lra\abv_dg\abvdgs.cpp(1388)

Time: 14:59:56
Source: MSExchangeAL
Category: Address List Sychronization
Event ID 8144
The service threw an out of memory exception

Time: 14:59:56
Source: MSExchangeAL
Category: Address List Sychronization
Event ID 8144
The service threw an out of memory exception

[Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]]

Per www.eventid.net most appear to be cleared up with a reboot.

MSExchangeAL
Type Error
Description The service threw an out of memory exception.
Comments Gary Pillans (Last update 11/12/2003):
Restarting the server seemed to clear this problem up.

Jerry Dubuke wrote:

--
http://www.sbslinks.com/really.htm

[Jerry Dubuke]

OK - I will try to reboot later tonight after hours... but does anyone know
*why* it occurred? I had free memory, and exchange had most of the
available memory to start with.

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbra...@pacbell.net>
wrote in message news:efdZkahr...@TK2MSFTNGP12.phx.gbl...

[Ricky Morris [MSFT]]

Jerry,

You're at the borderline regarding the /3GB switch for the boot.ini file, per:

823440 You Must Use the /3GB Switch When You Install Exchange Server 2003 on a
http://support.microsoft.com/?id=823440

You may need to add the /3GB and /USERVA: switches to your boot.ini to avoid Out of Memory conditions.

Use performance monitor to trace virtual bytes used by the STORE.EXE process to track actual memory being
used by the store.exe process per the KB's instructions...Task Manager is not good enough.

As a precaution, make SURE that your Anti-Virus software is not scanning the \exchsrvr folders nor the
\system32\inetsrv folders with file level scanning. Use only a qualified Exchange 2003 anti-virus scanner to
scan the Exchange Server's databases.

Best Regards,

Ricky

Ricky Morris, MCSE

Microsoft Platforms Support Engineer
More SBS Info:
http://www.microsoft.com/sbserver
and
http://www.microsoft.com/windowsserver2003/sbs
===============================================
When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit
from your issue.
===============================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Jerry Dubuke]

Hi Ricky,
Thanks for the heads-up. I would never have thought to look there, since I
had nowhere near 3GB RAM in the system. I am currently monitoring the
Virtual Bytes in the Store process, and it is currently 837,533,696.
Bouncing down, and then back up to that number.
I will make the change to the boot.ini tonight and reboot the server after
hours.
My A/V (Norton) is set to exclude the actual databases in exchange, but I
had it set to scan the bin and other directories. Is that OK? I modified
it to exclude the whole EXCHSRVR directory, but not sure if it needs to be
that inclusive. I had already excluded the system32\inetsrv directory.
Thanks again for the help!
Jerry

""Ricky Morris [MSFT]"" <ric...@online.microsoft.com> wrote in message
news:V305Dajr...@cpmsftngxa06.phx.gbl...

[Chris Ard [MSFT]]

The biggest problem we ran into with Anti-virus programs was people
scanning their M: drive. This usually broke things. There are some
anti-virus programs like Scanmail that will scan mail messages as they come
into the server or leave the server. These don't require scanning the
Exchange directories. In your case, you don't need to exclude the entire
exchsrvr directory, but I would avoid scanning the mdbdata folder since I
have seen some problems with scanning the actual edb files.

Chris Ard
Small Business Server
Enterprise Platforms Support