Bugs in scheduled tasks

Forum rules
Discussion on the R-Drive Image software

Post a reply


This question is a means of preventing automated form submissions by spambots.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Bugs in scheduled tasks

Re: Bugs in scheduled tasks

by Alt » Sun Mar 22, 2009 6:12 am

Thanks. I've past them to our developers.

Bugs in scheduled tasks

by Micropter » Fri Mar 20, 2009 12:30 pm

R-Drive scheduling bugs.

A few bugs i have encountered running R-Drive on a set of mixed servers for the last month. Servers vary from 2003 and 2008. The also vary in architechture (both 32 and 64 bits) however, these "bugs" have appeared on all.


All these servers are on domain and all backups are stored on network shares.

1. When creating a scheduled task, this error only occurs randomly. But when you get to the credentials page for under what account the task should be run. If you enter DOMAIN\USER followed by pass. After you save the task. If i ched the tasksceduler, it will randomly have set the task to run as local system account although other credentials were supplied. Opening R-Drive again and editing the task, changing the account again fixes this. Abit annoying coz i have to double check the tasks everytime. Some times it occurs, some times it doesnt. Its just randomly.

2. When the task is set to run under DOMAIN\ADMINISTRATOR if the Administrator is logged onto the console, or on a Terminal services session the task will always run successfully. If the server is rebooted and noone is logged in the task will in 7 out of 10 cases fail with the error "Failed to commit". The Scheduled task is ofcourse set to run wether the user is logged in or not.

Top