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.
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 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 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 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.