Error 1

[balakumar86]

Hi,

We have given full permission to one account in a particular folder. When we try to access that folder by logging into that account, we get the error

Livelink Error: Error browsing the specified object.
[No permissions to access the attribute definition node.]


Any idea about this error?

Regards,
Bala

 

[balakumar86]

Now, I tried to modify the privileges of that account by logging in as admin. When I tried to alter it, I get another error.

Livelink Error: Error saving User.
[Error changing the user's privileges. (662306825)]
---->Error Stack
----> 1) E662306825: You cannot grant more privileges than the current user.

Any thoughts??

 

[appnair]

if you are running dirsvcs temporarily change it back to LL Authentication and do what you need to do as logging in as 'Admin' or if you have a back door admin account use that to troubleshoot.If you think you have done everything accordingly then put logs on and send it to OT support.Sometimes the user created may have no "Public Access" and the categories volume may not be permissioned correctly that is my guess with the attribute definition error

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer and probably certfiable,Livelink ECM Champion 2008

http://www.linkedin.com/in/appunair

 

[balakumar86]

Hi Appnair,

I switched on the Conenct log and found out that the sql is trying to access today's recycle bin. Not sure Y.. I have pasted a part of connect log

05/07/2009 10:02:04 [4144520002] 0000067589: KSqlCursor::Open(201f,'select Permissions from DTreeACL where (DataID=:A1) and (ACLType=0 or ACLType=3) and (RightID in (100058268,100058815))') -->'SUCCESS'
05/07/2009 10:02:04 [4144520039] 0000067590: KSqlCursor:repare() --> 'SUCCESS'
05/07/2009 10:02:04 [4144520067] 0000067591: KSqlCursor::Bind(1,{100063426}) --> 'SUCCESS'
05/07/2009 10:02:04 [4144520691] 0000067592: KSqlCursor::Execute({'PERMISSIONS'}) --> 'SUCCESS'
05/07/2009 10:02:04 [4144520736] 0000067593: KSqlCursor::Close() --> 'SUCCESS'
05/07/2009 10:02:04 [4144520769] 0000067594: KSql::Execute(...) --> 'SUCCESS',0 records,[sec: 0 msec: 1]
05/07/2009 10:02:04 [4144520859] 0000067595: KConnect::ErrLog --> [10105,3],'Read Accessibility error. Not enough permissions.'
05/07/2009 10:02:04 [4144520922] 0000067596: KSTree::GetByID(0,100063426) --> 'Read Accessibility error. Not enough permissions.',TRUE,FALSE

where 10006326 -> Object ID of the today's recycle bin folder
100058268,100058815 -> 1st one is Kuaf ID of the account which is getting the erro and the 2nd one is the group to which this account is added.

This account has only Login enabled. If we enable Public access, wedon't get this error.

Any idea?

Regards,
Bala

 

[appnair]

you should understand this if you have worked in livelink for sometime.When you create a user in Livelink the only two privileges the account has is "Login Enabled" and "Public Access".This is by design so that several volumes do not need to be explicitly permissioned.The categories volume has "PA" and if the calling user has "PA" then LL shows the category definition.The Search slices have PA that is why they can search on them.If your organization has a policy of not giving "PA" to a user then all volumes,containers need to be permissioned correctly.OpenText does not need Public Access but if the user cannot access his/her "Recycle Bin" how can they be blamed.These rules are applicable to workflow attchments volumes also.

Whenever I create a account with no "PA" I make sure the
touch points have been correctly permissioned.

Take a look and analyze the problem correctly.If needed use support at opentext dot com.

My USD 0.02

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer and probably certfiable,Livelink ECM Champion 2008

http://www.linkedin.com/in/appunair

 

[balakumar86]

Thanks Appnair. That was helpful. We have 3 groups that have access to all the volumes in livelink. So, what i needed to do was to add the group of this account to any of those 3 groups which resolved the issue.