Error Element is not locked for edit with Teamwork Server

General discussions about teamwork

Moderator: Moderators

Error Element is not locked for edit with Teamwork Server

Postby twinpeaksJD » Tue Oct 27, 2020 1:32 pm

Versions:
    MagicDraw 19.0 SP3
    Teamwork Server 19.0 SP3 Windows 64

Issue:
    I have a collaboration project on teamwork sever that only I have access 2 (I control the server, I am the only one grated access). When I go to commit I get an error "Element is not locked for edit or locked by another user".


Items Tried without success
    I have locked the whole model, Issue remains
    I have confirmed in the lock view that I am the only one with anything locked
    I have released locks on anything that has not changed

Logs
    I have looked at the MD log and the TWS log and neither tells me what the artifact is that causes the issue. I have had this issue show up other timed and have not figured out the cause or how to fix other that discard changes. Any help would be greatly appreciated.

Thanks!
You do not have the required permissions to view the files attached to this post.
twinpeaksJD
Forum Beginner
Forum Beginner
 
Posts: 38
Posts Rating:3
Joined: Wed Jan 03, 2018 10:24 am

Re: Error Element is not locked for edit with Teamwork Server

Postby dakota.dunn@raytheon.com » Wed Mar 10, 2021 6:56 pm

I've receive this error as well in a TWS environment. Although no official answer, it appears that when you commit changes to the server, even though there is an error thrown up, the model does commit and the version in TWS increases by 1 with your change comments.

This must be some type of bug between Cameo and TWS. Even when you commit and it removes your locks, the model still believes you have something locked/unlocked with pending changes (as indicated by the blue text in the containment tree).

Unofficial possible solution: Commit changes as normal with comments. When the error is received, note current TWS version number, click okay, and check that the version has updated. You can also check the project history in TWS. If the model creates a new version, close the model (without saving if prompted) and reopen the model. Further commits should not throw the error at you.
dakota.dunn@raytheon.com
Forum Newbie
Forum Newbie
 
Posts: 2
Posts Rating:0
Joined: Wed Apr 08, 2020 3:15 pm


Return to Merging, branching, modules, team collaboration

Who is online

Users browsing this forum: No registered users and 1 guest