Import Error - File Already Locked in WA

I have a scenario that is just baffling me. I am trying to Import some files into a workarea. The workarea has one file in it (.DS_Store), which is marked as modified and unlocked. There are no other files in the workarea. There are no files in STAGING. When I execute the Import I get a pop-up stating:

Error importing file foo.bar to TeamSite server:
File is already locked in workarea integration by nmbsde

Where nmbsde is a valid user on the system. Problem is, that file doesn't exist at all in the workarea and when I list locked files, it shows no files are locked. This is really frustrating. It's repeatable. Any idea why this might be happening?

TeamSite 6.1 SP2
Solaris

Find more posts tagged with

Comments

nipper

It does not like you ?

No idea why, but you may try creating the file on the server, then see if you can unlock it.

Any editions ? Maybe a deleted directory with the same name ?

Migrateduser

It pains me to say this, but....

er....ugh....thank you nipper...that seemed to....uh....er.....work....

Dude...that worked, but WTF? I guess it's best not to question the irrational behavior of a tight system like TeamSite.

Every time I think I'm out....they pull me back in...

Thanks, man...you've maintained your hero status with me...

nipper

Can you say that a little louder, I did not quite hear you. Smiley Very Happy

Migrateduser

So....would this scenario possibly happen if someone had, at some point prior to today, created those files, where they would then be locked. Then the person deleted those files before they were ever submitted to STAGING - and before ever unlocking them? Is TeamSite smart enough (or dumb enough as the case may be) to remember those files existing once and being locked? Does deleting a file therefore not delete the file lock? Bug? Anyone?

nipper

So....would this scenario possibly happen if someone had, at some point prior to today, created those files, where they would then be locked. Then the person deleted those files before they were ever submitted to STAGING - and before ever unlocking them? Is TeamSite smart enough (or dumb enough as the case may be) to remember those files existing once and being locked? Does deleting a file therefore not delete the file lock? Bug? Anyone?

If someone imported the file and then deleted it outside (say from Unix or DOS commandline) then the backingstore probably would not go through and remove the lock. If you deleted it from the GUI it will remove the lock. Just speculation, but it sounds good to me.

Stick around, this place is boring without you. Ghoti is the one who tends to offend people now.

Migrateduser

Maybe I deleted the thing from the filesystem. Whoops. Thanks for the help.

I see that Ghoti has something like 10000 posts now. That is just insane. Is he just trying to find out which gemstone he gets when he hits 10000?

Adam Stoller

Maybe I deleted the thing from the filesystem. Whoops. Thanks for the help.

I see that Ghoti has something like 10000 posts now. That is just insane. Is he just trying to find out which gemstone he gets when he hits 10000?

Welcome back - we've missed a lot of the rantings while you were gone ;-)

I haven't gotten to 10K yet (by the way - you might want to fix your signature and change [red]...[/red] to [color=red]...[/color=red]).

FWIW - a number of folks have indicated bugs with respect to the way TS (doesn't) clean up locks on deleted files / files in deleted workareas. I'm not sure what, if any, bug IDs were filed for this though (I haven't run into this recently so I don't have that data personally handy).

If you search the forums you might find some of the threads regarding this mis-feature.

Frederik

FWIW - a number of folks have indicated bugs with respect to the way TS (doesn't) clean up locks on deleted files / files in deleted workareas. I'm not sure what, if any, bug IDs were filed for this though (I haven't run into this recently so I don't have that data personally handy).

Yeah, I'm pretty sure having noticed this behaviour too in our TS 5.5.2 sp4 which we had for a couple of years before upgrading to TS 6.5 sp2.

I haven't seen this any more in TS 6.5 and the other day I came across a scenario where I was pretty sure that a "stale" lock would have been left in 5.5.2, yet it wasn't there in 6.5. This really is just anecdotal evidence, till someone (or I) manage to test more formally.

--Fred.