Hi
I was investigating this issue on a Single DMA. To give you some background, the following error in the SLErrors.log appeared after recovering the system from a Ransomware attack:
2023/04/18 00:00:01.508|SLDMS.txt|SLDMS.exe 10.2.2231.1894|19544|8484|CSystem::DoubleCheck|ERR|-1|Not executing midnight sync: local agent has not been fully synchronized yet.
2023/04/18 00:00:01.508|SLDMS.txt|SLDMS.exe 10.2.2231.1894|19544|8484|__DoubleCheck|ERR|-1|DoubleCheck failed. Operation aborted (hr = 0x80004004)
I was wondering if someone from the community has seen this error before.
Hi Melissa,
It is safe to ignore these errors for a standalone DataMiner Agent.
The message/error got introduced in v10.1.6 / 10.1 CU3 / 10.0 CU14 (ref) as a protection to prevent an agent that has not yet completed its full synchronization from being synchronized at midnight.
Standalone agents don’t need this midnight synchronization, as they have no other agents to sync with anyway.
Having the error show up for a standalone agent is wrong and can be raised as a software issue. However, there is no further impact.
A workaround to get rid of the message would be to stop the DataMiner, update DMS.xml to have <DMS synchronized=”true”> and start the agent back up.
For reference: task to prevent this error from showing up: ref 210221
Thaks for the response Wouter…We will implement that change on the system.