This article explains possible reasons why Runtime errors occur and how to resolve them.
If happening 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 due to the windows components we use have stopped working in your remote session, please follow steps below:
1. Log out of your server session completely by use the Start icon and Select Log Off
2. Log back in
3. Check if the error still exist.
4. If the error still exists, restart your machine.
5. Check if the error still exist. and if 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 happening 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
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.
The msvbvm60.dll virtual machine handles the running of parts of the WMS code base and the deployed VBVM is version 220.127.116.11. This version has been updated to fix small issues with subsequent Windows Operating System releases – the latest version now 18.104.22.168.
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.
AppV and other Virtualisation options
In order to truly isolate the application from the operating environment it is recommended to deploy the application using either CITRIX, ThinApp, or AppV technologies should on premise serving be a hard requirement.
If on premise configuration management is still not possible 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 agreement and not accessible by the End User.
Incompatible Device Drivers
There are cases of video, mouse and enhanced keyboard drivers causing system crashes. Most typically the video driver in combination with Remote Desktop Client has been reported as the root cause of run-time errors.
In terms of main WMS register failures during reloading – mouse drivers have also been identified as causing issues while register is loading and “scrolling” is undertaken by the user.
Review the specific client PC’s and connection peripherals for the offending users
We typically find in these cases it is a particular user(s) having the problem – which is normally linked to 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 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 required – 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 it is sometimes a requirement to provide all users Administrator Level right for the WMS application ONLY.
To achieve this, adjust the compatibility settings as shown below:
If problem still 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 occurrences date and time, take a screen shot of all errors on the screen and email firstname.lastname@example.org this can be caused by the following reasons:
Right click on your RDP icon, select properties
Select your performance option and un-tick all except Reconnect if disconnected - do not use auto select.
Connection speed can be improved by also 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 you are access from your PC via RDC, upgrade your software to latest or Microsoft specified compatible version. (IT/Admin to perform action)
Try run as admin mode, set all users option to Run as Admin (IT/Admin to perform action)
Corrupt Windows profile
If only happening to one WMS user create new profile from scratch (IT/Admin to perform action)
switch off for MYOB and WMS (IT/Admin to perform action)
switch to Never Notify (IT/Admin to perform 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 developer of the program causing the issue for any possible solutions. If no solutions are found, we recommend you contact 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 action)
-vbalExplorerBarLib Run-time error '0' in particular uses a file ssubtmr6.dll
Because computer viruses are capable of tampering with the system settings / memory it is possible for a computer virus to generate a runtime error. If you are currently 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 you have all the latest and compatible drivers 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 Security tab
For Cloud WMS, the setting is under Company tab
"Runtime Error 440 : Automation error "
Runtime error 440 is an OLE automation error. This error can be caused by a variety of factors:
- 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 that 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 re-installed. (Please contact email@example.com to reinstall WMS)
Runtime Error reference guide https://msdn.microsoft.com/en-us/library/aa264975(v=vs.60).aspx