TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ---------------------------------------------------------------------------- Hi Mark. There is a problem with Smartheap in NT. The work around is below. You need to prevent RS from allocating more than 500MB in one go. Once you set the pre-allocation to a number it can handle RS can safely extend the memory used until all the memory you have installed is used (if required). >I have in stall Real Secure on an Dell 2300 with Dual 500 MHz and a Gig of >Ram. My Question is why do I get OUT OT MEMORY in my application Log file. >This file Constantly Grows until I stop the Demon and Delete the OUT OF >MEMORY Errors in the application log file. Anyone have this Problem >Before. Any suggestion would be Helpful The bug you are finding could be a smartheap problem not a real secure problem . Find out how much memory is in the box and make sure you do not reallocate over 500MB ( i.e. if you have a Gig preall will be 50%, but if you have 2 gig then it is 25%) Symptoms: Error message - Detector Error:Network Engine running out of memory on Console and NT Event Log Effect: (Windows NT Only) Network Engines running on systems with large amounts of RAM (500+ MB) may encounter an Out of Memory condition at start up. Resolution: If you encounter this problem, do the following: 1. Shutdown the engine. 2. Edit the current.policy in the directory where the engine was installed. 3. Search for the term PreAllocationPercent. Find a section that looks as follows: []; PreAllocateMemory =B 1; PreAllocationPercent =L 80; The number following PreAllocationPercent dictates how much available memory will be pre- allocated for use by the engine Depending upon the amount of memory installed in the machine, decide on an initial number less than 80. You are advised to start from 40 on a 1 GB memory machine. 4. Replace the "PreAllocationPercent" number with this number. 5. Save the file and restart the engine. If you still see the problem, reduce the number and repeat the process again. When you find a number that works, repeat the process with larger and larger numbers until you've determined the optimal number (the largest percentage that does not cause the error). Beware aware if you get an error message about ole32.dll error , Do not change the value of the PreAllocateMemory =B 0; TO 1 If you cannot find a percentage that works, turn Memory PreAllocation off by putting 0 in the PreAllocateMemory field. This will make the engine ignore the value PreAllocationPercent : PreAllocateMemory =B 0; Save the file and restart your engine. How to determine the max amount of memory used by Engine Optionally you can determine the maximum amount of memory used by the NT Network Engine. Engine will work fine without this exercise as well. To determine the maximum amount of memory used by the NT Network Engine, follow these steps: 1. Shutdown the engine. 2. Edit the current.policy in the directory where the engine was installed. 3. Search for the word "NeedUpperBound" and change its value from 0 to 1. []; PreAllocateMemory =B 1; PreAllocationPercent =L 80; NeedUpperBound =B 0; 4. 4. Save the file and restart the engine. The engine will write back a new parameter to the [] section. This will look like this: UpperBound =L 160; This means that the upper bound of the memory is set at 160% of the preallocated memory. The engine will generate a "Detector_error: Network_engine memory upper bound reached" error messages in the Console and in the NT Event Log when the upper bound is reached : This means that RealSecure has reached 160% of the preallocated memory. You may change this value to find out how much maximum memory can be used by RealSecure before performance deteriorates. Looking at this value you can decide to upgrade the memory in your machine. Example: When you see a sequence similar to the following sequence of entries in your event log, 132 MB of Memory Available for the Engine PreAllocated 132 MB of Memory Memory upper bound set at 216 megs Network_engine memory upper bound reached this means that engine memory consumption reached 216 MB. Regards, Steve ---------------------------------------------------------------------------- Steve Reddock Consulting and Technical Support - Asia Region [EMAIL PROTECTED] Internet Security Systems KK, Japan Phone +81-3-5475-6458 Fax +81-3-5475-0557 http://www.iss.net http://www.isskk.co.jp Adaptive Network Security for the Enterprise PGP keys available on request ------------------------------------------------------------------------
