Suddenly one user can't save nor edit any DCR

This is my first post here, so first of all a friendly 'Hello' :-)

I am quite new to Teamsite Development, but I am assigned the basic user administration and templating tasks.

An error is occuring since yesterday I could not put my fingers on: One user (on Windows 2000 Server) suddenly can neither save nor edit & save any DCR - no matter in which folder he works. He has all rights and roles, they are correctly assigned to the folders. Actually any other user who has a similar configuration works fine.

This one however get's an error message:
"The DCR ... failed to save. Could the file be locked by someone else or locked in a different workarea."
Well, there is no lock. Problem keeps reoccuring after test-unlocking.

Again there is no difference to any other user; we did not change any configuration whatsoever. It "feels" like the user is "corrupted".
I did not try to delete and create a new user, because if this one was really corrupted it could result in major problems with the client (unexpectend failure of user accounts... "what the .....").

Does this all sound familiar to anyone here? Any comments are greatly appreciated; and please forgive my simple speaking as I still lack tons of TS expierence ;-)

Find more posts tagged with

Comments

rwinterpacht

This sounds familiar in our experience here at Household Intl. Did the user delete a dcr, and then try to recreate it?
Check this:

1. In TeamSite under the user's workarea, select View...List Modified.
2. Make sure that the dcr the user is trying to save is not listed as "DELETED" for files in the list.
3. If there is such a file, submit the deletion (hole.)
4. If not, is there someone else in the branch that has created, but not yet submitted, a file with the same name?
4. Try to recreate and save the dcr.

Hope this helps,
Raf Winterpacht

Adam Stoller

There might also be issues with the specific user's "entity" data within TeamSite - I believe there are some KBs on fixing issues with the entity db - but for your own sake, I'd suggest contacting Interwoven Support so that they can help you further diagnose and/or walk you through the steps of fixing this problem.

--fish
(Interwoven Senior Technical Consultant)

waldemar

Thanks for your hints...
Applying those procedures didn't help unfortunately.... Some day the account was ok again.... I suspect TS had some kind of hickups, that were "healed" during a reboot...

Bowker

We have had cases where the TS server has lost touch with the Windows domain security and couldn't associate SIDs with userids. It would happen often enough that we now reboot daily. The daily reboot also affords us the opportunity to clean up the logfiles by archiving them off and creating new ones. Editing 1gb log files is not my favorite thing to do.