Asset Management Suite

Hi,

after upgrading from 7.1 to 7.5 my customer is not able to merge assets anymore.

"Merge failed.The caller ('USERNAME') does not have one or more of the specified permissions on the specified items."
 
Nothing in the logs. :(

How can this error be debugged, if nothing is in the logs? (The same btw if the customer adds an asset to an organizational group)
When I do it with Symantec Administrator permissions it works, of course.

I appreciate any help on this!

Best regards,

Andreas

Are they using a default role (if so, which one?) or a custom role?

It is a custom Role, that worked fine in 7.1.

Hi,

in the errormessage you mentioned should be the guid of the object where the security rights are missing. You have to find out which object this is (eg. Item Browser in the Log Viewer) and then go ahead and set at least read or write to that Object for your custom role with the security manager.

If you still have problems resolving that issue, just send me an email.

Deutsch wäre kein Problem :-)

Regards

mafoe

Hi,

I am currently on the phone with Symantec Support about this. (and a few other problems).

The problem is, that the log viewer/item browser is not showing the dataclasses where the permissions are missing.

As soon this problem is resolved, I'll write the solution down here.

Regards,

Andreas

I ran into a similar problem and found inheritance changed from 7.1 to 7.5.  Some permission you may expect to be inherited are no longer in inherited.  The change took place in 7.5 and 7.1 SP2 MP1.1 v8.  If I recall correctly there is no inheritance on the Contact Types or Software License folder under Resource Type.  You'll also find the same situation with Contract related folders in Data Classes and Resource Associations.

Hope that helps.

As the time Symantec Support solved two other issues with permissions, asset merging is now magically working.

We found the following:

If you want to be able to put assets in organizational views, one must have all system permissions, especially "change permissions", which I never thought of and all ressource permissions for the source and destination organizational group.

The second: If you want to see CMDB Functions->Set Asset Status for an asset, one must have the "delete" permission on that object.

Maybe by accident, we also repaired the asset merging with that, too. The other possible idea is, that we currently don't have an asset with dataclasses that throw the error and we will run in the problems again with other assets.

To prevent a user actually to use the "delete" permission, I removed all permissions for the "Delete" from right click menu.

Best regards,

Andreas