Follow

Error: Faulting module OLEAUT32.dll

Symptoms:

Intermittent crashes during execution that result in a "hung" load. You will find the error message if you go through the error in the event viewer.

Error Message:

No error message occurs in TX DWA.  The load simply stays in "Running/Unknown" status.

However, an error does occur in the Windows Event Log:

Faulting application name: timeXtender.exe, version: <VersionNumber>, time stamp: <TimeStamp>
Faulting module name: OLEAUT32.dll, version: <VersionNumber>, time stamp: <TimeStamp>

Provisional Advice: 

We have discovered that this error may sometimes occur immediately after executing an Excel data source table while using SSIS transfer.  Although the issue may also be caused by a faulty OLEAUT32.dll file as outlined below, switching your Excel data sources over to ADO.net is a good thing to try first.

Note that this switch may cause changes in your Business Unit table data types, so be sure to double-check on them after you make the change.

If this does not solve the problem, or you do not have any Excel data sources, please see the rest of our advice below. 

You can also create a new execution package that only executes the excel data sources. It is important that you run it in one thread only and set it to run the standard execution package on success. In the normal execution package you then exclude the excel data sources.

Underlying Problem:

The OLEAUT.dll file is Windows system file.  It is a library for OLE Automation that is used for certain tasks by Microsoft SQL Server.  When this file is missing, corrupt, or inaccessible, TX DWA execution may fail.

It seems to be an issue where excel data sources gets splits out in multiple threads.

Solution:

Do not download a replacement .dll file from a third-party website.  These sites may not be safe.

There are a number of reasons that this this error could occur.  Troubleshooting the issue is an involved process that may require the assistance of your IT staff.  However, there are some steps we can recommend.

Basic checks

1. Log in as your system user and ensure that the OLEAUT32.dll file exists and that you have sufficient permissions to access it.  The default directory for this file is C:\Windows\system32\OLEAUT32.dll.

2. Check that the following registry exists:
folder: HKEY_CLASSES_ROOT\CLSID{00020424-0000-0000-C000-000000000046}\InprocServer32
value: (default) = C:\Windows\system32\oleaut32.dll

Antivirus checks

1. Run a full antivirus scan.  Some viruses will remove system files like OLEAUT32.dll and hide their own files in its place.  

2. Check your antivirus settings - it is also possible for an over-enthusiastic security program to block access to the file on accident.

Repair or restore the file

1. If the problem began after a system, software, or driver change, try reverting to a previous version of the driver or software, or using System Restore to revert to a previous system configuration.

2. If the problem is not related to a system, software, or driver change, ensure that the following are all up to date:

  • System OS
  • SQL Server
  • .NET Framework

3. Restore OLEAUT32.dll from a backup, if you have one. 

4. Open the command prompt and type sfc /scannow to use the System File Checker.  This will attempt to replace or repair missing or corrupted system files. 

5. Download and execute MSVBVM50.EXE from the Microsoft Software Library.  This will allow you to install files for Visual Basic 5.0 runtime, including OLEAUT32.dll.

6. Repair your operating system.  Methods for doing this vary depending on which version of Windows you are using, but all of them have at least one non-destructive repair option. 

Hardware checks

1. Check with your network admin/check your network card and make sure that there haven’t been any network problems that could render the file inaccessible. 

2. Check and repair the file system by running CHKDSK.

3. Check the integrity of your server's RAM.

4. Check to see if other files near the .dll on the disk can be opened. If not, the disc itself may be damaged.

Re-installation options

1. Reinstall MS SQL Server and TX DWA.

2. Reinstall your server's OS.

Note that these last options may be destructive, and should be considered a last resort.  If the problem persists through an OS re-installation, the issue is definitely a hardware problem.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.