I am running into a problem with Scheduled Agents and would appreciate any help.
I have 2 ahents. #1 is a Java agent and #2 is a LS agent
Java agent generates a data file and calls the LS agent to read file and ultimately build a Symphony Spreadsheet. LS agent has %include SYMPHONYLSX.LSS
While testing, I can manually run the Java agent and it successfully calls the LS agent which generates the Symphony Spreadsheet. All is godd.
If I set the Java agent up as a scheduled agent (currently set as a local agent on my Notes Client) - the Java agent runs correctly and generates the data file.
I receive the following error message via a Popup window
ntaskldr.exe - Unable to locate Component
The application has failed to start because sal3.dll was not found. re-installing the application may fix this problem
I have placed sal3.dll in my Path but still get the error
Is there anything else I need to do to get the Java agent to call the LS agent successfully as a scheduled agent
Subject: Have you looked at checking the security attributes of the agent?
Hello,
A client of ours had a same similar issue however it was with a LS Agent calling a Java Agent, then invoking an unzip program (7z). It worked fine if manually run from the client but when scheduled on the server using Amgr it didn’t work, presumably due to the way background agents work compared to foreground agents which can invoke UI elements.
I see you tried ensuring it’s in your path, however have you tried ensuring that the agents run with full security? My feeling is the symphony spreadsheet creation process relies on whatever invoking process having a valid Windows handle (background agents have none).
Where did you see the following error?
"The application has failed to start because sal3.dll was not found. re-installing the application may fix this problem"
Did you pull that from the agent log? what version of OpenOffice are you using?
Possibly if you could post the entire agent log or error information we can help.
Finally we eventually helped our client with our product “Agent Runner” which allowed agents that fit this scenario (issues running in background on client or server) to be scheduled with other scheduling systems like Task Scheduler. Task scheduler can then kick off the agent and the agent usually has no problem spawning other programs and doesn’t hit the issues typical background agents hit.
I would be interested to see if this works for you and would be happy to assist. you can check it out at http://www.pembrian.com