The file is already locked by you in workarea

I use Teamsite 6.1. I have a problem that occurs only with certain workflows and only when logged in to Standard, not Professional, content center. I create a new job, add a new form, enter some data, save it, and close the form. This returns me to the Task Detail page and the dcr has been attached. If I then try to edit the dcr, I get the following error message: The file **** is already locked by you in workarea yyy

This doesn't happen if I don't use a workflow (i.e. skip the New Job part).
This doesn't happen if I log into the Professional content center.
This doesn't happen when editing an existing file.
This happens with some workflows but not others and I can't see what the difference is.

I've only seen one other post reporting a similar problem, so I don't think it is a bug - I think I have something set up incorrectly.

Any ideas?

Find more posts tagged with

Comments

Valentine

Are you using CCI urls?

I had this happen to me, when the server name part in the vpath, was different from the server I've logged in to

ie.

logged in
http://cms.company.com/

CCI url /iw-cc/blah?vpath=//cms/default/xxxxxxxx

Chloe

I hate to admit it by I'm not sure what the term "CCI urls" means. However, I checked the server name issue you mentionned. The server name we log into is the same as the server name in the URL when you click the Edit link and the server name in the vpath, so I don't think that is the cause.

A coworked just found an odd workaround. If you are on the Task Detail screen and click the Versions link and then click Edit on that popup screen, you can edit the dcr! The main difference between the URL behind the Edit link on the Task Details page and the URL behind the Edit link on the Versions page is that the one on the Task Details page runs /iw-cc/command/iw.group.ccstd.edit_dialog and the one on the Versions page runs /iw-cc/command/iw.group.ccstd.edit.

export.png

Chloe

Found the problem. In the workflow, there is a place where I set the areavpath variable. I had an uppercase "a" where I should have had a lowercase "a" in the variable's value. Not sure why this didn't cause a problem in Professional Mode, but it fixed the issue in Standard Mode.