SizeQuota change by Schedule agent issue

I have a server-side schedule agent that’s designed to change the size quota of a database on another server. Both servers are running 8.0.2 and the target server trusts the server running the agent via a reference to the server name in the “trusted servers” field on the target server’s NAB entry. In addition the source server, the agent signer, and the target server all have manager access to the target database whose quota is being modified.

When ran, the agent opens the target db on the remote server, reads the quota value, and seems to have Manager access to the database (according to property db.currentaccesslevel). However, when attempting to modify the quota value (via a call to db.sizequota=x) I get the error “4005: Notes error: You are not authorized to perform that operation”.

I’ve increased the agent signer’s authority to allow unrestricted operations on both the agent host server and the target server. I’ve also changed the agent properties to allow unrestricted operations but I still get the same error message.

The agent runs OK from a Notes client, and OK server-side as long as the target is not on a remote server.

None of the online documentation I’ve found that discusses remote agents mentions any restrictions on operations of this sort but I’m wondering whether it’s a limitation of the security protocol that’s implemented which means this sort of operation isn’t allowed.

Any ideas would be appreciated! :slight_smile:

Warm regards!

Subject: Server access level ?

Hi,

Does the agent signer has Administrator access to the server ?

At least according to the documentation this is needed.

I have a quite similar problem.

My code works properly on a cluster and set the quota on both nodes whilst running on the first one.

But, on another cluster, it does not. I get the same 4005 error as you do.

I have agent signer and server have managers access to the db, admin access to the server and rigth to run unrestricted code this on all the 4 servers (the working cluster plus the non working cluster).

Other weird thing, according to my error trap code, the error happens line 19 … which contains the “else” instruction solely :confused:

Still searching for a solution… if you got one in the meantime, could you please post it ?