Corrupt Data


Corrupt Data category refers to a situation where the integrity of digital information has been compromised, resulting in synchronization errors. There can be multiple reasons why data corruption can occur.  Here you will find an explanation and best practices for solving corrupt-related synchronization errors.  

Table of Contents

Import Failure

Warning: DgnV8_0093

Warning message: The project is not geo-located because no Geographic Coordinate System was detected or supplied.  

Issue:
While preparing attached reality data for the iModel, no valid geographic coordinate system could be found for the project. Because of this, the geographic outline (footprint) that describes where the reality data sits on the earth could not be calculated. 

Cause:

Effect:

  • This is a warning only. Synchronization continues and the reality data is still processed and attached.
  • The reality data is not given a geographic footprint, so it may not be discoverable by location-based searches and may not be listed correctly in geographic data catalogs.
  • The iModel itself is not geo-located, so it will not align with mapping backgrounds or other geographically referenced content.

Solution:

  • Open the design file that serves as the basis of the iModel and check whether a geographic coordinate system is assigned.
  • If none is assigned, assign the correct coordinate system for the project and save the file.
  • If one is assigned, confirm it is a complete, recognized definition and not a custom or partial one that may not be understood. Reassign it from the standard coordinate system library if in doubt.
  • If your coordinate system definition is stored in a separate library or workspace file, make sure that file is included with the data you submit for synchronization.
  • Save the file and submit it for synchronization again.

Additional Information: 

  • This message normally appears only in unusual circumstances, because the geographic coordinate system is usually established earlier in the process. If it appears, it indicates the coordinate system information was expected but was unavailable or unusable.
  • If your project is intentionally not geo-located, this warning can be safely ignored, though reality data will not be locatable geographically.

 

Import Failure

Fatal: SPPID_0015

Fatal Error message: "Cannot open source <filename>. The file may be missing, corrupt, or unsupported." 

Issue:
Import Failure because of an issue with the source file. 

Cause:
The SPPID Connector failed to read the source file properly. It may be due to several reasons such as unsupported file, the data may be corrupted, or it has a missing data. As there may be different reasons, debugging may be required to determine the exact cause of the issue.

Solution:
• Ensure that the input file has valid data and is not corrupted by checking the content of the .zip folder. Extract the .zip file and verify that the source .pid file is present and has data - its size should not be 0KB. If source file has no data(0KB), kindly update the file with the correct data.
• Ensure .pid file validity by opening it via Hexagon SmartSketch® Viewer.
• Once file has been updated and re-exported from source application, re-synchronize the file to the imodel.
• Contact Bentley Support for assistance if the issue cannot be solved. 

 

Error: Rvm_0002

Error message: "Failed to read the rvm file, position #" 

Issue:
The connector failed to read the given .rvm file at the mentioned file position.

Cause:
The file format may differ from the versions currently supported by the connector, or the file’s binary data may be corrupted. This issue can occur if the file was saved in a newer or different format than the connector is designed to read. In such cases, the connector may not recognize the file structure or required metadata. Alternatively, the file’s binary content may be incomplete, damaged, or altered, preventing the connector from parsing it correctly. Corruption can result from interrupted saves, storage errors, or transfer issues. 

Solution:
• Ensure that the input file has valid data and is not corrupted by checking the content of the file. 
• The file size should not be 0KB. If the source file has no data (0KB), kindly update the file with the correct data.
• Verify that the file format is supported by the connector version in use. 
• Re-export the file from the source application, and re-synchronize the file to the imodel.
• Contact Bentley Support for assistance if the issue cannot be solved. 

 

Error: Rvm_0004

Error message: "Failed to read the .att file, position #" 

Issue:
Connector failed to read the attribute file at the mentioned file position.

Cause:
The attribute file format may differ from the versions currently supported by the connector, or the file’s binary data may be corrupted. This issue can occur if the file was saved in a newer or different format than the connector is designed to read. In such cases, the connector may not recognize the file structure or required metadata. Alternatively, the file’s binary content may be incomplete, damaged, or altered, preventing the connector from parsing it correctly. Corruption can result from interrupted saves, storage errors, or transfer issues. 

Solution:
• Ensure that the attribute input file has valid data and is not corrupted by checking the content of the file. 
• The attribute file size should not be 0KB. If the source file has no data (0KB), kindly update the file with the correct data. 
• Verify that the file format is supported by the connector version in use. 
• Re-export the file from the source application, and re-synchronize the file to the imodel.
• Contact Bentley Support for assistance if the issue cannot be solved. 

Error: Rvm_0005

Error message: "Unsupported .att file " 

Issue:
Unsupported format of the attribute file.

Cause:
The format of the attribute file is not recognized or may differ from the versions currently supported by the connector.

Solution:
We advise submitting a service case for Bentley Support for a detailed investigation. This will enable our team to analyze the file and identify any structural or formatting modifications impacting compatibility. Following this assessment, we will determine whether an update to the ATT file reader is feasible to support the changes or confirm if the modifications fall outside the scope of supported configurations. 

Range

Warning: DgnV8_0099

Warning message: Geographic Coordinate System conversion: coordinates outside the normal useful range of system.

Issue:
While calculating the geographic outline (footprint) of attached reality data, the position of the data had to be converted to standard world latitude and longitude. The conversion succeeded, but the location falls outside the area that the project's geographic coordinate system was designed to cover, so the resulting position may be less accurate than expected.

Cause:

Effect: 

  • This is a warning only. Synchronization continues, and the reality data is still processed and attached. 
  • The geographic footprint recorded for the reality data may be imprecise, which can affect location-based search and how the data is listed in geographic catalogs. 
  • If the positions are significantly wrong, the reality data may not line up correctly with mapping backgrounds or other geographically referenced content. 

Solution:

  • Confirm that the geographic coordinate system assigned to the design file is the correct one for the project's real-world location.
  • If a regional or local system is in use, verify that all of your content, including the reality data, actually falls within the region that system was designed for. If not, choose a coordinate system appropriate for the full area covered.
  • Check that the reality data is positioned where you expect. Reality data that was attached at the wrong location or with an incorrect origin can push coordinates far outside the expected area
  • Review the design file for stray or misplaced content that sits a long way from the rest of the project, and correct or remove it. 
  • Save the file and submit it for synchronization again.

Additional Information: 

  • If your project is genuinely near the edge of the coverage area of its coordinate system, small inaccuracies are expected and this warning can be accepted.
  • Other coordinate system warnings may appear alongside this one for the same reality data. Resolving the underlying coordinate system or placement problem usually clears them together.

Repository Link

Fatal: Revit_0027

Fatal error message: The input file's repository info was not found in the iModel. Perhaps the file was renamed several times without proper repository updates. 

Issue:
The Repository link is not found in the iModel.

Cause:
An earlier update might not have updated the repository links.

Solution:
Please contact Bentley support mentioning this error.