Could be we hit following issue:
https://gitlab.gnome.org/GNOME/libxml2/-/issues/638

The behavior was introduced by
https://gitlab.gnome.org/GNOME/libxml2/-/commit/bbd918b2e7e1b1a81a050f863b7f4802313b565e
to fix:
https://gitlab.gnome.org/GNOME/libxml2/-/issues/122

@pgajdos i don't understand how to solve my problem

If I am right and the issue you are seeing is the one described in upstream issue 638 linked in my comment, then I guess omreport devs should fix their code to work with libxml2 2.12. The temporary workaround could be to downgrade to libxml2 2.10.

I reported it to Dell support, I hope they will release an update :)

Maybe I should explicitly ask, whether omreport devs could outline the course of action, if possible. Otherwise people would be stuck with libxml2 2.10.

:) Nice coincidence. Thank you!

@pgajdos​ I got a respons:

"Thank you for the information, I verified the behavior of the command in the installed system with our older department. Unfortunately, such behavior is normal due to the lack of compatibility of the system with the server. Currently, there is no solution to the given problem, you have to wait for newer versions of OME or for the system to be added as compatible with the server."

Thanks @raftro for letting me know.