Issue with a particular file deletion

A file without any extention has been created and submitted to staging.

Subsequently attempts to deleted the same through the submit workflow is failing throwing errors like "Checked out files prevent submitting" and the workflow is stuck at the "Resolve conflict" task.

The context file is nither locked nor open for edit. Attempted doing a getlatest and then deletion but status co reamins.

Please advice.

Find more posts tagged with

Comments

Frederik

mmm, this error does indeed usually indicate file is locked - although you indicate it isn't. Are you sure it isn't locked e.g. in another WA? Are there any other files submitted at the same time, that could be locked?

Teamsite version and platform?

Antharix

The file is available in only one workarea. I have tried to unlock the file as administrator and then tried to delete.This file is submitted individually and there are not other Submit tasks triggered at that time.

TS 6.5 sp1
solaris 8

example.jpg

Adam Stoller

The file is available in only one workarea. I have tried to unlock the file as administrator and then tried to delete.This file is submitted individually and there are not other Submit tasks triggered at that time.

TS 6.5 sp1
solaris 8

Try doing an iwrlog and iwfilestate of the file in both the workarea and the staging area and examine the output carefully. If that doesn't help, you may post the output (as attachments preferably) - but please, only after you've looked at them yourself.

Also - when was the last time you tried running iwfsck on your backing store?

13adam13

The file is available in only one workarea.

Does this mean that there is only one workarea for that branch, or that there are several workareas on the branch, but only one of them has a copy of the file in it?

The file could have existed in another workarea, been locked in that workarea, and then deleted out of that workarea. If this happened, the file would remain locked, though it is not visible through the UI (usually).

Antharix

Try doing an iwrlog and iwfilestate of the file in both the workarea and the staging area and examine the output carefully. If that doesn't help, you may post the output (as attachments preferably) - but please, only after you've looked at them yourself.

Also - when was the last time you tried running iwfsck on your backing store?

I did not find much infor on executing the iwrlog and iwfilestat commands on this file. I did a get latest on the file and then executed the above scripts as the file was deleted in the WA.

The outputs of executing the iwrlog and iwfilestat, are captured in the attached files .

Please advice

Adam Stoller

I did not find much infor on executing the iwrlog and iwfilestat commands on this file. I did a get latest on the file and then executed the above scripts as the file was deleted in the WA.

The outputs of executing the iwrlog and iwfilestat, are captured in the attached files .

Please advice

Hmm - I don't have an active server to look at right now (I was pretty sure those commands would provide more information, but ...)

There's still a remaining question - when did you last run iwfsck -d on your backing store? This would help show, or eliminate, data inconsistencies from the list of variables that could be involved in what you're seeing.