Skip to main content

Backup failure after setting password on Windows userid

Thread needs solution

In the past I have run my Windows desktop computers without passwords because I pretty much control access to the computers.  Last week I added a password to my account on two computers.  Since then ATI would prompt me for my userid and password when a scheduled backup task would start.  I think this happens just once per task.  And it may happen only when the task is manually started.  At least 2 of the tasks failed when they were scheduled to run when the computer was sleeping.  No Ti_demon  log entry is created for these failures and the failure does not show in the task's Activity report but the task display shows a big red X.  I don't have Notifications set so I don't know if a failure notification would be sent.  

Is this known and expected behavior?  If not I'll submit a Feedback.

0 Users found this helpful

From your description looks like there is a problem in contacting the host. I have had a similar red x when I have forgotten to attach USB HDD (only happened once when I forgot I set a backup task for beta testing to a Seagate BackupPlus drive - was doing some work on the PC and forgot to reattach it. Took ages to work out what the problem was. Assumed one of the drives had become disconnected - counted the number of drives in Device Manager and max of 8 SATA was present. Checked to drive letter for backup an realised it was an external drive - really annoying seniors moment. 

You could try editing the backup task; I assume when hacking up to another PC you are also given the option of setting user name and password, so hopefully updating the task will over come the problem.

Ian

IanL-S wrote:

From your description looks like there is a problem in contacting the host.

I think we've had different problems. Two tasks - one backing up to an FTP server and the other backing up to a local (USB-attached) external drive. Both tasks showed the red X but left no footprints that I could see. And both requested my new Windows credentials - not a remote host's credentials - and ran with no problem after that.

A 3rd task had not been scheduled to run after my changing my Windows credentials so there was no failure, but I was prompted for the Windows credentials when I manually invoked the task.

I'll give this a try on my test PC running the 2020 Beta code. None of it's tasks are currently scheduled, and I have not manually invoked several of them since adding the Windows password. I suspect I will be prompted for the credentials.

Hmm. I think I will queue up several of the tasks and the sign off. I suspect the queued ones will fail.

Well, one theory shot down.  I was not prompted for credentials on my test PC even though I had not run the tasks since before setting the credential.  I'd say the 2020 Beta code fixed the problem ... except that I ran into it on a laptop that is also running the Beta code.

Unfortunately I won't get back to checking this for a week or so.

Not sure what is going on. I recall someone mentioned a similar issue a while back; cannot remember if it was resolved. I have been using Microsoft account to log into my various computers for a long time so I have never had the issue arise.

Ian