Error 1327 again!

How do you make Acronis look at this problem as a bug? I'm certainly not pay them to tell them this, which is what happened when I tried to report it. They don't want to know unless I pay for a support incident!

Nothing I've been told so far makes me believe that this isn't a bug. For instance, as the last time I reported this, I was told my scheduling details had been corrupted and I would have to delete it and start again. My major problem with that, is that corruptions don't sort them selves out. Am I seriously supposed to believe that if and when it runs ok the next night it has managed to uncorrupt itself! How about if you don't know what's causing the problem, say I don't know but your could try this. But then that likes admitting there's an issue with the program and someone would have to look into it. Couldn't have that could we!

Also, as far as support goes. Fine if I'm asking how to use the product or can't be bothered to read the manual or knowledge database. If the product is faulty, as I believe it is, I don't think I should have to pay to even get air time.

I am seriously unimpressed with Acronis! :(

Mark,

I understand your frustrations. It sounds to me like your issue is related to Windows permissions and not a problem with the TI app itself. There are countless post on this Forum that are related to this type of permissions error.

Let me ask you some questions.

The device you are using to run the backup task to (target), is this an external device?

This scheduled backup runs at night so do you leave your machine on in say sleep or hibernate mode?

When you leave your machine for this overnight time do you log off your user account?

Hi Bob

Thanks for the reply.

The backup device is an internal disk - a very large 4TB one.

I don't use hibernate or system sleep but I do allow the disk and monitor to power down.

It's always left logged on. My backup does a shutdown afterwards.

The weird thing is that it often runs for many days without an issue and then I may get a few nights of consecutive errors. But the main thing is that without any changes it runs ok again again as it has done for the last 2 nights.

I'm wondering if it can't handle the backup drive being powered down. i.e. it doesn't wait long enough for it too be ready. I might try a few experiments with that. Other apps I use don't seem to mind.

Thanks for your comments they make a lot more sense than the official support advice.

If I do figure it out I'll report back as it may help someone else.

Since this is an intermitant problem I would highly suspect a power issue is the source. Try adjusting your power scheme to not power down your hard disks and see if that solves the issue.

I had a play around with the drive powered down and TI seemed to handle it ok.

I've put a scheduled task to power up the drive 5 minutes before the backup time and see if the problem goes away. I'll be able to tell if the drive didn't power up in time as I'm writing to a log file with a timestamp.

I don't like the drive to powered on all day (I use the PC for work) as I use it mostly for backups and it's the only moving part in my PC apart from the DVD drive.

I've notice odd events which sometimes seem to precede an error. Like when I upgraded to the latest version of TI14 it fell over the next night but was ok the night after. These could all be coincidences though. I must start making a log of time I stop using my PC and when I use the TI app or make any changes to my backup options etc. There could be a pattern there.

Anyhow, thanks for your suggestions.

Well it was worth a try. The backup ran ok for 4 nights and then on the 5th night the same error. This time the backup drive definitely was powered up.

No other events or errors to indicate why. Nothing unusual happened during the day preceding the backup. No software installed. No system utilities run. No logging in/out. Nothing out of the ordinary as far as I can tell. No error/warning events. All my work during the day is done in VMWare VPCs, which is exited long before the backup.

Any other ideas anyone?

Same again last night. 6 days without a problem and then the same error.

The only thing that happened yesterday, which was different, was that my internet connection went down in the evening and I had to do a reboot.

I also notice that there are occasionally TI console errors (failed to process pair script) in the TI log. There don't always happen at the same time though so I don't imagine they're related but notice from searching about this error that again it's scheduler related.

One other thing that also makes my setup slightly different from the norm. Some of my manual backups use a removable drive which isn't present in the system unless I'm actually doing the backup.

I've had this issue on 2 separate PCs and across at least 3 versions of TI (2012-2014). Everything else in my system works fine except the random TI errors.

I notice with all the sort of errors that the stock remedy is to zap the scheduler. Well if you delete everything the problem is going to go away but it always comes back. How about fixing TI so this doesn't happen at all. I still don't believe that the scheduler is corrupted as how is it possible that it runs ok other nights without any changes?

I think your 1327 error is in fact an issue with your logon. Are you using a blank password? If it is, that's the cause of your problem and you either have to change it to something or change the registry key

HKLM\System\CurrentControlSet\Control\Lsa\limitblankpassworduse

from 1 to 0

Thanks for the suggestion but I have a regular password.

I didn't have one a couple of years ago when I first started getting these errors. I think it was one of the first things I changed.

Didn't know about that registry key though. That's one for the memory banks...

You might have a look at that registry key and if value us set to 0 change it to 1. There may be some other policy restriction at play here as well, maybe not something you did yourself but something an installed app created.

Thanks, it's already set to 1. Reading about it, I don't think I'd feel very safe setting it to 0.

The thing I can't understand is that this problem only happens 1 or 2 times a week. The rest of the week there's no issue? There's nothing scheduled to run at the same time as the backup (03:00) - at least nothing enabled. No other event errors or warnings. Nothing else I'm aware of not working properly. If there was a clash due to policy restrictions, wouldn't that cause an error every time?

Tell me about your backup task or tasks, do you perform a single backup task several times a week or do you have a full backup task followed by a number of incremental or differential tasks?

Let's say that scenario 2 above is true, you have a full backup followed by nightly incremental or differential backups.

It sounds to me like you first setup this task prior to your having established a password on your system. Then at some point you decided to setup a user account/password which is of course is a wise thing to do however, you had already performed a number of backups prior to this change in the system.

Now, let's assume for a moment that your backups before password assignment contained a file/folder or a number of file/folders that you still use and access on a regular basis. Since you indicate that you use the computer for work and I also see that you reference a "failed to process pair script" error being logged on occasion. I am going to take a guess here and assume that these nightly backup tasks you run are differential file/folder in nature for your work. If you made a backup of these same work files/folders prior to password establishment then these same files/folders are owned by and have permissions levels set for the default Windows Administrators account. You then create an Admin account with your chosen password but your account does not have the same permissions as the default Admin account.

Now think about that scenario and attempt to narrow down what data was contained in backups prior to the time you created your password. Using Windows explorer, locate those files/folders while signed in on your account and in the folder structure look for any folders or files that appear to have a lock icon by them. If you see any such icons, those files/folders are ones that you do not have permissions to write, modify, edit, etc. to. If you find such on your PC then it makes since that if you change those files/folders, then attempt to back those files up under your account not having permissions for those files/folders, then the backup will fail.

Now I am making a lot of assumptions here and I may be way of base but do some investigating and find out for sure. Nothing to loose but some time here to find out.