"Couldn't read DCR file [unable_to_read_dcr ] " errir occured while Editing the file in TeamSite

Details:

TeamSite Version 6.5

Windows Server 2003 with SP2 on Quad-Core AMD Opteron(tm) Processor 8360 SE at 2.51GHz AT/At Compatible 15 GB of RAM hardware.

VM Ware Platfrom

In our environment, We have huge number of Workareas in TeamSite and Each Workarea has huge number of Editions.

Recently we have deleted certain number(large - in 100's) of Editions through TeamSite UI.

Now, When we try to do an Edit operation on the file belonging to the same Workarea where we have deleted the Edition, we getting following error - "

unable_to_read_dcr

Root cause:
Couldn't read DCR file [unable_to_read_dcr ]:Exception thrown while trying to read document from server

Details...

com.interwoven.ui.formspub.datacapture.EditDCRPredicate$ReadDCRException: Couldn't read DCR file [unable_to_read_dcr ]:Exception thrown while trying to read document from server
at com.interwoven.ui.formspub.datacapture.util.ContentServicesUtil.readSimpleFile(ContentServicesUtil.java:67)
at com.interwoven.ui.formspub.datacapture.EditDCRPredicate.readDCRContents(EditDCRPredicate.java:101)
at com.interwoven.ui.formspub.datacapture.EditDCRPredicate.execute(EditDCRPredicate.java:60)

P S:

Batch jobs for the Deleting Edition is still running in the serve while we try to edit the file .

Is this Causing the issue?

Can you please suggest on this.

Thanks in advance

Regards,

Shwetha

Find more posts tagged with

Comments

Adam Stoller

shwethabhat wrote:
Details:
TeamSite Version 6.5
Windows Server 2003 with SP2 on Quad-Core AMD Opteron(tm) Processor 8360 SE at 2.51GHz AT/At Compatible 15 GB of RAM hardware.
VM Ware Platfrom

6.5 is no longer a supported version of the product - you should be looking at upgrading soon

shwethabhat wrote:
In our environment, We have huge number of Workareas in TeamSite and Each Workarea has huge number of Editions.
Recently we have deleted certain number(large - in 100's) of Editions through TeamSite UI.

Workareas do not have editions, branches have both workareas and editions.

Are you saying that you have a lot of branches with a large number of editions? or that you have a large number of branches each of which contain a large number of workareas? or both?

shwethabhat wrote:
Now, When we try to do an Edit operation on the file belonging to the same Workarea where we have deleted the Edition, we getting following error - "
...
P S:
Batch jobs for the Deleting Edition is still running in the serve while we try to edit the file .
Is this Causing the issue?

Can you please suggest on this.

Most likely the edition deletion process is causing some, if not all, of the issue here. Despite the fact that your software is woefully out-of-date, you should try contacting Support to see if they can help you out of this problem.

The best suggestion I can offer is for you to shut everything down and replace the backing store with a recent backup copy (you do have a recent backup - yes?) and see if the problem "goes away" - if so, continue from there and do not try to do mass-deletion of editions.

shwethabhat

Thanks alot for the response.

Yeah, we have lot of branches with a large number of editions.

As this Edition deletion causes the disc (mount) failure? Or any Performance issue in the TeamSite server?

As we don't have recent back up of the Content Store, Can we stop the batch jobs(For Edition Deletion) which is causing the issue by "iwabort" command.

Please suggest your inputs.

Regards,

Shewtha

Adam Stoller

The edition deletion process is most likely causing performance issues - the degree to which you will notice it depends on the beefiness of your system. Whether or not it is the source of the backing store mounting / unmounting issues I don't know.

You can try to abort the edition deletion commands with iwabort - but (a) it doesn't work all the time - I believe it depends on what stage the command is in, (b) it doesn't work "immediately" - it sometimes "queues" the request to abort until the process is in a stage where it can do so, and (c) it is possible that you may end up leaving your backing store in a questionable state.

The fact that you don't have a recent backup should be sending alarms to you and your bosses...

The fastest but most distasteful solution would be:

For each content branch

Take a surface copy (tar file, zip file, etc.) of every file in the staging area
Take a surface copy (tar file, zip file, etc.) of every [modified] file in each workarea (hopefully there's only one per branch - try using the output from iwlistmod to copy just the files which are currently modified)

Get a complete branch and workarea listing (home-grown script utilizing iwlist or whatever you want)

Get a complete access-rights listsing (iwaccess export-permission-entries file)

Stop all TeamSite services

Move (or remove) the IWSTORE/default directory

Start all TeamSite services (or just reboot the server - which should accomplish the same thing)

Re-create all the branches and workareas (home-grown script or manual process)

Reapply the permissions on the branches and workareas (iwaccess import-permission-entries file)

For each content branch

Restore the files from the surface copy of the staging area into the workarea
Submit the files

If you have multiple workareas on a branch, make sure to do a Get Latest (or iwupdate) for each additional workarea on the branch.

Create a named edition (iwpublish or through UI)
Restore the modified files from the surface copy of the workarea(s) into the workarea(s)

Make sure you have a proper backup strategy in place so that you don't have to go through this mess again (for any reason)

Put in place home-grown processes for maintaining a limit on the number of editions on each branch (if desired)

Resume "normal" activities