This means that the role running the decommission does not have permission to delete a component associated w/ the server object.
I believe we are providing a fix for this behavior in a future version of bsa, and support should have a workaround for this – please open a ticket w/ support for this.
Thanks Bill for the explanation, today morning I encountered the same error.
Thanks Bill, but the user I am using for the decommissioning is the admin user with BLAdmins Role. Is there any other reasons due to which the component access is denied?
Yes, BLAdmins does not have the Delete permission on the component. BLAdmins must be explicitly granted permissions on objects just like every other role. The only implicit permission that it has is a Read on all objects. it's possible to create objects that BLAdmins has no permission on, other than to read.