I have had a remote agent working as a service perfectly fine until recently.. It is unable to use the script library .. reporting keyword not found.

When I run this in GUI mode, everything is fine.

I have had the scheduler point to the main job database, as well as point to a local database.

i have also tried to copy the database over in full, and i have used remotecopysettings.

No matter what I try, the service will not use script library functions.. permissions are set properly, and looking at the registry for the scheduling DB it shows the proper place..

How else can I ensure the script library is loaded?

Just a guess. In the service mode it cannot find the ob database file becasue services have their current directory set to c:\winnt\system32 The likely reason is the job database file in the registry is entered without full file path. Try pdating the file name in the registry. You can do it manually
HKEY_LOCAL_MACHINE\SOFTWARE\SoftTree Technologies, Inc.\24x7 Scheduler\3.0\SceduleFile

or you can simply start the sheduler and use File/Save As menu to resave the file. This trick will update the registry.

: I have had a remote agent working as a service perfectly fine until
: recently.. It is unable to use the script library .. reporting keyword not
: found.

: When I run this in GUI mode, everything is fine.

: I have had the scheduler point to the main job database, as well as point to
: a local database.

: i have also tried to copy the database over in full, and i have used
: remotecopysettings.

: No matter what I try, the service will not use script library functions..
: permissions are set properly, and looking at the registry for the
: scheduling DB it shows the proper place..

: How else can I ensure the script library is loaded?

Yes .. I mentioned that I did verify that the registry entry was correct, and both before and after the save trick.

What actually turned out to be the problem was browing for a file using the open dialog and letting it save was a mistake.. Sicne I browsed i:\ ... it failed.. but when i substitute the correct machine path \\computer\file it works well.

I did realize that the remotecopysettings was not working. I would run the job on the scheduler side, to copy all values..

The remote agent's job database would update its timestamp accoring to the filesystem, but it would not reflect this change in the scheduler when i quit the agent then load it.

: Just a guess. In the service mode it cannot find the ob database file becasue
: services have their current directory set to c:\winnt\system32 The likely
: reason is the job database file in the registry is entered without full
: file path. Try pdating the file name in the registry. You can do it
: manually
: HKEY_LOCAL_MACHINE\SOFTWARE\SoftTree Technologies, Inc.\24x7
: Scheduler\3.0\SceduleFile

: or you can simply start the sheduler and use File/Save As menu to resave the
: file. This trick will update the registry.

Services cannot use drive mapping. Every network file you access for m a service must be referenced using UNC file name

: Yes .. I mentioned that I did verify that the registry entry was correct, and
: both before and after the save trick.

: What actually turned out to be the problem was browing for a file using the
: open dialog and letting it save was a mistake.. Sicne I browsed i:\ ... it
: failed.. but when i substitute the correct machine path \\computer\file it
: works well.

: I did realize that the remotecopysettings was not working. I would run the
: job on the scheduler side, to copy all values..

: The remote agent's job database would update its timestamp accoring to the
: filesystem, but it would not reflect this change in the scheduler when i
: quit the agent then load it.

any thoughts on the remotecopysettings ?

: Services cannot use drive mapping. Every network file you access for m a
: service must be referenced using UNC file name

remotecopysettings can only use the following items when settings are copied t remote agents
"AGENT PROFILES"
"DB PROFILES"
"HOLIDAYS"
"SCRIPT LIBRARY"

First 3 go to the registry and files. Because the agent is not using a job database (like the scheduler does) these replicated settings are updated in the memory cache only)

May be the following info will help you. Here is what is happening when remote script job is executed.
1. scheduler connects to agent
2. scheduler deploys job definition to agent
3. scheduler instructs agent to run the deployed job
4. agent parses the script and starts running the job.
5. for every scripted user-defined statement it searches the script library cache (agent process memory) and if found it executes the statement's code.
6. if user-defined statement is not in the cache, script library cache gets reloaded from last used job database file
7. if user-defined statement still cannot be found in the cache, job fails and an error is reported back to the scheduler

: any thoughts on the remotecopysettings ?