Learn more

Migration error codes

You may encounter one or more error conditions during the data migration process. The list below describes the possible error codes.

Note: You must first enable detail logging in the migration settingsbefore starting each migration to record migration error code details. Press the Alt key and click any event listed in the Migration Details window to see the corresponding error code details.

Error codes described in this topic are different than Pervasive error codes. You may have an error condition in your Pervasive data, which results in an error code prefaced by one of the following error messages:

"TSIO status code "
"Pervasive status code"
"Btrieve status code "

Pervasive error codes normally result in a failure of the data migration process. If you receive one of these Pervasive error codes, see Understanding Pervasive errors for more information.

Migration error codes
Type	Error Code	Description
	The AddonType character value, {0}, was mapped more than once.	The Pervasive data has been modified outside the Estimating Management Console application. The data migration cannot continue. Restore your data from backup before trying the data migration again.
	AB_DATABASE_	The original Pervasive file name has been appended to conform with Microsoft SQL Server requirements. This prefix is added to the database name where the original Pervasive file name started with a number, a space, or other non-conforming character.
	Finished uploading {0} rows in table {1}.	Diagnostic message—displays when the Estimating Management Console successfully imports data for migration.
	The attachment path '{0}' contains one or more invalid path characters.	Invalid path characters (such as quotation marks ("), ellipses (. . .), or less than (<) or greater than (>) symbols) appear in the attachment file path. Check the file path of the referenced attachment file.
	Beginning to upload {0} rows in table {1}.	Diagnostic message—displays when the Estimating Management Console begins importing data for migration.
	Unable to verify estimate totals because the estimate has multi-currency enabled.	The "Multicurrency" feature has been enabled for the referenced estimate. The Estimating Management Console cannot verify the estimate totals.
	Unable to verify estimate totals because the estimate requires recalculation.	The Estimating Management Console cannot verify the totals for the referenced estimate. You must open the estimate in Sage Timberline Office Estimating 9.x and perform the recalculation operation; then save the estimate and perform data migration.
	Unable to verify estimate totals because the estimate requires recalculation and has multi-currency enabled.	The Estimating Management Console cannot verify the totals for the referenced estimate because the "Multicurrency" feature has been enabled. The Estimating Management Console cannot verify the estimate totals.
	Unable to verify the estimate because the estimate has cuts or adds that have not been generated.	The Estimating Management Console cannot verify the totals for the referenced estimate because the estimate has cuts and adds that cannot be generated during the migration. The Estimating Management Console cannot verify the estimate totals.
	A discrepancy was found in the grand total for the estimate.	The Estimating Management Console discovered an issue with the estimate grand total. Perform a recalculation of your original Pervasive-based estimate and try the data migration again.
	A discrepancy was found in the overline for the estimate.	The Estimating Management Console discovered an issue with the estimate grand total. Perform a recalculation of your original Pervasive-based estimate and try the data migration again.
	A discrepancy was found in the add-on for the estimate.	The Estimating Management Console discovered an issue with an estimate addon amount. Perform a recalculation of your original Pervasive-based estimate and try the data migration again.
	A discrepancy was found in an item amount for the estimate.	The Estimating Management Console discovered an issue an estimate item amount. Perform a recalculation of your original Pervasive-based estimate and try the data migration again.
	A discrepancy was found in the add-on grand total for the estimate.	The Estimating Management Console discovered an issue with the estimate addon total amount. Perform a recalculation of your original Pervasive-based estimate and try the data migration again.
	Value '{0}' in row {1} column {2} in table {3} failed a check constraint. {4}	Displays the value and table location of the data that fails to meet Sage Estimating requirements. The affected data row and all rows referencing it have not migrated. If desired, you can adjust the referenced value in the data to meet the requirements and try the data migration again.
	An error occurred while reading to or writing from the disk. Contact your system administrator for support.	You must have a copy of Sage Timberline Office Estimating operating on the computer or server where the data you are migrating is located. Install the Sage Timberline Office Estimating software on the computer or server where your Sage Timberline Office Estimating data is located. Then try the data migration again.
	Category codes must contain only one or more of the characters, 'L', 'M', 'S', 'E', and 'O', with no duplication.	One or more "Category" codes in the selected data row is invalid. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and ensure all Category codes have only "L", "M", "S", or "E" characters with no duplication (such as "LL" or "MSM") and try the data migration again.
	The rate table row which '{0}' references does not have the expected category type {1}.	An item in the selected data that is set up to use an equipment rate table does not reference an equipment rate table row. -or- An item that is set up to use a labor rate table does not reference a labor rate table row. The affected data row and all rows referencing it have not migrated. If desired, you can review the referenced item's settings and verify the referenced rate tables are correct and try the data migration again.
	Created database; Database Name='{0}', ConnectionString='{1}'.	Diagnostic message—displays when the Estimating Management Console successfully creates the referenced database.
	The Pervasive database file path '{0}' contains one or more invalid path characters.	Invalid path characters (such as quotation marks ("), ellipses (. . .), or less than (<) or greater than (>) symbols) appear in the Pervasive database file path. The data migration cannot continue. Check the file path of the referenced database and remove the invalid characters then try the data migration again.
	AddressBook	Displays the name of the Address Book database into which data is merged.
	The destination column '{0}' is mapped more than once.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	The value is not one of the following: {0}.	The referenced data value is not part of a known set of values. For example, the round direction is not U, D, C, N, or a space. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Removing row {0} in table {1} because the value '{2}' in column {3} is outside the valid range of {4} to {5}.	A numerical value in the referenced data is out of the acceptable number range. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Changing subcategory description from '{0}' to '{1}' to ensure that the value is unique.	The referenced subcategory description is not unique. The Estimating Management Console has changed the referenced description to make it unique.
	Assembly help topics are not supported. Ignoring help topic in file '{0}'.	The referenced data contains one or more assembly Help topics; however, assembly Help topics are no longer supported. The assembly Help topic has not been migrated.
	The value '{0}' in column {1} exceeds the maximum length {2}.	The length of the value in the referenced data exceeds the limit in the Sage Estimating requirements. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Migrating to server; ConnectionString='{0}'.	Diagnostic message—displays when the Estimating Management Console is migrating data to the specified server.
	There is a mismatch in the definition of the foreign key. The count of child columns, {0}, in table {1} does not match the count of parent columns, {2}, in the table {3}.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing business flag value destination column.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing business flag value destination columns.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing business flag source column.	The Pervasive data has been modified outside the Sage Estimating application. The data migration cannot continue. Restore your data from backup before trying the data migration again.
	Missing business flag value map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing business flag value mapping.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing column map in table map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing destination column in column map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Estimating Management Console to restore them before trying the data migration again.
	Missing destination table in table map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	The value(s) {0} in column(s) {1} in the child table {2} cannot be found in the parent table {3}.	A row in the specified data references another row that does not exist. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	No foreign key child column names specified for child table {0}.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	No foreign key children specified for parent table {0}.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Row will not be migrated. {0}	The Pervasive data has been modified outside the Sage Estimating application. The data migration cannot continue. Restore your data from backup before trying the data migration again.
	Row will be migrated but the reference will be discarded. {0}	The Pervasive data has been modified outside the Sage Estimating application. The data migration cannot continue. Restore your data from backup before trying the data migration again.
	No foreign key names specified for parent table {0}.	The Pervasive data has been modified outside the Sage Estimating application. The data migration cannot continue. Restore your data from backup before trying the data migration again.
	Missing source column in column map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing source table name.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Missing the table map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Unknown Trade	A trade name was not found in the Pervasive data. The Estimating Management Console assigns the displayed trade name instead.
	Missing trade name in the trade table {0}. Using trade name '{1}'.	The company in the address book does not have an assigned trade but one is required. The Estimating Management Console assigns the displayed trade name instead.
	This address book is not associated with estimating and will not be migrated.	The specified address book contains no companies associated with Sage Estimating and has not been migrated.
	The value cannot be empty.	The value cannot be empty but it is empty. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	The value is neither an integer nor is it empty.	The referenced data value must be either an integer or a blank (empty). The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Null column map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Null table map.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	Removing row because row {0} in column {1} in table {2} is null.	The referenced data value cannot be processed. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	The value is not in the range {0} and {1} inclusive.	The referenced data value is not in the expected value range. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Reading Pervasive data from '{0}'.	Diagnostic message—displays when the Estimating Management Console is retrieving data from a database.
	STD_DATABASE_	The original Pervasive file name has been appended to conform with Microsoft SQL Server requirements. This prefix is added to the database name where the original Pervasive file name started with a number, a space, or other non-conforming character.
	The table {0} has been mapped more than once.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	A discrepancy was found in an add-on for the estimate.	A discrepancy was found in a total. Although the Estimating Management Console does not require you to take any action, you can review the referenced estimate for accuracy and try the migration again.
	A discrepancy was found in the add-on grand total for the estimate.	A discrepancy was found in a total. Although the Estimating Management Console does not require you to take any action, you can review the referenced estimate for accuracy and try the migration again.
	A discrepancy was found in the grand total for the estimate.	A discrepancy was found in a total. Although the Estimating Management Console does not require you to take any action, you can review the referenced estimate for accuracy and try the migration again.
	A discrepancy was found in an item amount for the estimate.	A discrepancy was found in a total. Although the Estimating Management Console does not require you to take any action, you can review the referenced estimate for accuracy and try the migration again.
	A discrepancy was found in an overline for the estimate.	A discrepancy was found in a total. Although the Estimating Management Console does not require you to take any action, you can review the referenced estimate for accuracy and try the migration again.
	The transform operation for {1} is finished. Duration: {0}.	Diagnostic message—displays when the Estimating Management Console successfully completes a transform portion of the data migration process.
	Subcategory will not be migrated. Unable to automatically create a unique description for the subcategory '{0}'. All automatically generated descriptions are in use.	A unique subcategory description could not be created. Subcategory descriptions must be unique. Under most circumstances, the Estimating Management Console can append an existing description to make it unique; however, it could not do so in this case. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Unable to automatically create a valid estimate name for '{0}'. All automatically generated estimate names are in use.	A unique estimate name could not be generated. Estimate names must be unique. Under most circumstances, the Estimating Management Console can append a value to make it unique; however, it could not do so in this case. The data migration cannot continue. Try renaming the referenced database file before trying the data migration again.
	Unable to automatically create a valid SQL Server database name for '{0}'. All automatically generated database names are in use.	A unique database name could not be generated. Database names must be unique. Under most circumstances, the Estimating Management Console can append a value to make it unique; however, it could not do so in this case. The data migration cannot continue. Try renaming the referenced database file before trying the data migration again.
	Removing the reference to the standard database. Unable to find a migrated standard database with the path '{0}' and identifier {1}.	Some of the data refers to a database that has not been migrated. The reference to the database in the affected data row and all rows referencing it has been removed from the migration. If desired, you can migrate the referenced database then re-migrate your data again to avoid this condition.
	Unable to retrieve the full path for '{0}'. {1}	Unable to get the full path of a database path specified in an estimate. Although the Estimating Management Console does not require you to take any action, you can review the referenced database path for accuracy and try the migration again.
	The value(s) {0} in column(s) {1} appear more than once in the table {2}.	The referenced data value or values appears more than one time; however, the value or values must be unique. The data row referencing the duplicate value has not migrated. If desired, you can review your data and make corrections then try the data migration again.
	The 'no warn' data relation '{0}' does not exist.	The AddressBookMetadata.xml, StandardMetadata.xml, or EstimateMetadata.xml files have been modified. The data migration cannot continue. Undo your changes to these files or uninstall and reinstall Sage Estimating to restore them before trying the data migration again.
	The file path, '{0}', does not reference a Pervasive estimate (.PEE), address book (.ABM) or a standard database.	The referenced file path that is not a directory containing a standard database, an estimate (.PEE file) or an address book (.ABM file). The data migration cannot continue. Review the referenced file path for accuracy and make corrections in the data migration setup before trying the data migration again.
	Uploading to database; ConnectionString='{0}'.	Diagnostic message—displays when the Estimating Management Console uploads converted Pervasive data to the SQL Server database.
	Removing row {0} in table {1} because the value '{2}' in column {3} is not convertible to type {4}. {5}	The referenced data value could not be converted to its corresponding SQL Server type. For example, the Estimating Management Console could not convert a Pervasive "string" value into an "integer" for Microsoft SQL Server. The affected data row and all rows referencing it have not migrated. If desired, you can review your data and make corrections then try the data migration again.
	Cannot create file {0} because it already exists. Change the file path or the file name, and retry the operation.	The referenced database cannot be migrated because a copy already exists in the SQL database server. This error occurs when an existing database of the same name is deleted from the SQL database server but Microsoft SQL Server does not remove references to the database from its data directory. Try renaming the referenced database in Pervasive and perform the data migration again.