Description

This article explains how to fix issue when Warehouse Management System (WMS) has stopped working.

Caused by OLEAUT32.dll failing in Event Viewer.



 

Detail Steps

Solution: 

1. Inform customer IT Team to apply the Windows update as below:

  • Windows update for the following KB must be performed:- VB6-KB924053-x86-ENU.exe


2. After IT Team has done below, check in C:\windows\syswow64 or C:\WINDOWS\SYSTEM32\WOW64 for the OLEAUT32.dll and ensure it's properties details as below:

Server 2008
File version: 6.1.7601.18640
Last Modified: 18/10/2014

Server 2012
File version: 6.2.9200.22435
Last modified: 22/4/2018

Server 2016
File version: 10.0.14393.2273
Last modified: 28/4/2018
Example:
Windows Server 2012 Standard
OLEAUT32.dll details:
Date Modified: 22/4/2019, 4:43pm
File Version/ Product Version: 6.2.9200.22435



3. For WMS V10, contact Datapel Support team and ask to organise WMS Update to version 10.2.178R4 onwards.


Steps to review

Reference: Runtime Errors

(Applicable to servers of all WMS versions)

There are additional configuration options for the WMS operating environment that improve overall system stability.

The compromise is typically that Windows “Security” patches need to be overridden or circumvented by allowing Administrator privilege to the faulting application. Other known precedents include video, input, and RDP device driver incompatibilities between 32bit/64bit operating modes.

The WMS exe operates as a 32bit application – when running on a 64bit environment device drivers have been known to introduce intermittent faults. Legacy component updates are not shipped with the latest versions of Windows Server. In this case the WMS utilises a range of components that have security and environment updates that are not generally distributed with server OS installation. These components may not be at the required version for stable WMS  operation – these components are Microsoft, or third party supplied and not managed by Datapel Systems. A manifest of core components and required versions are listed below.

 

 The following items can be obtained from Datapel Support and must be deployed to the relevant Windows/System folders – for 64bit distributions these must be located within /SysWOW64 folder.

Datapel FTP/Installers/Core/WMS_CoreDependencies_June2019.zip

 

Deployment notes

The msvbvm60.dll virtual machine handles the running of parts of the WMS code base and the deployed VBVM is version 6.0.98.2. This version has been updated to fix small issues with subsequent Windows Operating System releases – the latest version now 6.0.98.32. 

In order to bring all components up-to-date the previous list identifies the latest/recommended versions of all DLLs/OCX components used by the WMS Core application which are Microsoft Operating System dependent.

Note these controls will be found in the C:\Windows\SysWOW64\folder on 64 bit machines - otherwise these will be found in the C:\Windows\System32\ folder. Each has a dependency on COMCAT.DLL which should be at least version 6 and above - for legacy servers can be version 4 and above.

ALL COMPONENTS need to be UNREGISTERED (regsvr32.exe -u) using the existing control and regsvr32.exe AFTER REPLACEMENT VIA copy with Administrator privileges.

ALWAYS leave a backup copy of the original OCX/DLL replaced.


 

Related Information

Runtime Errors