TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

  Two thoughts, either your copy of ole32.dll in \winnt\system32 is corrupt
or you have a second pre sp5 copy floating around else where in your path.
Try finding and deleting all instances and then reapplying the service pack.

>From the Knowledgeable:

PRB: Relocating OLE32.DLL Causes an Access
    Violation

The information in this article applies to:

        Microsoft Windows 95 
        Microsoft Windows 98 
        Microsoft Windows NT 4.0



SYMPTOMS

   OLE32.dll expects to be loaded at a specified base address in a process.
If it is loaded at a different base address, the process might crash
unexpectedly. Also, under Windows NT 4.0, storage APIs (such as
StgCreateDocFile) return error 80030110 (STG_E_BADBASEADDRESS). 


   RESOLUTION

   At present, there is no way to work around this problem. However, this is
no longer a requirement under Windows NT 5.0. 


   STATUS

   This behavior is by design in Windows NT 4.0, Windows 95, and Windows 98.
Most applications will not run into this problem. 


   MORE INFORMATION

   You need to ensure that OLE32.dll is not relocated. There are two ways to
achieve this: 

   You should avoid dynamically linking to OLE32.dll in your applications. 

   You should make sure that your applications do not base their binaries
(.exes or .dlls) at the same base address as OLE32.dll. You can obtain the
base address of OLE32.dll by using the following command:              link
/dump /headers ole32.dll 

             OPTIONAL HEADER VALUES
             ....
             77B20000 image base
             ....



   NOTE: In the output of this command look for "image base." 

   Additional query words: 

   Keywords : kbole kbNTOS400 kbWinOS95 kbWinOS98 
   Version : WINDOWS:95; winnt:4.0 
   Platform : WINDOWS winnt 
   Issue type : kbprb 



                                        Last Reviewed: January 10, 2000
                             � 2000 Microsoft Corporation. All rights
reserved. Terms of Use.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 24, 2000 5:20 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Realsecure Error in NT 4.0 - Illegal System DLL relocation
- Ole32.dll -reply2



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 !!!!!



















Reply via email to