search cancel

Error "A server error occurred: Failed to get Resource Types for synchronization." occurs when trying to synchronize assets using Barcode


Article ID: 157321


Updated On:


Symantec Products


When trying to synchronize assets using Barcode, the error "A server error occurred: Failed to get Resource Types for synchronization." occurs. Previously, this may have worked.

From the Altiris logs before the Barcode sync occurs:

<event date="<date time>" severity="1" hostName="<host name>" source="Altiris.NS.ItemManagement.Item.GetInvariantName" module="w3wp.exe" process="w3wp" pid="<pid ID>" thread="<thread ID>" tickCount="<tick count>"><![CDATA[The specified GUID does not refer to a item (GUID: {<problem guid>})


An exception occurred in Altiris.Barcode.Sychronization.Action: Failed to get Resource Types for synchronization. Failed to get Resource Type (Fixed Asset Status Resource Type), spBarcodeGetEditableResourceAssociations expects parameter @AssocTypes, which was not supplied.


Source: Altiris.Barcode.Diagnostics.Logging.Logger.WriteException
Description: Application exception in Synchronization\GetResourceType
System.NullReferenceException: Object reference not set to an instance of an object.




This is known to happen for several different reasons. Depending on the error found in the Altiris logs, apply one of the following solutions.

Issue: User's security role has insufficient permissions
Solution: If the user is only in the Barcode Users security role, reset Barcode security by following the instructions from the following article:

How to reset the Barcode User Security

If resetting Barcode security cannot be performed for fails, a workaround is to add the user to the CMDB Managers role, in addition to being in the Barcode Users role. Information on this can be found here:

Unable to download or synchronize Barcode assets while logged in as a Barcode User

Issue: Corrupted security role.
Solution: Remove users from the corrupted security role, then re-add them.

  1. Determine which Altiris Security Role is the cause. Run the following SQL query in SQL Server Management Studio to find this:

    USE Symantec_CMDB
    SELECT *
    FROM Item
    WHERE Guid = '<problem guid>'

    Where "<problem guid>' is the guid from the Altiris log error. For example,

    USE Symantec_CMDB
    SELECT *
    FROM Item
    WHERE Guid = '70ab2b14-6996-435f-a665-6a2e57da818b'
  2. Review the value of the Name column from the returned record. From the above example, this is Symantec Monitor Administrators, indicating that Monitor Solution is involved with the issue.
  3. In a Symantec Management Platform Console, click on the Settings button > Security > Account Management.
  4. Click on Roles.
  5. Click on the role mentioned from step 2.
  6. Temporarily or permanently remove all members from the role, from its Member tab. Note: At the user's discretion, users can be re-added one at a time back to the role they failed in, and then the Barcode sync retried until specific ones are found to be the cause.
  7. Click on the "Save changes" button.
  8. In Barcode, attempt another sync. The issue should now be resolved. Note: Barcode Solution is not the cause of the issue and therefore their support team is unable to further troubleshoot Core or other Solution's security role-related issues. To further troubleshoot why, please contact the Symantec Management Platform Technical Support team, who work with security role-related issues, or contact the specific solution's team, in the above example, this would be the Monitor Solution Technical Support.

Issue: Corrupted custom data class, resource or record.
Solution: If the error refers to specific custom data class, custom resource type or record, these may have become corrupted. It may then be necessary to manually delete these to resolve the issue. As this may not be desired, please contact Technical Support for additional information regarding this variation of the issue.

Issue: Stored procedure spBarcodeGetEditableResourceAssociations needs to be updated. If "spBarcodeGetEditableResourceAssociations expects parameter @AssocTypes, which was not supplied." appears in the log, this is the cause.
Solution: Update the spBarcodeGetEditableResourceAssociations stored procedure in SQL.

Note: The user may need to have their DBA assist with the following if they do not have permission to change stored procedures.

  1. On the SQL Server, open the Microsoft SQL Server Management Studio.
  2. In the Object Explorer window, click to open the Databases folders > Symantec_CMDB > Programmability > Stored Procedure. Note: If the name of the Altiris database is not the default of Symantec_CMDB, click to open the correct folder instead.
  3. Locate and click on the stored procedure spBarcodeGetEditableResourceAssociations.
  4. Right click on the stored procedure spBarcodeGetEditableResourceAssociations and choose Rename.
  5. Change the name of the stored procedure, such as to spBarcodeGetEditableResourceAssociations-OLD.
  6. Run the attached stored procedure, which will create a new spBarcodeGetEditableResourceAssociations.
  7. In Barcode, attempt another sync. The issue should now be resolved.

Issue: NSEs are failing to process. This may cause syncs to fail seemingly randomly.
Solution: Resolve performance issues of the Core console by correcting failing NSEs. The following article describes this in more detail:

Barcode sync fails to add new assets

Or, add a new IIS app pool for Barcode to help with this. The issue may then occur far less as this is not addressing the NSE issue. The following article describes this in more detail:

Using Barcode results in poor Console performance or hangs the Console

Issue: Barcode license issues exist, and/or, there are too many resources attempting to be used on the handheld device. (Unconfirmed.)
Solution: (1) Verify that there are available license by reviewing the instructions in the following article:

Unable to release Barcode Solution licenses or the error "Barcode license is exceeded" occurs

(2) Verify on the synchronization profile being used, on its Resources and Synchronization tabs, that there are less than 3000 resources being sent to the handheld device. If there are more, create a new test synchronization profile and assign less than 3000 (for example, 100 or so). If the issue cannot be reproduced with less resources being sent to the handheld, continue to limit the amount in the future being sent by the selected synchronization profile.

Related Articles

Synchronization Profiles do not save changes and the page appears to refresh without saving the changes

Error "No creatable Asset Types available for this profile" when trying to using Create/Receive with Barcode Solution on a handheld