Seen in the Management Platform Server logs: 'The specified host resource has been blacklisted'
Attempt to save messaging resource with GUID <GUID code here> has been blocked by the Host Resource Blacklist..
The GUID that is assigned to the agent has been added to the AgentBlacklist table and is being blocked to prevent corrupted data from entering the database.
Clear the Agent Blacklist table by following these steps
Run the following query against the database to get a list of all agents being blacklisted
SELECT vi.name, ab.guid FROM agentblacklist ab JOIN vitem vi on vi.guid = ab.guid
Do one of the following:
Remove just the computer(s) you are interested in:
DELETE FROM agentblacklist WHERE guid ='<GUID>
<GUID> with the guid assigned to the computer from the list above
Empty the table completely:
TRUNCATE TABLE agentblacklist
In some cases this is only a temporary solution as there is a deeper issue causing the agent to be added to the agentblacklist table in the first place. If this deeper issue is not addressed the agent will eventually be added to the table again and resume being blocked.
The most common reasons for an agent to be added is that there are multiple resources reporting with the same GUID a condition known as Shared GUID. This condition is most commonly caused by systems being cloned with the Symantec Management Agent (SMA) already installed. When cloning systems either remove the SMA prior to cloning, or use a program like Microsoft's SysPrep to remove the SMA's GUID from the image.