Hi Dojo,
I’m unable to start DataMiner due to the following error in SLDataMiner.txt:
2026/03/10 18:39:56.920|SLDataMiner|13780|11144|CServiceModule::LaunchDataMiner|INF|-1|Startup Dataminer finished successfully.
2026/03/10 18:39:56.982|SLDataMiner|13780|11144|CServiceModule::RunFunc|CRU|0|Startup DataMiner succeeded in 00h 00m 31s
2026/03/10 18:39:56.989|SLDataMiner.exe 10.5.2521.1448|13780|13076|CIPSettings::Init|ERR|-1|Opening device failed for adapter {E1B7FD5F-7419-11EE-885F-806E6F6E6963} (Software Loopback Interface 1): The system cannot find the file specified. (2)
2026/03/10 18:40:04.091|SLDataMiner|13780|4012|IDataMiner::NotifyDataMiner|ERR|0|Finished [0x00000000000000A5] - NT_WATCHDOG_ELEMENT_STATS by DataMiner with error. (Could not communicate with remote DataMiner (hr = 0x800402B8))
As shown above, the log first indicates a successful startup, but immediately after, we get the adapter error, causing DMA to stop.
I have tried the fix suggested in the docs:
What if I have connection issues after a Failover switch? | DataMiner Docs, but it doesn't resolve the issue.
Additionally, I have:
-
Tested different active and persistent routes.
-
Added the Network Adapter MAC address to
DataMiner.xml.
Unfortunately, none of these steps have worked.
Could someone advise if this issue is familiar, or suggest a way to force DataMiner to bind to the correct NIC?
Thank you in advance.
Kind regards,
Nejra
Hi Nejra,
I don't think the adapter error caused the DMA to stop working.
I have that in my local DMA, and it's running fine.
My best advice is to look into SLErrors to better understand the other errors in the logs. If you can't identify the cause, I recommend reaching out to Techsupport. We'll need a LogCollector package to help you more effectively.
Thanks in advance.
Thank you Luis. I will proceed accordingly.