Kallal's vbscript and scheduled tasks

[patti]

I have used Albert Kallal's vbscript and it launches successfully when run
manually. (Thanks ALbert Kallal for the vbscript!)
Under server, won't go - runtime error 800a9d9f.
The script is on on a server that has access installed. The scheduler is on
that same server. The db is on another server that doesn't have access
installed. Why can't it run from scheduler?

Thanks for the help.

 

[Albert D. Kallal]

If the script works fine when you simply click on it, then it should work
for the scheduler.


My guess is perhaps your not using a logon, or user name with the same full
permissions that you do when simply clicking on the script...

So, do remember, the "user" name you use for the scheduler to logon, and run
this script will need the same permissions that you need when you test this
script.

So, #1, make sure the script runs just fine when you click on it on that
server box. If the script don't run on the server when you click on it, it
not going to run from the scheduler.

If the script runs fine when you click on it, then it should run fine from
the scheduler UNLESS you using a different logon id, or a user name with
different permissions to that folder.

So, test, and test again that the script runs fine on that server.

Does the script work just fine when run on the server (buy clicking on it)?

So, when you say it don't run from the server, are you saying that the
script DOES RUN just fine on the sever. However, when you attempted to run
it from the scheduler on the same machine, it does NOT work?

It possible that some things like drive mapping etc. take some time to
connect right after that scheduled process logs on. (or, as mentioned,
the windows user name used for the scheduled task does not have the
same drive mappings, or permissiosn).

I would use a unc path name to the mdb file, and NOT a mapped drive.

However, I should try and speculat for you!!!

It is best if you simply answer the above issue:

eg: specific, does the script run fine when
you manually run it on that server? Is it *just* when you scheduled on that
same server it don't work?

Or, are you saying that regardless of the script being run from the
scheduler, or clicking on it...it don't work at all?

It *seems* in your post you stated that it does work manually, but lets be
100% clear and sure that it does...

 

[patti]

Thank you for your help.

The script runs fine when clicked in its location on the server. It will not
run under scheduler.

 

[Albert D. Kallal]

Thank you for your help.

The script runs fine when clicked in its location on the server. It will
not
run under scheduler.

When you say "clicked on", are you running this ON the server?

When you say clicked on the location on the server, that is VERY VERY messy
in terms of communicating here.

It seems to imply that your testing this while on the server, but the above
leaves that a bit "loose"

I *think* that what you saying.

So, the script will run when test this ON the server. So you doing this test
while physically sitting in front of the server box, your logged on to this
server console, and double clicking the script works. However, on the SAME
machine, you then attempt to run this SAME script from the scheduler, and it
don't work?

Hum, that really is a stumper for sure.

I suppose you could move the script to run on the machine that has the
actual mdb file on it, since, obviously that machine has to be running also.

Give that try...

Anyway, if the above informaton is as correct, then I have zero clue why
this would not work....

 

[AccessVandal via AccessMonster.com]

Hi patti,

Are you trying to say that the vbscript file is in another machine and this
Folder is a Shared Folder? and when you are at the server, you double click
the run the vbscript, it works?

It's more likely that the Scheduler has no administrative rights the the
shared folder. You need to reconfigure the scheduler to a correct user to
access the file.

Thank you for your help.

The script runs fine when clicked in its location on the server. It will not
run under scheduler.

If the script works fine when you simply click on it, then it should work
for the scheduler.

[quoted text clipped - 42 lines]

It *seems* in your post you stated that it does work manually, but lets be
100% clear and sure that it does...

 

[Pieter Wijnen]

For Running vbscripts via scheduler you need to run C(onsole)Script instead
of the default W(indows)Script

RunScript.Cmd
---------------------
CScript /B myscript.vbs


HTH

Pieter

Hi patti,

Are you trying to say that the vbscript file is in another machine and
this
Folder is a Shared Folder? and when you are at the server, you double
click
the run the vbscript, it works?

It's more likely that the Scheduler has no administrative rights the the
shared folder. You need to reconfigure the scheduler to a correct user to
access the file.

Thank you for your help.

The script runs fine when clicked in its location on the server. It will
not
run under scheduler.

If the script works fine when you simply click on it, then it should
work
for the scheduler.

[quoted text clipped - 42 lines]

It *seems* in your post you stated that it does work manually, but lets
be
100% clear and sure that it does...