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
  • 0  

    I can only see 1 similar issue which was fixed before 24.4 was released. If it is still seen then it would be good to open a support case.

    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.

  • 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.

  • 0 in reply to   

    I opened a support case with high priority. Once I know what the issue was, Ill update this thread.

  • 0 in reply to 

    When trying to re-install the GUI (i.e.: first uninstall the software, then re-install it, I got another mysterious error message:

    [Critical] [110:1025] Cannot connect the Data Protector bootstrap service on client host-name-1:
    IPC Cannot Connect
    System error: [138] The system tried to join a drive to a directory on a joined drive.

    Examining Event Viewer I found that msiexec crashed with another error, but the interesting entry before was:

    Beginning a Windows Installer transaction: \\host-name-2\Omniback\x8664\Data Protector 24.4.msi. Client Process Id: 4412.

    When trying to access that "Data" directory, I found that it does not exist any more.

Reply
  • 0 in reply to 

    When trying to re-install the GUI (i.e.: first uninstall the software, then re-install it, I got another mysterious error message:

    [Critical] [110:1025] Cannot connect the Data Protector bootstrap service on client host-name-1:
    IPC Cannot Connect
    System error: [138] The system tried to join a drive to a directory on a joined drive.

    Examining Event Viewer I found that msiexec crashed with another error, but the interesting entry before was:

    Beginning a Windows Installer transaction: \\host-name-2\Omniback\x8664\Data Protector 24.4.msi. Client Process Id: 4412.

    When trying to access that "Data" directory, I found that it does not exist any more.

Children