Andy Brunner informed me a couple of days ago that using the “te amgr run” in a server program document command does no longer work after upgrading the server to Domino V10.
You will get an error message on the console similar to this one
Tell AMGr Run ‘LE4D.nsf’ ‘letsencrypt’
15.10.2018 07:24:11 AMgr: Start executing agent ‘ ‘ in ‘LE4D.nsf’
15.10.2018 07:24:11 AMgr: Error attempting to load agent ‘ ‘ in ‘LE4D.nsf’: Entry not found in index
I have created a case with IBM support. The case number is TS001489373 and the issue is tracked unter SPR# GFALB5NKTV.
The case has already been escalated to development and they are investigating the issue and I’m awaiting their feedback.
In the meantime, you can use the following workaround ( Thanks to Andy Brunner )
Create a text file on the server. The file can contain one or more lines where the syntax is the same as when you start an agent from the Domino console.
Tell AMgr Run “LE4D.nsf” ‘letsencrypt’
Next change your program document to use the text file as input
Hi Detlev,
it works fine if the nsf-path does not contain a blank. Then you can simply ommit the quotes around the nsf path:
server -c “tell amgr run admin/LE4D.nsf ‘letsencrypt'”
Works fine here with Domino 10 on CentOS. Or is it a pure Windows issue?
THAT is pretty cool. I tested on WIN & LIN. And even when you start the agent from the console, you can ommit the double quotes when there is no space in the FilePathName
What is the reason for using a program document instead of scheduled agent?
1) it is possiible
2) it is a valid way to schedule an agent
3) design of that specific application is hidden and the schedule cannot be changed using DDE
Er, having a space in the path and NOT using proper quotes has not worked for me since forever.
The documentation specifies double quotes around the database path and single quotes around the agent names.
Doing that in a program document poses a problem, since you also use quotes around the specification after the -c parameter. I’ve not had the opprtunity to test it. I’ll try that tonight.
tried escaping the reuired double quotes => no luck.
Great that a workaround exists by redirecting input!
Exactly that is the problem with V10. Prior to this version, you could use single quotes for the db filepath in a program document. But single quotes no longer work.