Here is your situation at a glance. 1. You got computer A running 24x7 Scheduler with a job database containing your user defined script library methods
2. You got agent running on computer B.
3. You send a job from computer A for remote execution on computer B. You expect it to run on B yet you refer to script library residing on computer A. Solution: Copy job database file (entirely or just the script library part) to computer B so it can be used by jobs running there. In theory you can share the same job database file if you keep it on a network drive (see the following paragraph), but I don't recommend doing that. Job database file should be stored on a local drive to ensure full and fast 100% access to the file. Make sure the copied or shared file is registered as the last active job database file. To do that stop the B agent, start the scheduler on B and open the file using File/Open menu, close the scheduler and then restart the agent. From that point agent's jobs can use "local" script library methods. Some people prefer to replicate script library using built-in replication methods every time they run a remote job. This way they can always have up-date script library on all computers while maintaining it only in one place. We have discussed that method several time here. For details please search for message threads containing words script, library, and replication. : I should also add that the schedule loaded is located on a remote drive..
: This has not posed a problem among other remote agents.. just this one
: loaded as a service
|
