Editor and Documentum

[byork]

We arehaving a problem that has seemed to stump a few experts around here. Without going into a lot of detail it centers around checking in.

I am wonderingif anyone out hadany problems with checking in.

This is a hard one to describe but Ican go into much more detail if needed.

Thanks in advance

[naglists]

orphaned entities can do that. fix is a set command for the environment.
validating checkins in dctm can do it and some shops avoid that.
bugs related to the dctm adapter can do it. acl code that forces Default to
Changed fix that with a big honking hammer.

Versions, Desktop or Webtop, what error message or what happens that
shouldn't or what doesn't happen that should are the minimum sort of details
required for other than speculation.

[byork]

Paul,



Here is a screenshot of my structure that is causing problems checking
in.







When I go to check in I get an error.







As permissions go I have version permissions but not write on the all
objects except the book which I also have write access.



After I check in I will have new versions of all the objects except the
book which ends up staying checked out after the error.





I am using Editor 5.3 M040 and

Webtop version Build: 5.3.0.416 SP4 07 December 2006 DFC Version:
5.3.0.414 SP4



Thanks for your help.



Brian

[GarethOakes]

Hiya,



"No write access sysobject named ID000-068-425"



Sounds like a permissions problem to me. Try checking in the same structure
in a test area where you have full access.



Cheers,

Gareth

[naglists]

On Mon, Jul 21, 2008 at 5:07 AM, Brian York <-> wrote:

> Paul,
>
> Here is a screenshot of my structure that is causing problems checking in.
>
> When I go to check in I get an error.
>
>
> As permissions go I have version permissions but not write on the all
> objects except the book which I also have write access.
>
> After I check in I will have new versions of all the objects except the
> book which ends up staying checked out after the error.
>
> I am using Editor 5.3 M040 and
>
> Webtop version Build*: *5.3.0.416 SP4 07 December 2006 DFC Version*: *5.3.0.414
> SP4
>
I do not have a lot of webtop experience and we are not using an Arbortext
webtop adapter, so I can't tell whether that screen capture is from regular
webtop or the webtop adapter view (or if that is even a differentiation that
makes sense in the webtop world ... it does when comparing Documentum
Desktop to the Arbortext adapter designed for connecting directly to the
docbase).

That said, what happens if you remove Editor and the adapter from the
equation? What happens if you check out the virtual document and attempt to
check the document in all using webtop, no Arbortext products involved? If
you have success, then I'd say you have something for PTC/Arbortext support
(assuming from the responses so far there won't be much guidance from this
group). If you have a failure, then you'll need to chase Documentum as the
culprit.

--
Paul Nagai

[byork]

Paul,



The screenshot was from just the Documentum WebTop view. I'm pretty
sure it is a Documentum issue and something to do with permissions but
we can't isolate the culprit. If I login as a user that has full write
access to the object it will check in. The normal user should only
need version permissions to make this work.



We have the Documentum folks looking into this but they haven't found
out why yet either. I was hoping that maybe somebody would see this
post and say "I have seen this before you need to do this. 🙂 "



No luck so far.



Brian