Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.6.1 database migration fails due to invalid XML characters in component name

SAM 6.6.1 database migration fails due to invalid XML characters in component name

Updated June 7, 2018


This article describes how to resolve failed database migration due to invalid characters in component names, such as special white space characters. 


  • SAM 6.6.1


The database migration script cannot serialize data for node IDs with invalid XML characters, such as special white spaces (hexadecimal character 0x000C)s. 


Convert the invalid XML character to a binary, variable-length binary (varbinary), or image data type and use the binary base-6 value directly.

  1. Backup the Orion database. See Backup the database using SQL Server Management Studio.
  2. Use a query to remove invalid characters in component names. The following example shows how to remove a  white space character, 0x000C (hexadecimal), by using the decimal equivalent, 12.

update [dbo].[APM_Component] set [Name] = REPLACE([Name], NCHAR(12),'') where [Name] like '%'+NCHAR(12)+'%'

  1. Run the Orion Configuration wizard.
  2. If the wizard returns additional character-related errors, convert the hexadecimal character to decimal format and replace the NCHAR integer_expression value in the query, as necessary. 


Last modified