| > |
|
Hmmm, this can be a lot of reasons. Apparently a certain action is being done that you are allowed to do, but when the agent runs scheduled on the server, with the ID it is signed, that action is not allowed.
So, first things first.
- If somewhere in your code, you are looking up values from a database that is located on a different server, it will not work. A scheduled agent is not allowed to lookup values on another server. This problem is somewhat resolved in R6.
- A scheduled agent written with LotusScript cannot execute any notesUi objects. So, if in the code you refer to any object like that, for instance notesUiWorkspace, your agent will not work either.
- The ID the agent is signed with has no access to the database where you lookup the values, or has no access to create documents. Check the ID the agent is signed with and look in the server document in the Security tab, if it is allowed to run agents properly.
- Should the agent be signed with the server ID, check if the server can execute agents. If so, try changing the access control level of the server in the ACL of the database where the documents are created into the type "unspecified" or "person" and make sure it is allowed to create documents.
As you can see a lot of reasons are possible, but the common thread here is security.
|
|
