Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

VB 4.0 Setup Problem - OLEAUT32.DLL

VB 4.0 Setup Problem - OLEAUT32.DLL

VB 4.0 Setup Problem - OLEAUT32.DLL

Has anyone come across the following problem:

I am installing a VB4.0 app onto a Win95 OSR2 machine with the latest version of OLEAUT32.DLL (i.e. MS OLE Update applied). The master development machine (VB4) contains the OLE versions as at the time of the VB 4.0 CD (i.e. earlier).

When the setup.exe is run, all runs fine until OLEAUT32.DLL is to be copied. I understood (and the log files seem to confirm) that only newer files are copied from installation disks. However, the error message 'Access violation' is displayed on OLEAUT32.DLL and setup is aborted.

If you ignore the error, the OCX's then fail to regoster.

Any ideas?



RE: VB 4.0 Setup Problem - OLEAUT32.DLL


The most likely problem (although not the only one) is that there is a VB app already running, probably one with an icon in the system tray if you've already closed other running applications.

Typically 'Access violation' is encountered when the file to be replaced is already in use by an application running, although it can be encountered when a closed application failed to clean up after itself and remove oleaut32 from memory. That latter condition usually indicates memory problems that require a restart of Windows to clear (not necessarily a machine reboot, just 'logon as new user' restart of Windows).

There is another possibility, that being a mismatch of versions in the OLE dll set. There are several different versions of the OLE libraries, but they do not coexist well - or at all!.

One last thing to check - this drove me crazy for about a week - is what version(s) of oleaut32 exist on the target machine and where they are in the path. This one's not very common, but its _very_ sneaky <grin!>.

RE: VB 4.0 Setup Problem - OLEAUT32.DLL

Thanks for the reply....I'll check these out next week.


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close