Strange authority problems with RunOnServer method

HCL Domino Domino Forum
1

I need the following function and I’m trying to use the RunOnServer method.- The user has Author access to the db.

  • The user has read-access to the document since he’s currently not listed in any AuthorNames field

  • The user need to change the document using an agent.

  • If possible; doing the above in a local replica as well.

I’ve tried having an agent (foreground) calling another agent using RunOnServer and also tried using a button with the RunOnServer call.

Whatever I try we’re getting “Notes error: You are not authorized to perform that operation”

Now to the strange part: The called agent works despite the Notes error message!

That is; the document is actually updated.

I’ve searched through various forum and gone through Julies articles and the FAQ many times but I’m obviously missing something.

Could someone please give an advice, suggestion, workaround or any other solution

TIA and regards, James

  • The called agent is set to run on: Event: Agent list selection with Target=None and a Runtime security level of 1 (we’ve tried level 2 also). The agent is signed by me and I can run any agent on the server.

  • The db has “Enforced consisten ACL” set (if that matters)

  • Client versions we’ve tried: 6.0.1 CF1 and 6.5.3

  • They have Author access in ACL without the ability to create any type of agents (if that matters)

  • Server is running 6.5.2 and everyone can “Run restricted LotusScript/Java agents”

2

Subject: Strange authority problems with RunOnServer method

What are you trying to accomplish? Are you trying to run the agent on the server? Where are you getting the error message? On the client or on the server?

Include the output of ‘test’ diagnostic for both of your agents, the answer will most likely be in the output window it display… and if not the rest of us might be able to have better theories if we can see that output.

3

Subject: RE: Strange authority problems with RunOnServer method

Thanks Rick for trying to help but I found out the problem had nothing to do with RunOnServer. Instead; it was because I used a document to pass data between the client and agent and it was the final attempt to delete that document, that failed because the users weren’t allowed to delete documents in the ACL.I’m now facing the problem to get rid of those temporary documents and I guess I could use another RunOnServer agent or perhaps schedule a normal agent to clean them out.