I've got a question that may not be especially appropriate to this
group but since it involves a SQL Server 7 job, thought I'd ask.

The company I work for has NT4 servers with SQL Server 7 in many of
its units. I wrote a vb script which runs just fine on the server
itself. I saved it to a folder on the hard drive, ran it, and it did
its thing. So I wrote a job to run it at a scheduled time every day.
The job is a command prompt - cscript "C:\Program
Files\Whataburger\OrderPickup.vbs". Now, if I opened a command prompt
directly and typed in that command, it works.

When I run the job, however, nothing happens. I mean that literally.
I don't even get a job history entry. So I'm wondering if there is
something with SQL 7 that does not recognize a cscript command. Has
anyone had this happen?

Thanks,
Jennifer

jennifer1970@hotmail.com (Jennifer) wrote in message news:<3358f49d.0308070549.5a9f6cc@posting.google.c om>...
> I've got a question that may not be especially appropriate to this
> group but since it involves a SQL Server 7 job, thought I'd ask.
>
> The company I work for has NT4 servers with SQL Server 7 in many of
> its units. I wrote a vb script which runs just fine on the server
> itself. I saved it to a folder on the hard drive, ran it, and it did
> its thing. So I wrote a job to run it at a scheduled time every day.
> The job is a command prompt - cscript "C:\Program
> Files\Whataburger\OrderPickup.vbs". Now, if I opened a command prompt
> directly and typed in that command, it works.
>
> When I run the job, however, nothing happens. I mean that literally.
> I don't even get a job history entry. So I'm wondering if there is
> something with SQL 7 that does not recognize a cscript command. Has
> anyone had this happen?
>
> Thanks,
> Jennifer

If something works interactively, but not when scheduled, the reason
is almost always due to the account used for SQL Agent. If that
account doesn't have the correct permissions, for example, then you
may have problems running OS-level scripts. If you can log in as the
SQL Agent account instead of your own account, then you could run the
command directly to see what happens - this might give you some more
useful feedback.

Simon