ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Getting error 'The specified resource got linked to another resource' when User policies are requested by client machines
Article ID: 161981
IT Management Suite
Customer started to get error messages in the NS logs referring to Policy requests failing. The resources mentioned were Users, so these policy requests are actually User based policies.
Policy request failed from: 22.214.171.124
The specified resource got linked to another resource:
[Altiris.NS.Exceptions.NSComException @ Altiris.NS]
at Altiris.NS.AgentManagement.PolicyRequest.LookupResources(ParseRequestResult result)
at Altiris.NS.AgentManagement.PolicyRequest.GetPolicies(String request, Boolean bCompress, String& agentPoliciesXml)
at Altiris.Web.NS.Agent.GetClientPoliciesHandler.ProcessRequest(HttpContext context)
In this particular case the issue is caused by the way the customer is bringing those users via a Data Connector import rule. His Data Connector import rule imports a csv file that contains just the user names, no domain info, and other details about the users. Bringing the users without a domain reference is adding a new entry in ResourceKey table, so there are 2 entries with unique GUIDs on this table for the same user. You can validate this by running the following query (just replace the GUIDs with the ones from the error message):
select vi.Name, vi.ResourceTypeGuid, rk.* from resourcekey rk
join vRM_Resource_Item vi on vi.Guid = rk.ResourceGuid
where rk.ResourceGuid in (
In this case you may notice entries like JohnDoe and JohnDoe.Beta for example.
The CMDB merge rules don't work because it needs to have name.domain references and one of the entries just have name on it.
This is not a defect but an issue with the way the Data Connector import rule has been setup and the data that is brought.
The simple way to fix this issue is to make sure the Data Connector Import Rule has the right Resource lookup key setup: "User UserId/Domain". Also that the data imported has a name and a domain entry for each user.
Then the CMDB "Duplicate User Merge" task (under Manage>Jobs and Tasks>System Jobs and Tasks>Service and Asset Management>CMDB) should take care of the issue.
If for some reason you can't add the proper domain reference for the users been imported, please import into your SMP the following files:
"Users with Duplicate ResourceKey (name.domain).xml". This report should show you what user resources have this problem
"Updating Inv_Global_Windows_Users.xml". This task runs a SQL query that should identify the user resources that need to be fixed and updates the records of them in the "Inv_Global_Windows_Users" table so the proper merge can be done. Depending how frequently the Data Connector import occurs, it is when this task needs to run. Usually right after the Data Connector Import occurs, then run this task.
Users with Duplicate ResourceKey (name.domain).xmlget_app