Windows 2000 Permission Problem?

[TheVMan]

I am having a problem with a batch process running on a Windows 2000 box, and I believe it is caused by a permissions setting somewhere in Win2K. The process is a VBScript file that spawns multiple processes, using WScript.Run(). The spawned process then creates an object and does work. I have set up the process through NT's at command to run each day in the morning. I have found that when I leave the user that the scheduled task runs as logged into the box, it runs flawlessly. However, if I log out of the box and let the process run, only the first two processes run to completion. All others (I have varied this number) fail to create the object (its a Business Objects object) reporting a 429 Error - ActiveX component can't create object. I have ruled out the possibility of a Business Objects error, as the ONLY difference between when it runs flawlessly and when if fails is that the user that the scheduled task runs as is logged out of the console when it fails. I have combed the BO docs looking for some setting and have found nothing. I have also pinged all the BO support forums looking for anything similar and have found nothing. This leads me to believe that it is more the OS and security permissions than the BO product. I am hoping that someone has seen this type of behavior trying to create multiple instances of other proprietary objects and perhaps a workaround or a solution. Leaving the user logged in on the console is not an option here, so I need a fix. Any help, guidance, or insight you may provide will be useful. Thanks for your time on this one!

 

[imatthec]

Have you tried scheduling the task used with the "run as" option? In this way you can set the tasks to run under the user credentials that have the correct permissions.

For an immediate fix you could just lock the machine and let the process run as the logged in user.

 

[TheVMan]

We are actually using run as, with a domain account that is a local admin account. Unfortunately, the powers that be won't let us leave a domain account logged into the console