iwlock error

I run this command from prompt: (TeamSite server 6.5)

\iw-home\bin>iwlock \default\main\ACS\WORKAREA\Main\TestContent\test1.html "grab" AXA-AP\ankur.kumar
ERROR:00001: Failure in operation

any ideas????

Same command works for other folders in same workarea:

\iw-home\bin>iwunlock "\default\main\ACS\WORKAREA\Main\Updates\Contact Centre Alert 2.html" "grab" AXA-AP\ankur.kumar

I logged in as administrator role.

Find more posts tagged with

Comments

Nicholas

Try below, I think you are missing double quotes

\iw-home\bin>iwlock "\default\main\ACS\WORKAREA\Main\TestContent\test1.html" "grab" AXA-AP\ankur.kumar

Thanks Nicholas

AXAMatt

\iw-home\bin>iwlock "\default\main\ACS\WORKAREA\Main\TestContent\test1.html" "grab" AXA-AP\ankur.kumar
ERROR:00001: Failure in operation

still doesn't work...

Nicholas

okay then try below.

1. Try adding -f for fource locking
2. check ownerid name is correct

Becoz same command I am able to run with win-TS6.5

Thanks Nicholas

Nicholas

One more thing, be sure your all teamsite services are running properly.

I suggest to restart once if problem still persist.

Thanks Nicholas

Adam Stoller

What version of TS are you using?

What happens if you run:

iwfilestate \default\main\ACS\WORKAREA\Main\TestContent\test1.html

Can you lock other files in the same workarea in the same directory with the same user? (perhaps its a permissions issue?)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

SubReport.rptdesign

AXAMatt

I tried it with -f option as well. It doesn't work.

I'm using admin user and I can lock any other file in any other folder.

Restart is not possible as it's PROD box.

Check attached screenshot.

Adam Stoller

The '-f' option is to force updating of the file before locking - it has nothing to do with forcing the lock (RTFM)
I'd prefer to see the output of iwfilestate than the screen shot - but my guess is that the GUI would show if the file was already locked too.

You're trying to lock it by using:

\iw-home\bin>iwlock "\default\main\ACS\WORKAREA\Main\TestContent\test1.html" "grab" AXA-AP\ankur.kumarWho are you logged in as when you run this command?
What roles are available for you when you login to the GUI?
Is ankur.kumar a member of the km_administrator or ContentDevelopers groups?
- if so, is it a recent addition or has the membership existed for some time?

Here's some info I'm about to use in a case with Support (you got me curious):

Environment:

I have 5 users:

'astoller' - all roles (me, who I'm logged in as on the command line)
'rcatabay' - all roles
'ated' - editor,admin,master
'wsgovae' - editor,admin
'auoese' - author

I have a file 'foo' sitting in my workarea - in my current working directory.

Two things stand out from the above:

http://www.quotient-inc.com

Adam Stoller

It's amazing what a night's sleep will provide ... last night, as I was trying to go to sleep, I realized my test case was severely flawed - and this morning I verified the flaw.

The workarea I was using yesterday was protected in such a way that I was the only user who had write access to it.

If I switch to a workarea which everyone can write into - then the results are significantly different:work > ls -ld .
drwxrwsr-x 7 2067 edwide 512 Apr 29 06:47 ./
work > id auoese
uid=909(auoese) gid=513(edwide)
work > id wsgoese
uid=949(wsgoese) gid=513(edwide)
work > id ated
uid=965(ated) gid=513(edwide)
work > id -a rcatabay
uid=2048(rcatabay) gid=10(staff) groups=513(edwide)
work > id -a astoller
uid=2072(astoller) gid=10(staff) groups=513(edwide)

work > touch foo
work > iwlockinfo foo
Lock does not exist.
work > iwlock foo test auoese
work > iwlockinfo foo
Name: foo
Area: work
Assignor: astoller
Assignee: auoese
State: Locked
Time Stamp: [Fri Apr 29 06:49:40 2005]
Comments: test
work > iwfilestate foo
foo
Conflict: No
Current: Yes
Modified: Yes
Editable: Yes
Locked by user auoese in workarea work
work > iwunlock foo
work > iwlock foo test wsgoese
work > iwfilestate foo
foo
Conflict: No
Current: Yes
Modified: Yes
Editable: Yes
Locked by user wsgoese in workarea work
...So - there are still some issues here, but nowhere near as serious as I was originally thinking or stating:

Why will iwlock allow me to assign a lock in my workarea to a master user who does not have write access but not to any other user who does not have write access? (I believe the former is a bug, the latter is correct behavior)
Why does iwlockinfo return the same results regardless of whether the master user has or doesn't have write access to the file?
Why does iwfilestate return different results depending on whether the lock assignee has or doesn't have write access to the file? (in this case, I believe iwfilestate is probably more correct than iwlockinfo)
The Permission Denied error message [for non-Master-users in protected workarea] is actually correct, but should probably be written up in more detail within the CLT manual as an example of an error condition

Given all this - my original questions still bear merit:

Who are you logged in as when you run this command?
What roles are available for you when you login to the GUI?
Is ankur.kumar a member of the km_administrator or ContentDevelopers groups?
- if so, is it a recent addition or has the membership existed for some time?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com