Knowledge Base > Data Architect > Resolving Check-In Errors using a Clean Get

Need Support?

Can't find the answer you're looking for? We're here to help.

Resolving Check-In Errors using a Clean Get

Description

Performing Repository operations can occasionally lead to local file corruption, resulting in persistent check-in failures or Repository Merge errors. This issue often remains even undoing any modifications and typically manifests as diagram operation failures, local .dm1 corruption, or the inability to merge changes. You may encounter specific errors such as:

20.9 error

The problem occurs when there is corruption within the local .dm1 file stored in the Active File directory, or due to persistent temporary table data issues. 

Steps To Fix This

  • Close the diagram in ER/Studio.
  • Find the file with Windows File Explorer in the Active File directory.
  • Rename the file or move it to another folder to back it up.
  • Back in ER/Studio, use Repository > Get Diagram to get a new copy of the file from the Repository.
  • Re-do the changes, or use compare/merge and submodel sync with the backed-up file to bring them into the new file.
  • Attempt the check-in again.

If you skip step 5 and the check-in still fails, then the corruption is in the Repository database. 

As a last resort, you can start over by using File > Save As to save the dm1 file with a different name and adding this new copy to the Repository. Be aware this action causes users to lose file history.

If you need additonal assistance, please contact Support.
Copyright © 2026 Idera, Inc.