In an automation script we already had a few times that a GetParameter call failed with error code: 0x80004005
Get Parameter (‘_22818_1’:530/) Failed: 0x80004005
We cannot reproduce the issue (only happens a few times a month), and couldn’t find the root cause. All agents and elements were active. No strange things could be found in the information events, except that the GetParameter has failed.
What are the possible causes for error code 0x80004005? Can this occur when something happens during network communication between the two DMAs?
0x80004005 is a very generic error code, it might as well say “computer says no”, without any additional explanation.
Not sure about it, but I would think 1 of the involved SL processes was blocked or frozen for a second. If this is the case, then it won’t be easy to investigate.
Possible ways to move forward:
- If allowed, increase log level to 5, but note that some SL* log files could get overwritten quickly (ie SLNet).
- If this is critical, then you could also try to add a try-catch on that GetParameter, if it fails, then take the memdumps + pendingCalls for that element. (We already have scripts for this, but might need some changes)
Hi Tom,
Is it possible that you try to get a table parameter without specifying a valid index?
No it’s a standalone parameter and all IDs are correct. Right before and after the get that fails, other gets on the same parameter succeed.