Resource Manager errors with duplicate right-click Items and Altiris 7.5 SP1

When we upgraded our production SMP server from 7.5HF2 to 7.5SP1 we noticed a lot of errors sloshing around our event logs in the days that followed,

1. Access Denied: No Permission to view task history
2. Unhandled Exception: An entry with the same key already exists
3. Unable to create menu item as there due to an XML schema error. An entry with the same key already exists

The first error initially dominated the logs (occuring every few seconds) and then it eased, becoming less frequent (perhaps hourly) and sporadic.

The second and third errors always occured together and only started appearing once the techs started using the console following the upgrade. It turned out that these two errors conincided with a broken resource manager. When console users double-clicked a computer object in the console this screen appeared,

So not very pretty. This error occured even for Symantec Administrators and, as stated above, coincided perfectly with errors 2 and 3 above in the event logs.

After chatting to Altiris Support and uploading my logs and a profiler dump, it turns out that the second two errors were known issues with HF4 (TECH215778: SMP 7.5 HF4 - Error while opening resource manager for User or computer resources). The query in that tech article didn't help locate the issue so I wrote one that might help,

select Name,MyCount from 
(select COUNT(*) as MyCount,Name from vItem
 where ClassGuid='AD07C90E-BFB5-4C7E-8F26-B2A57574EC03'
group by Name) xxx
where MyCount>1

This query searches the editable item actions (class type Altiris.NS.EditableItemAction.EditableResourceItemAction) and sees if any have the same name. And indeed it found the duplicate names and resolved them. With that change, those last two errors vanished and Resource Manager popped back into life.

As an aside, this is a pain as we wanted to have our right-click actions grouped in folders according to role for increased visibility of each roles items. Now we can't do that so ultimately that means a re-think.

As for the first error.... still working on it...