Scheduled task failed to run, again
Windows XP Pro SP3
TI Home 2009, build 9809
My scheduled nightly backup task failed to run last night, just as I had reported earlier in forum entries 3841 and 4426. Running the task manually this morning worked correctly.
Another system in the house, running the same software, has performed daily backups without error for months. That system does NOT have "Fast User Switching" enabled.
At that time, it looked like the failures only occurred when I'd used the "Switch User" function to log on with a second userid while leaving my original session active any time during the day preceding the failed backup session.
This last failure occurred when I hadn't done that. A single session had been active all day since the initial power-on in the morning.
The backup task is configured to run with my userid, which has administrator privileges and has no password.
I had earlier deleted all existing tasks using
schedmgr task zap
and re-created the single backup task. It had run without error for four days before last nights failure.
The task failed with this error:
"Scheduler is unable to run the task"} with GUID CF7CE177-CE57-4DF4-9FB2-69CCB5CDA982} because of the error 1327 (Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced."
just as I reported in forum entries 4426 and 3841.
Two entries were made in the Security event log, just as in previous failures:
Logon Failure:
Reason: Unknown user name or bad password
User Name: Bert
Domain: ASUS-II
Logon Type: 4
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: ASUS-II

- Accedi per poter commentare

My backup task run fine for a week with latest snap-in and built on W7 Ult x64.... until now.
I swapped out one backup drive (SATA interface) for WD 1TB Green.
Acronis keeps failing with I/O error and other messages that won't cancel, won't go away.
How about "volume is off line" and let me change / edit / modify or.... disable the task!
Or have the task run only if and when the volume is mounted next time.
I have tasks set to run on startup; every two hours; continuous backup.
So now what? delete the task scripts?
Restore the drive I wanted to keep off line?
Uninstall ATI2010?
It behaved like it was locked in a loop and poor error recovery or "awareness" of the situation and environment, to be annoying, nagging (hit cancel every second!) and frustrating.
Cure: msconfig and disable services and startup items got me out of the un-ending loop.
Never seen anything like this guys.
-----
1.You are trying to back up to an external hard disk;
2.The operation fails with an error message similar to one of the following:
The task failed.
How about like Microsoft, and allow for user submitted comments to error dialogues?
I went to kb articles, they didn't address issue, and would have been perfect place to leave comments.
- Accedi per poter commentare

1327 Error continues....
Dmitry,
I, too, have had this problem for a long time...
I have five separate tasks, one for each weekday night of the week. Each have my userid (correctly, and admin status) and no password (there is no password). I am using TI 2009 Home on Vista (current on all updates). The only difference in these five tasks is the name of the file created (I like to have 5 backups deep).
RANDOMLY, on some nights I receive the 1327 error (say, "Tuesday" night's backup) and the backup fails. I change nothing, and next week the same script "Tuesday backup" runs fine! A week or so later, "Thursday" night's backup fails to run with 1327 error. Another time, it could be "Monday" that fails to run with the 1327 errot. And so it goes.
The point is that this is random and intermittent. All five tasks have the correct userid and no password (because there is NO PASSWORD for my user account--I am the only user on the computer). I have tried on multiple occasions to get a response from support, but no response has been forthcoming.
It is reassuring to see others are also having this INTERMITTENT failure, but that does not fix the problem.
Anyone out there found a solution?????
Thanks.
- Accedi per poter commentare
Sorry for the delay in following up on this ...
Turning off "Fast User Switching" is not an option.
I have TI Home 2009 installed on a second machine which does not have switching turned on, and it's been performing nightly backups without fail since the day I started using TI.
I've created a new user, complete with a password, strictly for performing backups and have changed the backup task to run using that ID. It's only been in use for two days, so it's too soon to tell if it will work reliably. I'll do what I can to re-create the situations that I think have been causing the earlier backups to fail.
Does that user have to be a member of the "Administrators" group, or would "Backup Operators" be sufficient?
- Accedi per poter commentare
Bert wrote:Does that user have to be a member of the "Administrators" group, or would "Backup Operators" be sufficient?
I see from the answer to my question in topic 6499 that membership in "Backup Operators" should be enough.
Thanks...
- Accedi per poter commentare

Bert-
I checked my system, and Fast User Switching is apparently enabled (because it was never configured or disabled otherwise). I have never used it, nor do I have a need for it. So, I have "enabled" the disability of Fast User Swithcing in group policies. (Awkward phrasing, but FUS is now off.)
I will observe and report any change....
Thanks!
Robert
- Accedi per poter commentare
RobertP wrote:Bert-
I checked my system, and Fast User Switching is apparently enabled (because it was never configured or disabled otherwise). I have never used it, nor do I have a need for it. So, I have "enabled" the disability of Fast User Swithcing in group policies. (Awkward phrasing, but FUS is now off.)I will observe and report any change....
Thanks!
Robert
Take a look at the list of services and be sure that the "Fast User Switching" service is disabled.
Right-click "My Computer", select "Manage", expand "Services and Applications", select "Services".
In the right-hand pane, scroll down to find "Fast User Switching", right-click it and select "Properties". Make sure it's stopped and that "Startup type" is set to "Disabled."
- Accedi per poter commentare

Win XP Pro SP3 - True Image 2010
Been a while since this thread was updated, but I just encountered the 1327 problem, The consistant issue throughout posts seems to be a blank password. That was also my situation. I also have fast switching enabled.
Additionally, I am set to create a new full backup every 15 backups, and this job should have been a full backup. Also, there was insufficient disk space to hold the backup (9.2 GB available, 23GB required).
I will probably create a password, and then bypass it using "controluserpasswords2", although the suggestion to create a separate account is getting some consideration.
- Accedi per poter commentare

I set up a new User Account WITH A PASSWORD, specifically, and solely, to use to run the TI tasks. My existing User Account remains without a password. For about two months now, all tasks have consistently run as scheduled. So, the problem does seem to be a problem with tasks logging onto users with "blank" passwords.
- Accedi per poter commentare

To the best of my knowledge windows scheduler requires a password to run any scheduled task in the manner you described.
- Accedi per poter commentare

Oh, but I wish windows "required" a password to run any scheduled task. If that were so, the tasks would have failed first time, the problem would have been easily diagnosed, and simply fixed. However, in reality the tasks run about 95% of the time WITHOUT a password, then randomly would fail, only to run fine the next time (again, without a password). In the end, the solution appears to be to simply to use passwords for the user accounts associated with any scheduled task.
- Accedi per poter commentare

RobertP wrote:Oh, but I wish windows "required" a password to run any scheduled task. If that were so, the tasks would have failed first time, the problem would have been easily diagnosed, and simply fixed. However, in reality the tasks run about 95% of the time WITHOUT a password, then randomly would fail, only to run fine the next time (again, without a password).
I hear you, RobertP. It is unbelievable that this is still an unresolved issue. This is exactly how it happens for me, too.
- Accedi per poter commentare

Hello all,
Let me assist you with the issue.
When you schedule a backup or validation task in Acronis True Image, you will need to provide your Windows user name and password at the Credentials screen of the Schedule Task Wizard:
(!) To find out your Windows user name please invoke Windows Task Manager (CTRL-ALT-DEL) and select the Processes tab and check the User Name in the corresponding column.
Please also check the following KB article: Acronis True Image Errors Out with Code 1326
Please reply to this thread if you have any additional questions.
Thank you.
- Accedi per poter commentare

This does not help at all. As mentioned before: The error is intermittent! Sometimes the backup works, and sometimes it doesn't. And when it doesn't, there is not any notification of the failure.
- Accedi per poter commentare

I believe thomasjk is correct. A windows password is required for all Windows scheduling tasks. This is a Windows limitation, not an Acronis one. However, the poor documentation and alerting within the program IS an Acronis problem.
@Robert Graff: I would consider the backups that DID run to be an anomaly. Since you know that know that scheduling isn't reliable the way you have it now, have you put a password on your Windows account and tested it?
If you are adamant about not having a password, you could try the tweak at http://www.kellys-korner-xp.com/xp_tweaks.htm line #67.
- Accedi per poter commentare

Hello,
Dogma, thanks for your help.
Robert, I may suggest you to create another account with administrator privileges and run tasks under it.
Please reply to this thread if you have any additional questions.
Thank you.
- Accedi per poter commentare
