This article explains possible reasons why Runtime errors occur and how to resolve them.
If happens when loading software after a run time error
When WMS produces a ‘Runtime error’ and exits, it may fail to start and show a runtime message again because the windows components we use have stopped working in your remote session. Please follow the steps below:
1. Log out of your server session entirely by using the Start icon and selecting Log Off
2. Log back in
3. Check if the error still exists.
4. If the error still exists, restart your machine.
5. Check if the error still exists. And if it still exists, review your Terminal Services colour setting and ensure it is set to 16-bit full colour or higher and retry.
6. Log back in.
7. If the error is not resolved, please contact Datapel Support.
***Reminder: Please don’t close/log off via clicking X or Start icon - Disconnect as this will not reset your windows session!
If happens every time/multiple times per day when loading software
Review your Terminal Services colour setting and ensure it is set to 16-bit full colour or higher, and retry.
Steps to review
Additional configuration options for the WMS operating environment improve overall system stability.
The compromise is typical 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. In addition, legacy component updates are not shipped with the latest versions of Windows Server. In this case, the WMS utilises a range of components with 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.
The msvbvm60.dll virtual machine handles the running of parts of the WMS code base, and the deployed VBVM is version 126.96.36.199. This version has been updated to fix minor issues with subsequent Windows Operating System releases – the latest version is now 188.8.131.52.
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 depends 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.
AppV and other Virtualisation options
To truly isolate the application from the operating environment, deploying the application using CITRIX, ThinApp, or AppV technologies should be on-premise, serving as a hard requirement.
Suppose on-premise configuration management is still not possible. In that case, a “VIRTUALBOX” can be installed under special circumstances to provide a local “cloud” version of the WMS application – fully isolating the operating system from external influences. The virtual server is configured and maintained by Datapel Systems under the agreement and not accessible by the End User.
Incompatible Device Drivers
There are video, mouse and enhanced keyboard drivers causing system crashes. However, most typically, the video driver combined with Remote Desktop Client has been reported as the root cause of runtime errors.
In terms of main WMS register failures during reloading – mouse drivers have also been identified as causing issues while the register is loading and the user undertakes “scrolling”.
Review the specific client PCs and connected peripherals for the offending users
In these cases, we typically find a particular user(s) having the problem – which is usually linked to a similar workflow or similar Client PC setup. Review related drivers – push back to “vanilla” drivers where possible / remove non-standard HW where possible. Review for 3 – 4 days to see if the situation improved. Datapel to check “SUPERSCAN” mode is disabled in PREFS.xml – DATAPEL to check RunAsHighPriority is DISABLED.
Set App Setting to run at elevated privilege (e.g. Administrator) just for the WMS application – required for all users – please make this a global setting. This may require a change to the WMS.EXE.MANIFEST file – You can go ahead and change this if needed – please keep a backup of the original version. Review for 3 – 4 days.
Further to the overall strategy of providing a stable environment using the standard windows operating system, giving all users Administrator Level right for the WMS application ONLY is sometimes required.
To achieve this, adjust the compatibility settings as shown below:
If the problem persists, discuss options for application Virtualisation to remove Operating System dependencies/environmental system factors and replan Application deployment. (between 1 – 2 weeks)
If Runtime error happening intermittently while using software
Note each occurrence's date and time, take a screenshot of all errors on the screen and email email@example.com. The following reasons can cause this:
Right-click on your RDP icon, select properties
Select your performance option and untick all except Reconnect if disconnected - do not use auto select.
Connection speed can be improved by selecting Persistent bitmap caching if you find the above setting causes speed issues.
Out of Date or Incompatible version of MSTSC.exe (RDC/RDP software)
If your WMS is installed on a server and accessing your PC via RDC, upgrade your software to the latest or Microsoft specified compatible version. (IT/Admin to perform the action)
Try run as admin mode, set all users option to Run as Admin (IT/Admin to perform the action)
Corrupt Windows profile
If only happening to one WMS user, create a new profile from scratch (IT/Admin to perform the action)
switch off for MYOB and WMS (IT/Admin to perform the action)
switch to Never Notify (IT/Admin to perform the action)
A Component or dependent not registered correctly
Re-install the application in administrator mode (Run as Administrator) (Datapel Support to Assist)
It is possible that you may be encountering a hardware/memory-related issue. We recommend that you first contact the program developer causing the issue for any possible solutions. If no solutions are found, we recommend contacting the computer or motherboard manufacturer for additional recommendations and/or service.
It is important that the Datapel folder contents, including ssubtmr6.dll, be put on the safe list or the WMS itself kept out of the scan list. (IT/Admin to perform the action)
-vbalExplorerBarLib Run-time error '0' in particular uses a file ssubtmr6.dll
Because computer viruses can tamper with the system settings/memory, a computer virus can generate a runtime error. If you are running a virus protection program on your computer, ensure it has the latest updated patch or .dat file.
Windows screen / mouse / Device add-ons
Disable all non-STD features and add-ons for USB/serial port devices
Driver incompatibility for Devices, Mouse and Keyboard etc
Check that all the latest and compatible drivers are installed for all hardware and devices.
“Runtime Error 5: Invalid Procedure call or argument”
Refer to Datapel Support - this error should reoccur each time you perform a specific entry such as a particular sale or action within the WMS and will need to be reviewed by a support member visually while you process the action.
An argument probably exceeds the range of permitted values. (overflow error)
Invalid procedure call or argument
Check if the WMS has this Preferences setup “Logout Inactive User activated.”
Tools > Preferences > Security > Activate the option to 15 minutes and see if the error occurs again.
For WMS, the setting is under the Security tab.
For Cloud WMS, the setting is under the Company tab.
“Runtime Error 44.0: Automation error”
Runtime error 440 is an OLE automation error. A variety of factors can cause this error:
Corrupt download or incomplete installation of Windows Operating System software.
Corruption in Windows registry from a recent Windows Operating System-related software change (install or uninstall).
Virus or malware infection has corrupted Windows system files or Windows Operating System-related program files.
Another program maliciously or mistakenly deleted Windows Operating System-related files.
Tried everything on this list?
If the above does not work and fails again, WMS may need to be re-installed. (Please get in touch with firstname.lastname@example.org to reinstall WMS)
Runtime Error reference guide https://msdn.microsoft.com/en-us/library/aa264975(v=vs.60).aspx