nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

File not accessible

Ottawa_IWOV

All,

I have found a problem with TeamSite that I am sure others have encountered at some point. When I try and create a DCR with an identical DCR that has been deleted, and REMOVED from STAGING, I get "File not accessible" error. I am hoping there is a fix to this somehow. I can envision how this can be acceptable from a product like TeamSite. Hopefully I am just over looking something.

I anyone has some thoughts one this I would be happy to hear them

Thanks,

Lucas Cochrane

Lucas Cochrane
lcochrane@dc.com

Find more posts tagged with

Comments

webby

See the other thread in this forum called "Reusing DCR file names". I'm not sure, but it seems like a very old issue from TS 4.2.1 which has resurfaced.

nipper

Lucas

You are CERTAIN it has been removed from Staging ? Do a list modified, check the deleted files ? Any chance it is still there.

We see this here, but because the delete workflow has not completed yet.

ANdy

johnjamesmarsh

In order to get the deleted file into the Staging area you need to do a submit with the overwrite button checked. Have you done that on the directory or workarea where you deleted the files from?

Ottawa_IWOV

Does anyone know if this bug ("File not accessible") has been fixed in any TS 5.5.2 Service Packs (i.e. SP 4)?

Thanks.

Lucas.

Lucas Cochrane
lcochrane@dc.com

Migrateduser

If someone gets me a bugID I can check, but I don't really have enough to go on with what's posted here to do a good search. thanks.

lissa

gbarnett

My system is experiencing this issue also. We are running 5.5.2 SP4 with patch nt_ts552sp4_p46316 on Windows.

Any updates? What is the Bug ID?

Edited by gbarnett on 11/13/03 12:04 PM (server time).

Migrateduser

I found a bug id 43573 with this description:
Saving DCR with previous used name shows "This file is not accessible" message

Steps to reproduce:
---------------------
(As master Smiley Happy

1. Create new branch dev/demo.

2. Create a templatedata directory, copy some type into it.
3. File | New Data Record.
4. Save the DCR to templatedata/common/page/data/main.
5. Submit Direct.
6. File | Delete templatedata/common/page/data/main. (Not File | Delete Data Record.)
7. Submit Direct.

(As editor Smiley Happy

8. File | New Data Record.
9. Save the DCR to templatedata/common/page/data/main.

(Error results.)

Note that File | New File (to templatedata/common/page/data/main) works.

Please contact support if you wish to have your company notified of changes in the status of this bug. The bug was found in 5.5.2 SP3 and is still open according to the bug database.

Regards,

lissa

orb

One important point is that IF you are an IW master THEN you can create the new DCR.
Of course it could be dangerous to the integrity of your Interwoven instance to give
naive users IW master where they may accidentally run amuck...

Not really a solution but a note on this issue