Software

Ask something
Discussion Locked

Exchange 5.5 '1160' Error

0 helpful
7 replies

by timseery 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am a contractor with a large government agency and a couple of the email servers are experiencing '1160' memory errors and users are no longer able access their email via Outlook. These errors occur when the user connection peak somewhere between 900 and a 1000.

Both servers are running the Enterprise version of Exchange 5.5 but not the Enterprise version of Windows NT 4.0. Each Server has Quad 700Mhz Xeon processors and 2 GB of RAM.

We (the contractor) has argued the problem is that Information Store (STORE.EXE) does not have enough memory to handle the number of users and this coupled by the fact that Exchange Enterprise Edition is running on the Windows NT Server product, which the per-process address limit is 2 GB, instead of Windows NT Enterprise Edition (4GT), which increases this limit to 3 GB.

The customer said that they were told by Microsoft to remove 1GB of physical RAM because Exchange may not be addressing it correctly.

We believe this is a big load of crap and that we should add an additional 2 GB and upgrade to the Enterprise version of Windows NT or build a new server and move some users to the box.

The problem was solved at another site by reducing the amount data in the store by moving users to an additional server.

Comments and suggestions are welcome.

7 replies

by lordinfidel

I found a couple of things.

2 are bs with the install the latest sp spiel;
although Q195006 did give a good description and cause of the problem. I reccomend reading it.

Q178911 actually has a remedy that makes sense.

CAUSE
This error may be reported if the Performance Optimizer is run and, in the Memory Usage properties, the value for Limit Memory Usage to MB is set to something other than zero (0).

Because this value sets the limit on how much memory all of Microsoft Exchange has to use, the lower the value, the more likely this error message is to be displayed. If this value is set too low, for example, to 25, the services will run, but after a short time the server's performance will degrade. Shutting down the service will take a long time as well.

RESOLUTION
To correct this problem, run Microsoft Exchange Performance Optimizer and reset the to zero (0).

by lordinfidel

One last thing;

Microsoft recommends that you run the Performance Optimizer (Perfwiz.exe) on an Exchange Server computer after you perform a service pack update.

There are generally modifications and improvements to the Performance Optimizer (Perfwiz.exe) in each service pack.

The Performance Optimizer is a very sophisticated tuning and balancing tool that you should also use in the following situations:

After every new installation of Exchange Server or upgrade of Exchange Server, before you put the server into production.

After you add components (such as connectors) to a server, including directory replication connectors.

When the number of users on your server, site, or organization changes significantly.

by maxwell edison

I would surmise that the Microsoft suggested resolution of simply removing RAM both is and is not, as you put it, a big load of crap.

Microsoft Knowledge Base Article Q195006 titled, "Resource Failure Error on Computers with More Than 800 MB of RAM" does indeed reference the error you mentioned. However, another solution, as suggested in that article, is to simply apply the latest service pack.

Here is a link to that article:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q195006&

REMOVE SPACES from the pasted URL.

This discussion is closed to new replies.