lock file not found from Draft copy

[Anonymous]

I somehow got locked out of the teamwork file after taking a draft copy home and working on it. When opening the draft and signing in I get a message that a lock file has been corrupted and should be trashed. the lock file does not exist. It can't be found anywhere. What do I do? Do I trash the Admin file? How do I reconnect to my project. I have not signed out of the file at all.

I am using AC 7 and working on a Mac G4 667 powerbook.

Thanks much!

[Miquel Garcia]

The lock file is a file with an .lck extension. It must be placed near your admin file.

The best way that i have found in failure events is to save the draft copy as a solo project and then share it again as a Teamwork project. This will run except if other team members have been working on their own copy. In this case you will need to check every drawing.

[David Larrew]

Be careful saving out solo .PLN files from standard Teammate workspace .PLC files. When you save out the .PLN file it saves exactly what you are signed-into.

You might find elements, layers, stories, etc. that you cannot access in the .PLN file due to the fact that they were not part of the active workspace before the conversion.

At least that is what we experienced in AC 7.0. I haven't tested AC 8.1 yet.

[__archiben]

David wrote:
Be careful saving out solo .PLN files from standard Teammate workspace .PLC files. When you save out the .PLN file it saves exactly what you are signed-into.

You might find elements, layers, stories, etc. that you cannot access in the .PLN file due to the fact that they were not part of the active workspace before the conversion.

At least that is what we experienced in AC 7.0. I haven't tested AC 8.1 yet.

david

this is strange! i have never experienced that with 6.5 or 8+ . . .

when i save a solo file out of a teamwork draft, it creates a proper, fully-accessible, .PLN file. i've never found that i can't work on something?!

as i said; this has been 6.5 and 8+ (we skipped 7), but it does seem very strange.

~/archiben

[David Larrew]

We use Teamwork on 99.5% of the projects (+500 projects/year) in our office (77+/- licenses). We've stumbled across MANY bugs and unexplainable issues that no one else has experienced. I think this issue depends on how the file is being shared (layers/stories/marquee defined workspaces) and how many teammates are signed-in at the time.