TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ---------------------------------------------------------------------------- Hello Marc, I do not recall seeing this recommendation you are describing for systems encountering this type of error message. There are multiple parameters that come into play. First the system specs are very important. I agree with you that it not always a good idea to destroy your data. However, reformatting your disk is a drastic solution. When we take a look at the customer's system specs, ISS has a standard resolution for this issue that does not require the format process. Only when this resolution fails to work, it may be necessary for you to reformat your Hard Drive. Here is the workaround: For Windows NT, the RealSecure Network Engines running on systems with large amounts of RAM (500+ MB) may encounter an Out of Memory condition at start up. Symptoms of this condition include "Detector_Error: Network_Engine running out of memory" error messages in the Console and in the NT Event Log, etc.. 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. 4. Find a section that looks as follows: [\config\Memory\]; 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. 5. Replace the "PreAllocationPercent" number with this number. 6. 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). 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. Cleo. ======================================================= Cleophas A. Toe | Internet Security Systems Tech. Support Engineer | Phone #: 678-443-6400 FTP://ftp.iss.net | Phone #: 888-447-4861 HTTP://www.iss.net |Fax #: 678-443-6485 Privacy Statement: http://www.iss.net/tech/support.php3 PGP Public Keys: http://www.iss.net/tech/sensitive.php3 Security through obscurity is counter-productive Adaptive Network Security for the Enterprise ======================================================= -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 29, 2000 9:32 AM To: Toe, Cleo (ISSAtlanta) Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Re: Realsecure Error in NT 4.0 - Illegal System DLL relocatio n - Ole32.dll -reply2 Let's go over this again, I did say the solution was recommended by ISS, but completing a dirty Windows NT install does solve the problem if one does not have the time to reformat the Hard Drive. I have witnessed the problem with various versions of OEM releases of Windows NT. (i.e. Gateway, Compaq, and DELL). For some reason those manufacturers modified a couple of .dll extensions to account for specific hardware that may be installed. The ole32.dll is used or referenced by some misc driver, and when you install ISS RealSecure it is looking for such & such rev of ole32.dll. I don't know the exact problem, ISS can simply fix the issue by modifying the installation routine and checking for the correct version of ole32.dll that is requires. Reformatting the hard drive can potentially destroy any logging information that detector has collected and was not able to send to the console before the application died. The rule of thumb is never destroy evidence unless you work for the government, have a paper shredder and your name is Ollie North. A couple of days ago, there were references on how to handle data and how to remove it from a system prior to reformatting. /m "Toe, Cleo (ISSAtlanta)" <[EMAIL PROTECTED]> 03/29/00 06:14 AM To: "Eng, Audra" <[EMAIL PROTECTED]>, "Cole, David (ISSWestCoast)" <[EMAIL PROTECTED]>, "Nguyen, Ann" <[EMAIL PROTECTED]>, "Christian, Brian (ISSCalifornia)" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: ISS Technical Support <[EMAIL PROTECTED]> Subject: RE: Re: Realsecure Error in NT 4.0 - Illegal System DLL relocatio n - Ole32.dll -reply2 Hello Audra, I have seen this problem several times. I have also noticed that I was copied in the email but my email address was spelled wrong. Well, for this issue, the relocation of the ole32.dll cannot be solved by registering the DLL. I have tried to unregister it. Regsvr32 /u <dll_name> and then register it anew without success. Rebooting the system does not solve it either. Reinstalling the WinNT OS did solve the issue. But, I will not recommend the solution provide in the email thread. It's better to reformat your HD and proceed with a clean installation of NT. I have tried something here to make sure that the repair process was not efficient. I have created an ERD using the CLI <rdisk /s> and then I checked to see if this will have the OLE dll. After a *find* I did not find anything there. Disable all unnecessary services for RealSecure and then install RealSecure. I have already dealt with it with customer who tried the repair process and they ended up with the same problem. Cleo. ======================================================= Cleophas A. Toe | Internet Security Systems Tech. Support Engineer | Phone #: 678-443-6400 FTP://ftp.iss.net | Phone #: 888-447-4861 HTTP://www.iss.net |Fax #: 678-443-6485 Privacy Statement: http://www.iss.net/tech/support.php3 PGP Public Keys: http://www.iss.net/tech/sensitive.php3 Security through obscurity is counter-productive Adaptive Network Security for the Enterprise ======================================================= -----Original Message----- From: Audra Eng [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 28, 2000 6:18 PM To: [EMAIL PROTECTED] Subject: Fwd: Re: Realsecure Error in NT 4.0 - Illegal System DLL relocation - Ole32.dll -reply2 FYI. >Delivered-To: [EMAIL PROTECTED] >Delivered-To: [EMAIL PROTECTED] >Delivered-To: [EMAIL PROTECTED] >From: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: Re: Realsecure Error in NT 4.0 - Illegal System DLL relocation - >Ole32.dll > -reply2 >X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 >Date: Fri, 24 Mar 2000 14:19:36 -0800 >X-MIMETrack: Serialize by Router on Apollo/Predictive(Release 5.0.2c >(Intl)|2 February > 2000) at 03/24/2000 05:19:39 PM, > Serialize complete at 03/24/2000 05:19:39 PM >Sender: [EMAIL PROTECTED] >X-Loop: issforum > > >TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to >[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! >--------------------------------------------------------------------------- - > >It appears that an old OLE32.dll Extension file is not interoperating well >with the ISS RealSecure 3.2 version.. > >If this is an engine, you can reblast it correct?? If you can, do the >following, do a dirty install of Windows NT 4.0, basically boot from a >CD-ROM, Hit repair, then hit format NTFS, install the full bloated NT 4.0, >then install Real Secure 3.2, after you have Real Secure 3.2, harden the >box. > >It could be that the OLE32.dll driver is just finicky, and doesn't like >being touched.. To bad... 'touch' is not a bad thing.. > >/m > > > > >[EMAIL PROTECTED] >03/24/00 02:19 PM > > > To: [EMAIL PROTECTED] > cc: > Subject: Re: Realsecure Error in NT 4.0 - Illegal System > DLL relocation - Ole32.dll >-reply > > >Hi Mark. > >Yes. Same error !!! > >Regards, >Rubens. > > >[EMAIL PROTECTED] >03/24/2000 07:32 PM GMT > >To: Rubens Caparica@Andersen Consulting >cc: [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: Re: Realsecure Error in NT 4.0 - Illegal System DLL relocation - > Ole32.dll -reply > > > >Hmm, interesting, Have you tried Windows NT Workstation for the engine..?? > >/mark > > > > >[EMAIL PROTECTED] >Sent by: [EMAIL PROTECTED] >03/24/00 09:56 AM > > > To: [EMAIL PROTECTED] > cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Realsecure Error in NT 4.0 - Illegal System DLL >relocation - Ole32.dll > > > >TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message >to >[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any >problems! >--------------------------------------------------------------------------- - > >Dear All; > >I have a problem installing Real Secure; and I hope you can help me to >over >come this problem. > >The configuration that I am using s/w and h/w as follow: > >HP LH SERVER 4, 1GB Ram, 200 Gb HD >WinNT4 server and SP5 as recommended >Real Secure 3.2.1 Network Engine >Internet Explorer 5 > >Management console is in other machine > >Problem: > >When I initiate the connection between the RealSecure Engine and the >Realsecure >Management Console, the follow error is shown in the RealSecure Engine >machine >NT error box: > >The system dll OLE32.DLL was relocated in memory. The application will not >run >properly. Contact the vendor to get the new version of DLL. > > >Can anybody help me ? > >Urgent help needed !!!! > >Thanks !!!!! > > > > > > > > > > > > > > > >
