Hey Jamie,

There is little information to give a full answer, but we can give some information that might help investigation.

This type of alarm gets thrown when by SLDataMiner when it has to handle an alarm that is not generated by an element itself. For examples alarms from Services, Redundancy groups, Correlation, …

SLDataMiner tries to forward these alarms to SLElement so they can be linked to the necessary elements. SLElement performs some sanity checks (correct format, existing PID,…) if these fail it will throw this error.

So the advise here would be to check the SLElement logging to see if there is any indication there as to why it failed.

SLDataMiner should also log the entire alarmdata right below the logline you posted. The format might be a little complex. But can be though of as the following.
~ 0 [data (Ignore)] ~ 1 [data (Ignore)] ~ 2 [The user/Owner of the alarm] ~ 3 [Alarm data]

Under the alarm data position ~ 0 should give the sourceModule of the alarm (Values can be found in the help), Position ~ 8 and ~ 9  should be the target ElementID and the target ParameterID for the alarm and finally Position 4 should contain the value of the alarm.

Hope this helps in tracking down the source of the issue.