Reality Model Tile Sets
Error: DgnV8_0104
Error message: Reality model <model name> is invalid. Skipping
Issue:
While preparing a reality model (a scalable-mesh 3D model, such as a scanned or photogrammetry mesh) for display in the iModel, the synchronizer found that the model could not be opened or read as a valid reality model. Because the model is not usable, it is skipped and it will not be shown in the iModel.
Cause:
- The reality model's source data is missing, incomplete, or could not be loaded.
- The source data is damaged, or was not fully uploaded, copied, or downloaded to the location the drawing references.
- The reality model attachment points to data that is no longer available at the expected location.
- This is an error for the affected reality model; that model is skipped.
- The reality model will not be viewable in the iModel.
- Other models and content continue to be processed.
Solution:
- Note the model name shown in the message; it identifies which reality model could not be used.
- Confirm the reality model opens correctly in its authoring or viewing application.
- Make sure the reality model's source data is complete and that all of its supporting files are present at the location the drawing references.
- If the data was uploaded or shared through a reality-data or project service, verify it finished uploading successfully and is fully available.
- Re-attach or re-point the reality model to a complete, undamaged copy of the data if needed, then submit the source file for synchronization again.
- If the model opens correctly in its authoring application but the problem persists, contact Bentley support and provide the model name from the message.
- The message includes the name of the specific reality model that was skipped, which helps you locate the source of the problem.
- Related messages cover other reality-model situations, such as a model format that is not currently supported, or a failure while creating the display tiles. If you see several of these together, review the reality models attached to the source file.
Error: DgnV8_0110
Error message: Failed to create tiles for <model name> (Status: <status code>).
Issue:
While preparing a reality model (such as a point cloud or raster model) for display in the iModel, the synchronizer was unable to generate the display tiles for it. The partly created output for that model is removed and the synchronizer moves on to the next model.
Cause:
- The source reality data (point cloud or raster) is incomplete, corrupt, or in a format that could not be processed.
- There was a problem writing the tile output to disk, such as insufficient disk space, a full or unavailable temporary/output location, or missing write permissions.
- The output location was blocked or in use by another process, preventing files from being written.
- This is an error for the affected model, but the overall synchronization continues with the remaining models.
- The reality model that failed will not have display tiles and therefore will not appear (or will appear incomplete) in the published iModel.
- Any partial output already written for that model is cleaned up automatically.
Solution:
- Open the source reality data in its native application to confirm it is valid and not corrupt; repair or re-export it if needed.
- Re-run the synchronization after addressing the disk or data problem.
- If the problem persists for a specific model, note the model name shown in the message and share it with your administrator or contact Bentley Support, along with the status code.
- The status code in the message is a technical indicator that support can use to narrow down the cause.
- Related errors cover other stages of reality model publishing — for example, a scalable-mesh model failing to tile, a temporary or output directory that could not be found or created, an empty tile output, or a failure uploading the generated data. If you see several of these together, focus first on disk space, folder permissions, and the validity of the source reality data.
Error: DgnV8_0112
Error message: Failed to upload tileset '[Model name]' to Reality Data Server (The Reality Data Server's own error text is included with the report as additional context.)
Issue:
The connector reports error DgnV8_0112 when it fails to create the Reality Data entity on the Reality Data Server (RDS) for a reality model (ScalableMesh, point cloud, or raster tileset).
- During the "Create Reality Model Tiles" step, after the connector has generated the local tileset for a model, it calls the Reality Data Client to create a Reality Data entry on the server before uploading the tiles.
- This error is reported when that create request returns an unsuccessful response.
- The affected model's tileset is not uploaded, its local output directory is removed, and processing continues with the next reality model. The model will not have a reality-data URL and will not display its reality content in the iModel.
- Example: Failed to upload tileset 'Terrain.pod' to Reality Data Server - HttpStatus: 403, The user has insufficient permissions for the requested operation.
Cause:
This error is reported when:
- The connector has successfully created a local tileset for a reality model and is configured to upload reality data
- The attempt to create the Reality Data on the Reality Data Server failed.
- Authentication or authorization failure: the access token / token provider could not obtain valid credentials, or the account lacks permission to create Reality Data in the target project.
- The project (iTwin/context) id is invalid or the user has no access to it.
- Network connectivity problems, proxy/firewall restrictions, or the Reality Data Server being unreachable or temporarily unavailable.
- The connector is pointed at the wrong region/environment (DEV/QA/PROD mismatch) so the service rejects the request.
- Invalid or incomplete reality-data creation parameters (name, type, root document, or extent).
Solution:
Review the reported error text:
The Reality Data Server's response message is included with the issue; use it to identify whether the failure is authentication, authorization, connectivity, or a bad request.
Verify credentials and permissions:
- Confirm the account has permission to create Reality Data in the target iTwin.
Verify the project and environment:
- Confirm a valid project GUID is associated with the iModel (otherwise the fallback test project id is used, which may not be accessible).
- Confirm the connector is configured for the correct region/environment matching your credentials.
- Ensure the machine can reach the Reality Data Server (network, proxy, and firewall allow the connection).
Re-run the connector and confirm the tileset uploads and the DgnV8_0112 error no longer appears for that model.
- Ensure valid, non-expired credentials and correct project/context access are configured before running reality-data upload jobs.
- Keep the connector's region/environment configuration aligned with the credentials and project being used.
Monitor connector synchronization reports for the accompanying Reality Data Server error text: it distinguishes authentication/authorization failures from connectivity or bad-request failures.