Failed To Download Assets For Duplication
Cesar Sergeantson
I have a new MacBook Pro using Monterey 12.5.1 I am trying to duplicate a photo that was originally taken on an iPhone and then exported to the MacBook. When I try to duplicate the photo or export it to my desktop, I get the following message: Failed to download assets for duplication. How do I download assets for duplication?
Does the record link field exist to link the duplicate asset? Duplicate assets are linked to a parent using a record link field. If the record link field used in the setup of the workflow template has been deleted, then asset duplication will fail. Make sure to add the record link field back to DAM. After that, a retry should be successful.
When using the Multiple target asset functionality, the Failure Mode/Copy to function does not allow you to add assets to target analysis during the copy process as expected. Error message:
Using N-Able. I've manually added some devices to a company. Later, the discovery job finds the same device and lists it under discovered assets. Is it possible to merge the already-imported asset with the discovered asset so that I don't have to ignore the discovered asset and cause possible confusion down the road? I've looked into using the NcentralAssetTool.exe, but there isn't really any documentation on the tool itself and the documentation on how to use it is quite limited. Maybe it's possible for a single device to have multiple asset tags? Maybe it's possible to manually set an asset tag on an already-imported asset without breaking it? Any help/insight is appreciated!
You can use any of these methods to upload assets after creating a folder. To create an empty folder, click Create Folder from the toolbar. While Assets Essentials offers a powerful, full-text search functionality, you can also use folders to organize your assets better.
To view a subset of assets based on the upload progress or status, use the filter in the Upload Progress sidebar. The various filters are to display all assets, completed uploads, in-progress uploads, queued assets to be uploaded, paused uploads, duplicate assets, and assets that failed to upload.
Immediately after the assets are uploaded, Assets Essentials processes the assets to generate thumbnail and process metadata. For many assets, the processing takes some time. If do not see a thumbnail and see a processing message on the placeholder thumbnail, check the folder again after a few minutes. During processing, amongst other things, Assets Essentials generates the renditions, adds smart tags, and indexes the asset details for search.
Assets Essentials processes the uploaded assets in near real time and for many supported file types, it generates renditions. Created for images, the renditions are resized versions of the uploaded image. You can download not just the asset but also the renditions to use an appropriate version. You can view all the renditions of an asset when you preview an asset.
If you attempt to upload duplicate assets, the assets are not uploaded until you explicitly confirm the upload. At first, the duplicate assets are marked as failed uploads. To resolve, you can simply create a version, delete and replace the existing assets, or create a duplicate copy by renaming the asset. You can resolve such failures one asset at a time or do it in bulk for all failed duplicates in one go.
This white paper article provides general information and best practices on how to understand, prevent and troubleshoot duplicate assets. Note: This article is primarily intended for CMDB Solution duplicate assets and merges. Most references are therefore regarding these types, not other non-CMDB duplicate assets and merges, which are only briefly discussed.
Other non-CMDB duplicate assets and merge types therefore only briefly covered.
What Are Duplicate Assets and How Are They Caused
The phrase "duplicate assets" refers to when two or more asset records share at least one data class value between them, such as the resource name or serial number. These asset records may or may not refer to the same physical asset. In general, this refers to one of the following:
Duplicate assets can be any asset type but are most often associated with duplicate computer records. Depending on how the computers and their data classes were brought into the Symantec Management Platform often determines how the duplicates were caused. For example, the following are three scenarios where duplicate computers can be caused:
Scenario 1: Duplicate computer names (normal)
Computers that have duplicate resource names are not considered to be an issue because the resource name data class by itself is not required to be unique. These can be created in a variety of ways, such as by the following:
Scenarios 2 and 3: Duplicate unmanaged and managed computer records (normal) and running the Inventory to Asset Synchronization task (normal)
A common business practice is to create unmanaged "staging" computer records before their physical computers are brought into the Symantec Management Platform. Later, their physical computers are integrated with a Symantec Management Agent and create managed computer records. These processes result in one unmanaged computer record and one managed computer record both referring to the same physical computer. The following example demonstrates how duplicate assets can be created by unmanaged and managed computer records. Note: Computer records created by Asset Management Solution, CMDB Solution, Barcode Solution or Data Connector are all considered to be unmanaged records with only CMDB Solution/Asset Management data classes initially. Computer records created by a Symantec Management Agent checking in for the first time are considered to be managed records with only Core data classes initially.
Shared and Duplicate GUIDS
If asset records share the same GUID, or, a GUID is somehow duplicated many times in a table, these become very serious issues. While these could be thought of as duplicate assets, and in fact the Resource Merge Rule can merge duplicate GUIDs, they are seen as a different type of issue and are not otherwise covered in this article. For information on how to troubleshoot these, refer to the following article:
Resolving issues with shared GUIDs
HOWTO49693
How to Find Duplicate Assets
Duplicate assets can be found by a variety of ways, such as when using reports, editing assets, SQL scripts or by searching for data such as for a computer's serial number. Three out of box reports also help find duplicate assets, which can be found under Reports > Service and Asset Management > Merge. These three reports list assets that have duplicate CMDB Solution barcode, serial number and system numbers, respectively.
Another way is attempting to edit an asset that has a unique data class that has an existing duplicate, such as the Serial Number or System Number values. For example:
Example 1: Two (or more) computers have duplicate unique data class values already, which were caused by unknown processes.
This error looks similar to the following:
As the error states, there is another record that already has the same System Number data class value, and therefore, the record being edited, cannot be saved (regardless of the changes made, unless that was to remove/change the System Number to be unique).
Refer to the following article that further discusses this error for additional information about it:
Error "An error occurred saving changes. A resource with a duplicate field already exists in the system." occurs when trying to save a computer
161062
Included as attachments in this article are several SQL scripts that can find duplicate assets. These are:
How to Find Merged Assets
While it is not technically the scope fo this article to answer, sometimes it's useful to see what assets have already been merged. Included as an attachment in this article is a SQL script that can do this, which is "Find CMDB merged assets.txt".
How to Merge Duplicate Assets
Duplicate assets can be resolved in one of three ways: by resolving the conflict by editing or otherwise changing the duplicated shared data class values, by deleting the unwanted duplicate or by merging the duplicates together. It's usually easiest to perform an automatic merge of the duplicates to resolve the issue, of which CMDB Solution provides three tasks (described below) that can perform this.
Merge types under control by the user include a manual merge and several automatic merge tasks, all of which are controlled by CMDB Solution. For automatic merge tasks, however, the user should be very cautious about running these as they can delete records that were not intended to be deleted (from the merge process). For all CMDB merges, the latest record is kept, along with the latest updated data classes from each of the records. Certain resource merge keys can cause the wrong record then to be kept, such as if Resource Name were used. If the oldest is the record to keep, and duplicate names were added later (which can be a normal process in the work environment), the correct old record is deleted and merged in favor of the newest, which may not be what the customer expects. For example both Barcode Solution and Asset Management Solution can receive new computers as a single name, such as "New Computer". If an automatic merge task were ran against Resource Name, all "New Computer" records except the latest, last one, are deleted and merged with it; not at all what should be done as the actual valid assets are now permanently deleted. If this were then performed without understanding this, the user would then find that they have "accidentally" deleted a lot of valid assets, with no way to restore these other than re-receiving them or restoring from a database backup.
CMDB Solution Merges
CMDB Solution merge tasks are found under Manage > Jobs and Tasks > Service and Asset Management > CMDB. Note: For a merge task to work successfully, the target records must contain matching duplicate data class values. For example, if Resource Name is used as the merge key, but no duplicate resource names are found but similarly named ones are (for example, TestPC1, Test PC2), these cannot be merged with a merge rule as there are no actual duplicate data class values.
All CMDB merge types, manual or merge task, always keep the latest record and all of the latest data class values of the records to merge. (With the exception of the manual merge, which the user can control which record and data classes are kept.) For example: New Computer (1) was created on 5/1/2014, and New Computer (2) was created on 7/1/2014. New Computer (2) would be kept, and (1) would be deleted. If (1) had data classes that (2) didn't have, they are copied over to (2). Or likewise, if (1) had data classes that were filled out that (2) had, but were more recent, these will overwrite (2)'s as they are newer.
The following are merges that are controlled by CMDB Solution: