Marked for Deletion icon in TS

Hi there,

Can someone explain how I can permanently remove a folder (and its subfolders and files) from within my templatedata directory in TeamSite. The 'category' folder was previously submitted to STAGING, but is no longer needed and I wish to remove it from my workarea and from STAGING.

Unfortunately after trying several times, from several workareas, to delete and Submit to staging, and also Get Latest, I keep getting prompted about Files in Conflict - my favorite folder friend being listed as the offender.

How can I zap that pesky little guy? Any advice would certainly be appreciated - thx.

cb

Find more posts tagged with

Comments

Adam Stoller

Hi there,

Can someone explain how I can permanently remove a folder (and its subfolders and files) from within my templatedata directory in TeamSite. The 'category' folder was previously submitted to STAGING, but is no longer needed and I wish to remove it from my workarea and from STAGING.

Unfortunately after trying several times, from several workareas, to delete and Submit to staging, and also Get Latest, I keep getting prompted about Files in Conflict - my favorite folder friend being listed as the offender.

How can I zap that pesky little guy? Any advice would certainly be appreciated - thx.

cb

If there is a conflict perceived - then the submit never completed - you need to make sure you enable the overwrite option when submitting (either within the GUI or via the command line) the deletions from the workarea.

You should also check - before doing this - whether anyone has any of the files locked within that directory - if so - you should remove the locks first before submitting - because TS has a tendency to not do this automatically and then it ends up causing problems later on.

You may want to try submitting the deletion of each file in the directory separately so as to clear away any files that don't have conflict issues - and then see what you're left with. When you get all the files deleted you should be able to delete and submit the directory.

octogon

Thanks, fish, for your response. I haven't tried the command line method of submitting the files, only via the TeamSite gui. There are only two workareas, and the folder with its subfolders/files have been deleted in each workarea. The offending folder is a 'category' under templatedata, with two 'type' folders and datacapture.cfg files beneath that. The only place these files and folders appear to exist is in the STAGING area. Both workareas show that same dang folder icon as 'Marked for Deletion'.

I've tried submitting from both workareas, with Overwrite Conflicts enabled. However, the folder just won't go away.

:eek:

Adam Stoller

Thanks, fish, for your response. I haven't tried the command line method of submitting the files, only via the TeamSite gui. There are only two workareas, and the folder with its subfolders/files have been deleted in each workarea. The offending folder is a 'category' under templatedata, with two 'type' folders and datacapture.cfg files beneath that. The only place these files and folders appear to exist is in the STAGING area. Both workareas show that same dang folder icon as 'Marked for Deletion'.

I've tried submitting from both workareas, with Overwrite Conflicts enabled. However, the folder just won't go away.

:eek:

You can try restoring / reverting the deletions in one (or both) workareas and then explicitly go through and unlock all files within - and then try deleting the folders again - and/or you can try contacting IWOV Support - I believe they have a utility for finding "stale locks" or some such that might also help you work around this problem.

nipper

This is always a pain and it is easy to get TS confused. If you have deleted in both WAs then you have a conflict, even though it is the same.

Do a get latest in each workarea and get whatever is in staging. Make certain you overwrite your deletes.

In one workarea check for locks for all sub dirs and files. Remove any. Check the second WA to be certain but there should be no locks.

Then remove files. Submit. Go up a folder. Submit. Repeat.

This is slow but should do what you need.

HTH

Andy

octogon

Thanks for the advice guys. I did try Nipper's method - getting latest from Staging, overwriting the workarea. No locks visible in either workarea, and I delete content within each workarea file by file, starting with the deepest files. The files delete normally, but the very first subdirectory that I try to delete and submit shows up as 'Marked for Deletion', and just won't go away. I'm not much of a Unix guy, but perhaps this could be a Unix permissions problem - group permissions and such?

As Fish suggested, I will try to contact InterWoven support about a possible utility if this thread doesn't provide any more suggestions.

Thanks again!

Smiley Happy

sivaramiyer

i m also facing similar issue.

octagon: Can you please write across what exactly you did to resolve.

sivaram

lizb

Hi

I as well am having the same problem with TS 6.7.1.

Did either of you resolve this?

Let me know, Thanks

abhijeet1

Same problem. Anyone find a solution for this. We are running TS 671 on Solaris. Used to be, you just copied the files back to the WORKAREA from STAGING, using the copyto option and submit direct with overrides.

abhijeet

moonkhanna

good one.. I faced a similar issue as short while ago.. There must be some stale locks on the file.. probably someone will be able to provide you with unlock script for stale locks..

slarty

I am having a similar problem also. A colleague submitted some deletes (which includes deleting a directory). A file was locked however, which created a conflict. She then unlocked the offending file, and in the "Task Details" pane of the Submit task, she hit the "Resolve Conflicts" button (selecting to "overwrite all"). The deletes did physically work but, the problem is that the task won't complete, and it still has the "conflicts" flag.

Interestingly, when you hit the "Resolve Conflicts" button, it says "0 out of 6 conflicts", yet it still flags it as a conflict.

Does anyone know how to "force" the task to complete? (i.e. make that annoying little red flag go away :-).

Also, there is an interesting article in the Interwoven knowledge base about some problems deleting folders with TS 6.5 SP1:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=54520

It might assist in shedding some light on this issue for you.

Sailesh

This looks like a issue of stale locks where lock is still there on the file though it is been deleted.

But believe this issue was resolved long time back, to be safe better option is to run iwstalelock utility and unlock all files then do a submit. If this problem persist add a menu item which will unlock all files for you in a workarea.

abhijeet1

Cannot find any utility called iwstalelock anywhere under teamsite install. Is it supposed to be there. Using teamiste 671

abhijeet

Adam Stoller

Cannot find any utility called iwstalelock anywhere under teamsite install. Is it supposed to be there. Using teamiste 671

abhijeet

I think you may need to contact IWOV Support for it....

abhijeet1

I think you may need to contact IWOV Support for it....

Thx. Will do

abhijeet

rodigz

Run this command:

/bin/iwstalelocks /default/main/branch_name /default > /tmp/stale_locks_results.txt 2>&1

This will redirect the output to a text file - this is a list of files, including the full path, of files with stale locks in that branch. You may get a 998 error when you run the command, which can be safely ignored.

Once you have the list of files, run this command on each one that is reported to be in the deleted folder:

/bin/iwunlock /default/main/path_to_the_file/test.txt, where test.txt is the file that contains a stale lock.

nipper

Run this command:

/bin/iwstalelocks /default/main/branch_name /default > /tmp/stale_locks_results.txt 2>&1

This will redirect the output to a text file - this is a list of files, including the full path, of files with stale locks in that branch. You may get a 998 error when you run the command, which can be safely ignored.

Once you have the list of files, run this command on each one that is reported to be in the deleted folder:

/bin/iwunlock /default/main/path_to_the_file/test.txt, where test.txt is the file that contains a stale lock.

This is done AFTER you get the command from support. iwstalelocks is not part of the normal TS release.

slarty

[For my own education and experience gathering]: Would love to know what actually constitutes a "stale lock". Can a stale lock be safely unlocked in all cases, or is there a case where a stale lock is meant to be locked?

octogon

Hi guys,

Sorry I didn't post my solution earlier, once I 'solved' the problem I didn't come back in here until today...

Unfortunately, my 'solution' probably won't be one that many other people can use. Since this was a relatively small TeamSite project (20 or so HTML pages plus supporting files), I ended up just creating a new Branch for the project. I downloaded all of my content from the offending (old) branch, uploaded it to the new Branch, then deleted the old branch that was no longer needed.

Not an elegant solution, but it solved my little problem. :eek:

Sorry I couldn't post a resolution that would be more useful - I know how frustrating this particular bag of bones is.

Good luck!

cb

moonkhanna

Octogon - good short term solution but you may face the issue again. If I would have been in your place, I would have logged this with Iwov support, got an unlock script from them and got it logged as a bug probably..

As good question is - Where do these stale locks come from? Maybe files deleted when they are attached to a workflow? Anyone who can test it ?

beez

A "stale lock" is a lock that references a nonexistent file. A bug in TeamSite (fixed in 6.5SP3 and upcoming TS6.7.1SP1) created these stale locks when a directory containing a locked file was deleted and submitted.

--Mike

moonkhanna

Mike, this is not true. This does not happen everytime you delete a directory containing locked file and submit. This is something else. I think, when some file is locked by a workflow and we delete it...kind of a thing..

Sample.pdf

rptPurchaseOrderTmp.rptdesign