Resolve data import error messages
Microsoft Cloud for Sustainability
This article lists error messages you might receive during data import in Microsoft Sustainability Manager, along with troubleshooting steps you can take to resolve them.
MSM-01-0001
Error message: Cannot add, edit, or delete records in a closed period.
Cause: You attempted to add, update, or delete records within a closed period. During a closed period, you can't make any changes.
Resolution: You can either reopen the closed period, or you can update the dates in the records causing the error.
More information: Edit a reporting period status.
MSM-01-0002
Error message: Duplicate: this record already exists.
Cause: The record already exists in Sustainability Manager, either in the Dataverse store or the current import flow. The duplicate record isn't imported. If you don't take action, the error continues to appear while the duplicate record is present, and the update doesn't occur.
Resolution: Identify the duplicate in the error log and the Sustainability Manager data store. Use the origin correlation ID if applicable, or use other record identifiers. Either remove the record in Sustainability Manager or from the current data import and try again. Origin correlation IDs are used as primary keys.
More information: Determine record uniqueness and Considerations and FAQ for data import.
MSM-01-0003
Error message: No emissions source called was found.
Cause: Sustainability Manager couldn't find the given emission source. Emission sources are case sensitive, and are required so you can relate an emission to its source.
Resolution: Verify that the value you're trying to import is the same value that you refer to in the application.
More information: Considerations and FAQ for data import.
MSM-01-0004
Error message: Unable to get display name for a lookup attribute while adding failure record.
Cause: The provided value doesn't exist in the data for the attribute. For example, a business travel record has a lookup attribute to a facility entity. If the facility isn't in the system, the business travel import for that record fails. This error could be for an option set, entity, or other data. To keep data clean and consistent, all attributes that reference other tables must be resolved.
Resolution: Review the existing data and the attribute that failed, and determine whether the record exists. Be sure to check the spelling and case sensitivity. Also ensure that all lookups are valid records in the system.
More information: Required attributes for the Microsoft Cloud for Sustainability data model, Extend the Cloud for Sustainability data model, and Considerations and FAQ for data import.
MSM-01-0005
Error message: Data import failed because a prerequisite entity within the same import failed.
Cause: The import of one entity failed, which caused the import of another entity to fail. To import the second entity, the first one must import successfully.
Resolution: Review the error messages for any prerequisite entities, resolve the errors, and then retry the data import.
More information: Microsoft Cloud for Sustainability data model and Considerations and FAQ for data import.
MSM-01-0006
Error message: Data import failed. Unable to schedule a connection refresh.
Cause: An incremental refresh can fail due to multiple causes.
Resolution: Get more details about the cause from the error message. On the Data imports page, look up the Dataflow Name in the Error message field. In the Power Apps portal, select Dataflows, search for and select the dataflow, and then select Show refresh history. Select the latest start time from the list of failed dataflows and review the more detailed error message.
More information: Error handling for incremental refresh.
MSM-01-0007
Error message: Unable to write failure record.
Cause: Sustainability Manager couldn't generate an error report.
Resolution: This message is informative only. Try rerunning the data import. Be sure to select the option for replacing duplicate records. If the error happens again, contact Support.
More information: Error handling for data import and Considerations and FAQ for data import.
MSM-01-0008
Error message: Invalid value for attribute. Please check if it exists.
Cause: There's a mismatch in the data types. This attribute requires a different value.
Resolution: Review the value and ensure it's valid for the attribute.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0009
Error message: Invalid boolean value for attribute.
Cause: There's a mismatch in the data types. This attribute requires a boolean value of either true or false.
Resolution: Review the value and ensure that you set it to true or false.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0010
Error message: Invalid datetime value for attribute.
Cause: There's a mismatch in the data types. This attribute requires a date/time value in mm/dd/yyyy format.
Resolution: Review the value and ensure that it's in mm/dd/yyyy format.
More information: Microsoft Cloud for Sustainability data model and Locales or regions for data.
MSM-01-0011
Error message: Invalid decimal value for attribute.
Cause: There's a mismatch in the data types. This attribute requires a decimal value, such as 123 or 123.45.
Resolution: Review the value and ensure that it's a decimal number.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0012
Error message: Invalid value for entity. Please check if it exists.
Cause: The entity contains an invalid value.
Resolution: Review the value and ensure it's valid for the entity.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0013
Error message: Invalid integer value for attribute.
Cause: There's a mismatch in the data types. This attribute requires an integer value, which includes positive or negative whole numbers and zero (for example, -1, 0, or 1).
Resolution: Review the value and ensure that it's an integer.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0014
Error message: Invalid lookup value for attribute. Please check if the value exists in the system.
Cause: There's a mismatch in the data types. Available data types are string, number, and boolean.
Resolution: Review the value and ensure that it's the correct data type for the attribute. Values are case sensitive.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0015
Error message: Invalid money value for attribute.
Cause: There's a mismatch in the data types. This attribute requires a value in the appropriate currency format.
Resolution: Review the value and ensure that currency format is one of the defined currency option sets/enums.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0016
Error message: Invalid option set value for attribute.
Cause: The provided value doesn't match any of the available choices in the option set for the attribute.
Resolution: Review the value and make sure it matches one of the available choices in the option set defined for the attribute.
More information: Create a choice.
MSM-01-0017
Error message: Job failed. If the problem continues, contact Microsoft customer support with the correlation ID.
Cause: The import failed.
Resolution: Retry the data import. If the problem continues, contact Support and provide them with the correlation ID.
More information: Error handling for data import and Considerations and FAQ for data import.
MSM-01-0018
Error message: Job failed. A column in the data source for connection no longer exists.
Cause: The source data file is missing a column.
Resolution: Ensure the source data file contains all necessary columns.
More information: Overview of data import in Microsoft Sustainability Manager.
MSM-01-0019
Error message: Job failed. The associated connection is not found in the system.
Cause: The connection wasn't created or doesn't exist. Possible that user could delete the connection while the import is still being processed.
Resolution: Create a new connection. If the error continues, contact your support.
More information: Overview of data import in Microsoft Sustainability Manager.
MSM-01-0020
Error message: Job failed. No emission sources exist on the connection.
Cause: Emission source not found for connection. This error occurs on versions of Sustainability Manager that are older than version 2.9.x.x, which was released on April 2023.
Resolution: Upgrade to the latest version of Sustainability Manager.
More information: Set up Microsoft Cloud for Sustainability.
MSM-01-0021
Error message: Job failed. The data source is empty.
Cause: The data source doesn't contain data.
Resolution: Ensure the data source contains data.
More information: Overview of data import in Microsoft Sustainability Manager.
MSM-01-0022
Error message: Job failed. Unable to read from the data source.
Cause: The data source doesn't contain data.
Resolution: Ensure the data source contains data.
More information: Overview of data import in Microsoft Sustainability Manager.
MSM-01-0023
Error message: Job failed. The source data file for connection was not found.
Cause: The source data file doesn't exist.
Resolution: Ensure the source data file exists in the specified location and contains data.
More information: Overview of data import in Microsoft Sustainability Manager.
MSM-01-0024
Error message: Incomplete error report. Maximum number of input rows reached.
Cause: The import errors report reached the maximum number of errors allowed.
Resolution: Resolve as many errors as you can and retry the import. If there are any remaining errors, they'll show up with this next run.
More information: Error handling for data import and Considerations and FAQ for data import.
MSM-01-0025
Error message: Incomplete error import. Maximum number of input rows for trial reached.
Cause: The import errors report reached the maximum number of errors allowed.
Resolution: Resolve as many errors as you can and retry the import. If there are any remaining errors, they'll show up with this next run.
More information: Error handling for data import and Considerations and FAQ for data import.
MSM-01-0026
Error message: Maximum number of rows reached.
Cause: The import errors report reached the maximum number of errors allowed.
Resolution: Resolve as many errors as you can and retry the import. If there are any remaining errors, they'll show up with this next run.
More information: Error handling for data import and Considerations and FAQ for data import.
MSM-01-0027
Error message: The associated entity is necessary to reference.
Cause: The entity that the import is looking up doesn't exist.
Resolution: Create the missing entity and retry the import.
More information: Microsoft Cloud for Sustainability data model and Considerations and FAQ for data import.
MSM-01-0028
Error message: Missing value for attribute.
Cause: A value is missing for a required attribute.
Resolution: Add the missing value for the attribute.
More information: Required attributes for the Microsoft Cloud for Sustainability data model.
MSM-01-0029
Error message: Missing option set value for attribute.
Cause: A value is missing in the option set for the attribute.
Resolution: Review the value and ensure it matches one of the available choices in the option set defined for the attribute.
More information: Create a choice.
MSM-01-0030
Error message: Job failed. Contains multiple non-lookup type attributes in its alternate key.
Cause: The entity contains two or more alternate keys.
Resolution: In the Power Apps portal, review the table settings and remove all but one alternate key.
More information: Determine record uniqueness and Considerations and FAQ for data import.
MSM-01-0031
Error message: No mappings found for query.
Cause: The data import tried to run, but didn't find any maps or queries associated with the connection. Data imports require at least one query that maps source data columns to the Sustainability Manager data model.
Resolution: In Sustainability Manager, select the connection. Select Edit mapping on the top menu bar. Map at least one of the available queries, and then select Save. Turn the Import toggle off and on to restart the import.
More information: Map data.
MSM-01-0032
Error message: No data definition found for the ID.
Cause: The Excel import template doesn't contain the data definition ID.
Resolution: Ensure that you download latest Excel templates, and that you populate the template data according to their instructions.
More information: Import data with Excel templates.
MSM-01-0033
Error message: Incompatible Microsoft Excel file.
Cause: The Excel template used for data import is invalid. It might not have the correct column or row format.
Resolution: Download the template from the Excel import wizard and use that instead.
More information: Import data with Excel templates.
MSM-01-0034
Error message: No valid records were inserted.
Cause: The import completed running, but didn't import any valid records.
Resolution: Download the error report by selecting the Information icon near the error message status or by selecting the failed connection and the respective recent connection.
More information: Error handling for data import and Considerations and FAQ for data import.
MSM-01-0035
Error message: Record not imported. No natural key for entity.
Cause: A referenced entity from the current record doesn't have a defined natural key. Without a defined natural key, the system can't find the record.
Resolution: In the Power Apps portal, go to the entity definition and add a natural key for the entity. Alternately, you can refer to the entity with the GUID associated with the record.
More information: Determine record uniqueness.
MSM-01-0036
Error message: Source record contains unknown.
Cause: A lookup value doesn't exist for a referenced entity during import.
Resolution: Review the value and ensure it's correct. It can be case-sensitive.
More information: Microsoft Cloud for Sustainability data model.
MSM-01-0037
Error message: Source record contains an unknown value for at least one of the following.
Cause: The provided value doesn't exist in the data for the attribute. For example, a business travel record has a lookup attribute to a facility entity. If the facility isn't in the system, the business travel data import for that record fails. This error could be for an option set, entity, or other data. To keep data clean and consistent, all attributes that reference other tables must be resolved.
Resolution: Review the existing data and the attribute that failed, and determine whether the record exists. Be sure to check the spelling and case sensitivity. Also ensure that all lookups are valid records in the system.
More information: Required attributes for the Microsoft Cloud for Sustainability data model, Extend the Cloud for Sustainability data model, and Considerations and FAQ for data import.
MSM-01-0038
Error message: Unknown error. If the problem continues, contact Microsoft customer support.
Cause: The correlation ID has an unspecified error.
Resolution: Retry the data import. If the problem continues, contact Support and provide them with the correlation ID if necessary.
More information: Determine record uniqueness and Considerations and FAQ for data import.
MSM-01-0039
Error message: Unknown error. If the problem continues, contact Microsoft customer support with the correlation ID.
Cause: The correlation ID has an unspecified error.
Resolution: Retry the data import. If the problem continues, contact Support and provide them with the correlation ID.
More information: Determine record uniqueness and Considerations and FAQ for data import.
MSM-01-0040
Error message: Unknown error. If the problem continues, contact Microsoft customer support with correlation ID.
Cause: The correlation ID has an unspecified error.
Resolution: Retry the data import. If the problem continues, contact Support and provide them with the correlation ID.
More information: Determine record uniqueness and Considerations and FAQ for data import.
MSM-01-0041
Error message: Unable to schedule connection refresh. Please try again. If the problem continues, contact your Microsoft customer support with the connection ID.
Cause: Scheduling failed for a heterogeneous data import.
Resolution: Retry the data import. If the problem continues, contact Support and provide them with the correlation ID.
More information: Overview of data import in Microsoft Sustainability Manager, Error handling for data import, and Considerations and FAQ for data import.
MSM-01-0042
Error message: No columns were mapped.
Cause: The data import tried to run, but didn't find any maps or queries associated with the connection. Data imports require at least one query that maps source data columns to the Sustainability Manager data model.
Resolution: In Sustainability Manager, select the connection. Select Edit mapping on the top menu bar. Map at least one of the available queries, and then select Save. Turn the Import toggle off and on to restart the import.
More information: Map data.
MSM-01-0043
Error message: Cannot import data. Importing Scope 3 categories 10, 11, 14, and 15 requires a Microsoft Sustainability Manager Premium license.
Cause: The import contains entities that are only available with a valid Microsoft Sustainability Manager Premium license. Your license likely expired.
Resolution: To import these entitities, you need to renew your Premium license. Otherwise, remove them from your import.
