When doing sets from automation we noticed that from time to time we get failures.
(Code: 0x80131500) Skyline.DataMiner.Net.Exceptions.DataMinerException: Set Parameter ('_512_13':63001/) Failed: 0x80004005
at Skyline.DataMiner.Automation.ScriptDummy.SetParameter(Int32 pid, String idx, Object value)
at Skyline.DataMiner.Automation.ScriptDummy.SetParameter(Int32 pid, Object value)
at Skyline.DataMiner.Automation.Element.SetParameter(Int32 pid, Object value)
at Script.ClearInterface(Engine engine, Element eElement, String sCVlanID, String interface, Boolean vlanPVID)
at Script.Run(Engine engine)
What can be the reason for the set to fail?
Hi Michiel,
I saw a similar questions in the past:
Set Parameter in Automation Script failed
Is the option 'After executing a SET command, check if the read parameter or property has been set to the new value' enabled?
Check the protocol stack, element may busy processing another group.
Hi
Miguel, thanks for your reply.
I would like to know why the system is so slow from time to time, which leads to more than only these errors. It looks like the automation script does not get a response in time to confirm the set has been processed. I would prefer to increase the timeout time instead, otherwise, we need to implement our own validation which could also put extra load on the system to retrieve the parameter’s value for validation.