My issue that I was refering to the job database as : i:\dir1\dir2\database.dat

where I: was a mapped remote drive.

this worked fine, and was verified in the registry entry for 24x7

changing this registry entry to point to the UNC name of the server : \\appserver0001\dir1\dir2\database.dat

and restarting the service worked. The remote database was loaded, and my script ran.

This was only needed when your agent / schedule was running as an AGENT.

: This was only needed when your agent / schedule was running as an AGENT.

sorry .. i meant running as a SERVICE

Service applications cannot use drive mapping. You are correct you must use UNC names when referring to network files.

: sorry .. i meant running as a SERVICE