OMSA Crash

Hallo,

I have running a Windows Server 2016 HyperV instance on a PowerEdge R710 server.

There are 2 VMs running on that HyperV, both also Windows Server 2016 Standard. One of these VMs is a DC. The HyperV is not in that domain, but in the same network

I had installed OpenManage Server Administrator on the HyperV for a while now.

Today I noticed, that I cannot achieve any Information via OMSA. The service is reachable via browser, but I cannot see any information about the hardware, e.g. Storage Controller, RAIDs, ...

Then, I started searching and saw the following logs (sorry logs are in German):

Name der fehlerhaften Anwendung: dsm_sa_datamgr64.exe, Version: 8.5.0.2372, Zeitstempel: 0x5888eb12
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.14393.479, Zeitstempel: 0x5825887f
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000f8283
ID des fehlerhaften Prozesses: 0x2fa8
Startzeit der fehlerhaften Anwendung: 0x01d2e52134b65a73
Pfad der fehlerhaften Anwendung: C:\Program Files\Dell\SysMgt\dataeng\bin\dsm_sa_datamgr64.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: d071294e-7b3e-4dd6-8ad3-16c55256afac
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Obviously the DataService (sorry I do not have the exact service name) could not be started.

I already removed OMSA with the setup-enclosed tool. Besides, I have updated to the latest version 8.5 A00 (OM-DRAC-Dell-Web-WINX64-8.5.0-2372_A00). But the error is unfortunately the same.

During the installation (prerequisites check) of the new OSMA version I get the following warning

The installer has detected that the HTTPS listener is not configured for Windows Remote Management. You can either configure the HTTPS listener before installing Remote Enablement, or install Remote Enablement now by selecting the "Custom" installation screen and configure the HTTPS listener later. See the "Remote Enablement Requirements" section in the Server Administrator Installation Guide for information on configuring the HTTPS listener. Note: Remote Enablement is required to manage this system from a remote Server Administrator Web Server and is applicable only for those systems that support Server Instrumentation. Click here to configure HTTPS Listener for Windows Remote Management.

I clicked on the link at the end in order to fix that problem, but it does not help. I have assured, that the Remote Management is activated on the HyperV - anyway, the message still pops up.

Does anyone have an idea, what's causing this problem?

thanks in advance.