Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    7
  • Subscribers subscribers
    13
  • Views views
    455
  • Users 0 members are here
  • +1 person also asked this people also asked this
Related
Options

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

Ulrich Windl

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.

  • Verified Answer

    +1 in reply to 

    I was able to solve the issue doing the following:

    1. Run csetup from the IS share to set up the GUI. Now Manager.,exe won't crash any more, but is unable to connect (with no helpful error message given)
    2. Do the "omnicc --secure_comm -reconfigure_peer CM" game on the GUI client as administrator, and then "omnicc -secure_comm -configure_peer GUI-client" on the CM (Linux, as root user)

    Then I was able to connect. I don't know what had went wrong before. At that point the GUI client was not listed in the CM's client list, so I imported it.

    To verify, I did a "Check installation", as well as an "Upgrade installation", and then re-ran the manager to verify.

Reply

  • Verified Answer

    +1 in reply to 

    I was able to solve the issue doing the following:

    1. Run csetup from the IS share to set up the GUI. Now Manager.,exe won't crash any more, but is unable to connect (with no helpful error message given)
    2. Do the "omnicc --secure_comm -reconfigure_peer CM" game on the GUI client as administrator, and then "omnicc -secure_comm -configure_peer GUI-client" on the CM (Linux, as root user)

    Then I was able to connect. I don't know what had went wrong before. At that point the GUI client was not listed in the CM's client list, so I imported it.

    To verify, I did a "Check installation", as well as an "Upgrade installation", and then re-ran the manager to verify.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.