Faulting application Manager.exe version 24.4.168.0 in C:\Program Files\OmniBack\bin\libcef.dll

After upgrading Data Protector 23.4 to 24.4 yesterday i was able to start Manager.exe, but today I can't, because it's faulting like this:

Faulting application name: Manager.exe, version: 24.4.168.0, time stamp: 0x6721efd8
Faulting module name: libcef.dll, version: 126.2.10.0, time stamp: 0x6675fcf5
Exception code: 0x80000003
Fault offset: 0x00000000013cdff6
Faulting process id: 0x151c
Faulting application start time: 0x01db5067f31f7c36
Faulting application path: C:\Program Files\OmniBack\bin\Manager.exe
Faulting module path: C:\Program Files\OmniBack\bin\libcef.dll
Report Id: f30cd608-5792-4152-b433-2265e2526fe4
Faulting package full name:
Faulting package-relative application ID:

OS is Windows Server 2019 version 1809 (OS Build 17763.6659).

I found out that over night the following updates had been installed:

 KB5043126, KB5048661, 

Anybody else made similar experience? Maybe something went wrong when installing the updates.

Parents Reply Children
  • 0 in reply to   

    Well if it was running once (assuming this was not "by accident"), and then stops to work, I would suspect that something changed "outside" of Data Protector. So it could be some harmful Windows update, or Data Protector has a severe programming error that caused a flip from "working" to "crashing". A good error message is worth its weight in gold ;-)

    Looking at the debug.log (last updated December 16th) it seems there was some problem before the fatal crash already:

    2024-12-16 14:35:45.886 MONITOR.2100.6136 ["/lib/cmn/win32nls.c $Rev$ $Date:: $:":157] 23.4 b196
    FormatMessage() failed with 1813, message #1131 in set 110


    2024-12-16 14:45:20.380 INSTALL_SERVICE.4132.3764 ["/lib/cmn/win32nls.c $Rev$ $Date:: $:":309] 23.4 b187
    CRITICAL: Cannot open default message catalog (LANG=ENU)


    2024-12-16 14:45:21.009 SecLibIpc.4132.3764 ["/lib/cmn/win32nls.c $Rev$ $Date:: $:":309] 23.4 b187
    CRITICAL: Cannot open default message catalog (LANG=ENU)


    2024-12-16 14:47:37.290 SecLibIpc.4132.3764 ["/lib/ipc/ipc.c $Rev$ $Date:: $:":5133] 23.4 b187
    [IpcIPIsLocal] empty_ip
    [install_service]: SetServiceStatus(STOPPED) failed, err=6

    2024-12-16 14:48:31.167 GUICORE.6400.1824 ["/lib/cmn/win32exe.c $Rev$ $Date:: $:":295] 24.4 b168
    Process PID:2212 exited with exception warning 0x800702E4!

    2024-12-16 14:48:31.183 GUICORE.6400.1824 ["/lib/cmn/win32exe.c $Rev$ $Date:: $:":295] 24.4 b168
    Process PID:2212 exited with exception warning 0x800702E4!
  • 0   in reply to   

    The exception warning 0x800702E4 seems to indicate that an operation requires elevated permissions. I can only say that we did at least once release a similar fix. It's not because something external is triggering it (if that's the case in the first place) that it's not a potential problem in our code. With that I'm not saying it is a DP problem, rather that it's worth to be investigated.

    You may also be interested in my Support Tips.

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.