Hi community,
We are working with a connector that interacts with DataMiners Scheduler module.
One of the actions performed in the connector is deleting a Task with the SetSchedulerInfoMessage SLNET call as shown in the following image:
We have tested the connector in multiple test environments and the Delete feature works.
But on a production environment we see the following error after the call is sent:
Exception thrown:
(Code: 0x80004005) Skyline.DataMiner.Net.Exceptions.DataMinerCOMException: Unspecified error
---> System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.
Does somebody know what this DataMinerCOMException means?
Hi,
There are various reasons that could cause the E_FAIL exception.
Possibilities are:
- SLScheduler has no connection with the SLXML process
- SLScheduler has no connection with the SLDataMiner process
- Task ID does not exist
- Task could not be removed from MS Task Scheduler
Most likely the task ID could not be found and does not exist (value that is past with the 'Info' field).
To know the real root cause, the "SLScheduler" log file can be consulted, which will contain the failure reason. Note that the log level needs to be increased to the highest level to log everything, as not all possible reasons will be logged under the default level.
Regards,
A scheduled task gets executed by the Windows Task Scheduler present on the DMA. These task IDs are present under C:/ Skyline DataMiner / Schedule.xml. This is a file that is not synchronized. In other words task ID 1 on DMA A could mean "Execute Provision", task ID 1 on DMA B will be a different task "Send Report", so when asking to delete task 1 and this is requested on a different DMA then a task will be deleted that was not expected. My advise would be to take a look at the Schedule.xml to the <Task id attribute. When comparing the Schedule.xml between the different DMAs in the cluster, the content will be different, which is normal and expected.
Hi Laurens,
Thank you for your response.
We validated the issue using the SLScheduler log, and the Task ID is reported as "not existing". We also replicated the SLNET call in the Client Test Tool and encountered the same COM error.
However, we noticed something unusual:
– When we perform an SLNET call to retrieve all available tasks, the task with the ID we’re trying to delete is present in the list, indicating that it does indeed exist.
Additionally, we observed the following behavior:
– When performing the same task deletion in the Client Test Tool but specifying a different DMA agent from the cluster, the deletion succeeded.
– We tested this several more times, but the deletion with other agents doesn’t consistently succeed.
What do you consider should be could be the issue?