Here you will find an explanation and best practices for solving Unexpected Data related synchronization errors.  

Category: Unexpected Data

Unexpected data refers to data within a dataset that does not align with the expected values. Dealing with unexpected data involves identifying the source of such data and deciding how to correct it.

Unexpected Reference File data

Duplicated data can be introduced in different situations and can cause duplicated graphics and attributes to appear in the iModel, which is not desired. 

Error: Dwg_0199

 Error message: "Model [FileName.DWG, INSERT ID=11A] was not imported.<File name> MissingInputFile: <File path>.

Issue:
One or more references in the master design file could not be resolved. This can cause missing data in the Model. 

Cause:

• Reference files have been disassociated from the master file 
• The reference file is damaged
• The reference file is 0 bytes in size
  

Solution:

• Check if you can successfully open the reference file. If the error is shown while loading the file, follow the design application error guidelines to resolve the issue.
• Open the master design file and check if the references are loaded and visible. If the references are not loading, fix the reference relations in the design application.
• If using ProjectWise, run a Reference scan and check if the references have been resolved automatically. Read more about Reference Scan in ProjectWise Explorer.
• Reference relations can be fixed manually by using MicroStation Connect Edition Desktop Reference dialog. Read more about References.
• Read more about why Reference scanning is important. 
• Contact Bentley Support for assistance if errors can not be resolved. 

Invalid Input Data

Fatal: SPPID_0001

 Fatal message: "Drawing.xml was not found inside ZIP archive. Input file is not a valid SmartPlant ZIP file.."

Issue:

Import failure because of the invalid or corrupted ZIP source file.

Cause:

• The input file format is incorrect.
• The Drawing.xml file is missing in the ZIP file.

Solution:

• If these kinds of issues are occurring, the ZIP file was likely not created by SPPID. Please follow the instructions on exporting here: 

Fatal: SPPID_0002

 Fatal message: "Input file is not a valid SmartPlant PID/ZIP file"

Issue:

Import failure because of invalid source file format or .pid file is missing in the .zip file.

Cause:

• The input file (.zip file) format is not correct
• Graphics.pid file is missing in the .zip file. The .zip file should have both Drawing.xml and Graphics.pid files.

Solution:

• If these kinds of issues are occurring, the ZIP file was likely not created by SPPID. Please follow the instructions on exporting here: 

View

Warning: Revit_0014

 Warning message: "File_Name' view has 3050 excluded elements. This is too much and could decrease display performance."

Issue:
 Elements are missing in the created iModel. 

Cause:

• Elements could be out of Extent and due to this reason not processed to iModel. 
• Elements can be unused in Revit file and for this reason, ignored during processing. 

Solution:

• Open the file in Revit and Purge unused elements
• Set Extents appropriate for the iModel. Read more about Spatially Aligning Revit models.

Parasolid

Warning: DgnV8_01344

 Warning message: "ACIS elements were found. This will cause slow processing every time the file is synchronized."

Issue:
Slow Synchronization performance due to ACIS elements in the iModel.

Cause:

ACIS elements were converted or imported from Autodesk or other software.

Solution:

To optimize synchronization performance, ACIS elements need to be converted to a more efficient format. Conversion can be done in a Design application. This is a one-time operation that will improve performance during synchronization.

Steps to fix ACIS elements:

1. Open the Bentley Design application (for example MicroStation, OpenBuildings Designer, or any application you are using) and please type Key-in in the Search Ribbon. 

2. Type convert acistoparasolid all. 

3. Click Enter and on the lower ribbon you will see if and how many ACIS elements have been converted.

Conversion and importing processes require attention. If you want to open the non-DGN file in MicroStation, it is important to convert it to a suitable format. Read more about  MicroStation supported formats. 

GCS

Warning: Revit_0016

 Warning message: "Geo-location point (Survey Point) was moved to local zero coordinate (Project Base Point) due to too large distance between them"

Issue:

The distance between the Survey Point (SP) and Project Based Point (PBP) exceeds the "Maximum Distance Limit" (10 milles or 16 kilometers), which would lead to less reliable and less accurate graphical representation of geometry elements.

Cause:

Some elements are beyond the maximum distance limit.

Solution: 

Move the Project Base Point and Survey Point closer together, within 10 miles or 16 kilometers distance.

Follow this wiki on how to move the Project Base Point: https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-A973AC69-7095-4C09-BD7E-E3B6EAF36ABB 
Follow this wiki on how to move the Survey Point: https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-4EAEF1B1-CC5B-4484-9727-91ACD90B0B78 

Follow the best practices from: https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-3F79BF5A-F051-49F3-951E-D3E86F51BECC which are:

• When you start a project, move the project base point and survey point to the desired locations and pin them in place. Avoid moving them unnecessarily.
• If the survey point is located more than 20 miles or 32 kilometers from the internal origin, turn off its visibility in views to avoid issues:
  1. Open the desired view
  2. Click View tab > Graphics panel > Visibility/Graphics
  3. On the Model Categories tab of the Visibility/Graphics dialog, scroll down to Site, and expand it
  4. Uncheck Survey Point