scheduled command/program problem

[mrCide]

So we got this progress database on one of our servers--we gotta stop the database before we can do a backup of it. Problem is currently we have to log onto the console so the scheduler we use will run the batch (command line to stop the db) or else it won't run. Regardless if it's this scheduler or MS task scheduler. Apparently the thing just doesn't run unless someone (admin) is logged onto the console/machine.

It's at a CoLo so we use a dell KVM utility to get in (via tcp/ip) and log onto the console with admin.

I'm looking for a way around this basically. Is there a way to trick the program/command line/batch into thinking the console is logged in so the DB will shut down? I mean aside from writing a custom application to somehow do this, i'm not sure.. i'll take any suggestions i think.

TIA

 

[Markbnj]

In the MS task scheduler you can choose the account to run the task as. If you set this to an admin account, does the problem still occur? If so, then it's something in the batch you're running.

 

[mrCide]

Thanks for the response, problem is that it IS what's in the batch. 🙂 Simple batches will run okay but this one runs a command that apparently won't run unless someone is logged onto the console..

So what I think I'm asking for is a way to trick the utility into thinking the machine is 'logged in'. Like, would it be possible to create a fake service that's always manual, and use a batch to 'start' the service and stop it after a few minutes, thus executing the program and then closing it after a set amount of time? Or is something like that not possible?