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.

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!

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.

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

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.

Support referred to https://portal.microfocus.com/s/article/KM000003871?language=en_US which seems to indicate some DCOM permission problem.

However the setting was correct already.

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.