Category: Briefcase to iModel
Error message: There was a server error. (Unable to open briefcase <id> for other reason: 406.) — The iModelHub returned an internal server error (Error::Id 406 = InternalServerError) while opening the briefcase. This is a transient service-side failure.
Issue:
This error occurs when the connector is unable to open the briefcase against iModelHub during the Pull/Merge/Push phase of the synchronization.
Cause:
The connector holds a local briefcase and must open it against iModelHub before it can pull, merge, and push any changes. When the request fails, Dgn_0190 is raised. The most common cause is a transient iModelHub service error which is a temporary problem on the service side rather than a problem with the input files, configuration, or the local briefcase. Other causes include the server briefcase having been deleted (BriefcaseDoesNotExist), a concurrent push by another user, or a required pull.
Solution:
Retry the synchronization: This error is usually caused by a temporary iModelHub service issue, so re-running the connector job most often resolves it on its own.
Wait a few minutes and try again: if the first retry fails, in case another user was pushing at the same time or the service was briefly unavailable.
Check the iTwin Platform / iModelHub service status: Confirm there is no ongoing service incident for your region/environment. This can be checked on https://status.bentley.com
Confirm your access: Make sure you still have permission to the iTwin and iModel, and that your credentials or sign-in have not expired.
Contact Bentley Support: If the synchronization continues to fail with this error, contact Bentley Support. Provide your iModel ID, the iTwin ID, the environment, and the approximate time of failure. Support will review the detailed service logs (which capture the internal error code and message) to determine the exact cause.
Error message: Pull is Required.
Issue:
Pull is required.
Cause:
This error occurs when another user or process has pushed changes to the iModel on the server. Your local copy of the iModel (the briefcase) must be updated with these server changes before your new changes can be synchronized. This is a common and expected event in collaborative workflows to prevent data conflicts.
Solution:
The synchronization service usually resolves this automatically by pulling the latest server changes and merging them into your local briefcase before retrying the push.
- Retry the operation: In most cases, simply running the synchronization job again will resolve the issue, as the framework is designed to pull changes first.
- Contact Support: If the issue persists after several retries, it may indicate a more complex merge conflict or an issue with the iModel service. Contact Bentley Support for assistance.