Internal error in merging model changes. Please contact Tekla Structures support for instructions.
Not version-specific
Tekla Structures
Environment
Not environment-specific
Question:
I got this warning that says there is an internal error in merging model changes. Any idea what is happening?
Answer:
This error relates to multiuser mode, autosave, and using of several Tekla Structures sessions. We have noticed that this error happens in a situation where one user already has one multiuser session running and the same user starts another Tekla Structures session from autosave to the same multiuser model. After doing some changes in the first session and trying to save in both sessions, this error will appear and save is not working any more. At the moment this is not supported workflow. The recommended workflow is to load autosave only after ending the first session.
If you get this error, it is very probable that the normal save is not working in that session. Only thing you can try is to do save in another session where saving still works. You just need to close model without saving in the session where you get this error. It looks that the autosave from the error session is also corrupted, and you cannot use it for saving your work.
Since versions 21.0 SR9, 21.1 SR8, 2016 SP6, 2016 SP3, and 2017 we have prevented the opening of another multiuser session from autosave. The error message is "Could not load autosave, the folder is locked by other session".
I got this warning that says there is an internal error in merging model changes. Any idea what is happening?
Answer:
This error relates to multiuser mode, autosave, and using of several Tekla Structures sessions. We have noticed that this error happens in a situation where one user already has one multiuser session running and the same user starts another Tekla Structures session from autosave to the same multiuser model. After doing some changes in the first session and trying to save in both sessions, this error will appear and save is not working any more. At the moment this is not supported workflow. The recommended workflow is to load autosave only after ending the first session.
If you get this error, it is very probable that the normal save is not working in that session. Only thing you can try is to do save in another session where saving still works. You just need to close model without saving in the session where you get this error. It looks that the autosave from the error session is also corrupted, and you cannot use it for saving your work.
Since versions 21.0 SR9, 21.1 SR8, 2016 SP6, 2016 SP3, and 2017 we have prevented the opening of another multiuser session from autosave. The error message is "Could not load autosave, the folder is locked by other session".