Re: Virtual Memory Error




One thing he could, according to that article is upgrade to 2003, which does have the /3GB switch in all versions.

"Just as a side note or FYI, Windows [Server] 2003, all SKUs, will support the /3GB switch, so that's going to be a big plus for a lot of smaller customers."

Does this switch exist in 2003?

Cheers,

Cliff

John John wrote:
You're in a catch 22 situation. If Exchange sees that there is more than 1GB of RAM it thinks that it hit the jackpot all will try to grab as much RAM as it can. If you have an Advanced Server you can us the /3GB switch in the boot.ini file and it helps keep things under control. Being that you only have Server the catch 22 part is that the problems are worse if you have more than 1GB RAM but the /3GB switch doesn't work with the "regular" Server 2000, Microsoft recommends Advanced Server for Exchange with more than 1GB RAM. There is information about the problem here: http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Ftranscripts%2Fwct042903.asp


There isn't much that you can do other than making sure that Exchange is installed and configured optimally and that it runs as smoothly as possible. Make sure that you have no unused groups configured, Exchange grabs and allots RAM for all groups, even if they are unused. This utility can help with the configuration and may adjust Exchange's hungry behaviour when more than 1GB of RAM is present:

http://www.microsoft.com/downloads/details.aspx?familyid=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en

http://www.microsoft.com/downloads/details.aspx?FamilyID=4F2F1339-CBCD-4D26-9174-F30C10D7EC4C&displaylang=en


John

TJ wrote:

Hello, and thanks for your assistance in advanced. I am running a windows 2000 server with exchange server also installed. It has 1.5GB of physical ram and the paging file is set for 100-600MB for the C drive and 400-2350 for the E drive. The reccomended value is 2300MB. The problem is, a few hours after a reboot, the following error appears: "Your system is low on virtual memory. Windows is increasing the size of your virutal memory paging file."
There is plenty of disk space on all drives - >5GB Free
Drives have been defragmented.
It appears that store.exe is using 800MB of memory.
Physical memory available generally runs between 300MB-500MB Free.
Nothing in the event viewer regarding this issue.
Any suggestions?

Thanks Again.





--

Have you ever noticed that if something is advertised as 'amusing' or 'hilarious', it usually isn't?
.



Relevant Pages

  • Re: Alocated Memory Error (SQLSERVR)
    ... but my understanding is that the MSDE instances are designed to ... and you don't want it grabbing all that RAM. ... running but non ever going about 200mb of memory usage. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)
  • Re: Alocated Memory Error (SQLSERVR)
    ... FWIW I am not using sbs 2003 premium, ... non ever going about 200mb of memory usage. ... on what you should throttle the RAM to. ... Server 2000 SP4, ...
    (microsoft.public.windows.server.sbs)
  • Re: Allocated Memory Alerts & Mem Usage vs. VM Size
    ... haven't added the /3GB switch. ... It's now been roughly a week since the change and the memory situation seems ... Although the memory settings I applied to the sql server instance ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Alocated Memory Error (SQLSERVR)
    ... what you should throttle the RAM to. ... Server 2000 SP4, ... The memory problem on my ... shared exchange server address book or anything exchange related). ...
    (microsoft.public.windows.server.sbs)