After assigning a barcode to a computer, the barcode value disappears later.
In general, once a barcode value is assigned to a computer, it should not disappear later. The following instructions provide comprehensive troubleshooting on how to find out why this is happening. Note: This article discusses a computer's Barcode field, but this is also applicable to any resource type that has a Barcode field as well.
Part 1: Check if the Barcode value is present or not.
Check the computer record that has a missing barcode value to verify if it is actually present or not. This is performed by editing the computer that has a missing barcode value and also by checking its Resource Change History. Also check if the Notification Server is in a hierarchy or uses stand-alone replication rules. The following instructions describe how to perform these checks.
Part 2: How to troubleshoot Barcode changes.
If Part 1 proved that a barcode value was present but is now missing, troubleshoot the process(es) that add a barcode value to computers. The following instructions describe how to perform this troubleshooting.
Review if the barcode value was added to the correct computer and that the value added was the correct barcode. It may be that this was added to the wrong computer by accident or that the barcode value was added incorrectly. Also, ensure that the barcode value was added to the Barcode field, not to another field such as the Serial Number or System Number fields.
Data Connector Import Rule Changes
Review any Data Connector import rules, and also CMDB rules, that may be importing or changing barcode values, specifically, any that are mentioned in the Resource Change History of the affected computer. If these are making changes, next ensure that the changes were applied correct as the user expects. If not, perform troubleshooting on the specific rule.
Barcode Solution Sync Changes
If the Barcode Solution synchronization profile used is set to require that the Barcode Manager approve changes, review the approval process.
Part 3: How to perform advanced troubleshooting.
Normally, Parts 1 and 2 should be sufficient to find and troubleshoot issues setting barcode values. If not, more in-depth troubleshooting needs to next be performed.
Barcode Solution Sync Changes
If Barcode Solution is used to set barcode values, ensure that the Notification Server has a stable, fast environment. Poor performance by the server can result in changes not being processed, which could then impact the the Barcode field failing to update. Information about this can be found in the following articles:
Barcode sync fails to add new assets
Using Barcode results in poor Console performance or hangs the Console
Merges Have Taken Place
Review if merges are occurring, as this may be changing the barcode value. A merge should not normally be causing the barcode value to be removed. This can occur, however, if the record to keep has recently had its barcode value removed. The resulting merged record will then have no barcode value, even though the old record did have one. If merges are being ran or scheduled, if these are suspected to be removing barcode values, disable these from being ran. If no other barcode values are later removed, then these were the likely cause. Note: A merge does not record its changes to an asset's Resource Change History.
Duplicate Computer Names and/or GUIDS are Present in the Database
If duplicate computer names and/or GUIDS are present, both of which are not supported, this can result in severe issues, such as data corruption to fields such as the Barcode. Resolve any duplicate names and/or GUIDs to prevent data corruption or field loss. Information about this can be found in the following article:
Issues occur when using duplicate computer names and/or GUIDs
Review the Database for References to the Barcode Value or the Change
As mentioned earlier, normally most changes to a barcode value is recorded in the asset's Resource Change History. There are certain SQL tables that can also provide similar information. The following SQL scripts provide examples of how to display this information. Note: When a barcode value is added or changed, records are added or updated to both the Inv_Barcode and InvHist_Barcode table. If an asset with a barcode value is deleted or merged, both tables have their record deleted referencing the barcode value.
-- Check the Barcode table.
ORDER BY 3
-- Check the Barcode History table.
ORDER BY 6
-- Check the Evt_NS_Item_Management for changes to an asset by a user or a task.
ORDER BY 3 DESC
Custom Data Classes and the Resource Change History
As discussed, nearly all changes to an asset are recorded into its Resource Change History. This also includes the editing of custom data classes (which is not necessarily related to the topic of this article).
Computer's Manufacturer, Model, Serial Number or System Number are incorrect
Random assets suddenly disappear from the Symantec Management Platform Console
Asset pick list windows take a long time to populate, times out or doesn't populate at all
What reports offer a historical view of asset changes or deletions?
After upgrading the Symantec Management Platform 7.1 to 7.5, associations in resources are then missing
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.