Hi everyone,
I'm encountering an issue with a QAction failure on a specific element and was hoping for some guidance.
When attempting to run a QAction, the process consistently fails with the error code 0x8004022D. Checking the logs, I see a preceding error indicating that the assembly type could not be found.
2026/05/12 09:19:52.011|SLManagedScripting.exe|ManagedInterop|ERR|-1|100|Could not find assembly type (QAction)
2026/05/12 09:19:52.011|SLProtocol - 12008|8552|CQAction::Run|ERR|-1|QAction [15] triggered by [pid=2500/idx=-1/pk=/user=] failed. (0x8004022D)
I've found a previous community post regarding similar error codes (0x8004022D and 0x800402A4) and followed the suggestions there, but unfortunately, it hasn't resolved the issue in my case.
DataMiner (10.5.2.0-15384)
Hi Tarik,
The "Could not find assembly type (QAction)" message usually points more to an assembly loading/resolution problem than to the QAction logic itself.
Also worth checking:
- was the connector recently upgraded?
- were QAction namespaces/class names changed?
- does creating a fresh element with the same protocol reproduce the issue?
If a newly created element works fine, that would strongly suggest element-specific cached state rather than a protocol issue.
Kind regards,