Skip to content

Error 114 with GUIUTL32.LBR\ in Deferred Processing

Release Date: 04/09/2018

Q - We are receiving Error 114 in Defer Processing 2 - 3 times a week with the following messages:
    Executiion error : file 'GUIUTL32.LBR\
    error code: 114, pc=EE, call=4, seg=4
    (Signal 11)
See sample screen below:

Please advise how to resolve this problem.

A - This particular program has not been changed since 1999.  We believe the reason this started to happen is related to the OS.  There was something changed at the OS level to cause this.  Initially, we were going to add additional logging logic in Deferred Processing so we could trap this error and hopefully further isolate this problem.  Later on, we were advised by the user that this problem was resolved on their side.  We asked for more details on how how they resolved it.  Here is their response:

"It looks like the issue is resolved. I doubt this will ever be an issue for you in the future, but in case it is, the situation is not easy to identify at first.

It took a while to put all of the individual benign innocuous pieces of the puzzle together, but once I did, the light went off.

We had some back end storage issues that caused a slight delay in our backend IOPS for our VMware infrastructure. Our overall IOPS was running slower than normal (sorry, no real world numbers for comparison). Ever so slightly, that end users were noticing very little in performance issues. Most issues that crept up were crash issues, of various nature. I finally realized this issue might be the culprit for the EL700 night processing to fail. It turns out it was.

The hard part for this is that most everything ran nearly as well as normal.

Our virtual storage platform was running in degraded mode, meaning all IO storage calls for everything on sight, was being run off from one of the two available storage nodes."

Just as an FYI, this user is running on VMWare Virtual Workstation and Windows 7 OS environment.


Feedback and Knowledge Base