Out Of Office - Enable Problem

OK, I’m not sure what the issue is here - whenever a user has Manager rights to their mail file, Out-of-Office enables immediately. If they have Editor rights, however, the following message appears:

“A request to enable the Out of Office agent is in progress. Please wait momentarily for the server to enable the agent.”

The thing is, that message never goes away and the agent is never enabled. Once again, though, the agent enables immediately for users with Manager access.

Any ideas?

Thanks,

Justin

Subject: Out Of Office - Enable Problem

Check the admin4.nsf and see if there are errors there. AdminP requests are generated for Editors to run their OOO agents. For Managers, you don’t have that middle man type of process.

Subject: Out Of Office - Enable Problem

I’ve seen the exact same error, except that the user has Manager rights to his mailfile. The only way OOO can be enabled is via iNotes. I called IBM and they had no idea why it happened.

Thanks,

Dave

Subject: RE: Out Of Office - Enable Problem

Have a look at the server document. The user needs to be able execute Lotus Script Agents. Look at the “Run restricted LotusScript/Java agents:” field. I usually put in wild card */OurOrganisation in here.

Also try re-signing the database with watever ID you use to sign database, either a dedicated Agent Signer ID, or the Server ID.

Subject: RE: Out Of Office - Enable Problem

My users were having the same problem and also seeing the following error in the Status Bar “Notes error: 4000 Notes error: You are not authorised to perform that operation”

I fixed it by:

  1. Enabling “Allow User Activation” in the OOO Agent Properties (Key Tab)

  2. Ensuring the users had “Depositor” access to the Admin Requests database

Subject: RE: Out Of Office - Enable Problem

The problem is that this problem is not consistent across all users on the same mail server. Some can enable OOO, others cannot.

Thanks.

Subject: RE: Out Of Office - Enable Problem

Editor level users do not need to be listed in “Run restricted LotusScript/Java agents”. But the entity that signed the agent should have the rights to sign the agent on behalf of other users (new to R6 security field). The server id or Lotus Notes Template signer also have that right even when not explicitly listed. But if you resigned the template with your own id, make sure it was added to the Domino Directory in that field.