Hello everyone,

Few month ago we were on Windows Server 2016 and we had the same issue. Automatic Backup was not working properly.

After migrating to Windows Server 2019, we were still having the problem.

A .tmp file is created by the Autobackup, but it's empty. So we dont have any backup.

We then decided to investigate the issue by ourselves, because QB Support is not able to help us, even after over a year.

After checking the QBBACKUP.LOG file, we realized that there was a "Bad Connection Handle Used" error.

** This QBBACKUP.LOG File can be found by pressing in QuickBooks F2 > F3 > Open File > QBBACKUP.LOG

*** This log can also be found at C:\Users\<username>\AppData\Local\Intuit\QuickBooks\Log\QBBackup.txt

The solution is quite simple : The local user QBDataServiceUserXX need to have full permission on the shared folder of QB Files/Backup.

** QBDataServiceUserXX was for us QBDataServiceUser30 for us. It depends on your QB version I believe.

After doing that, automatic backup is working back again ! After over a year ! Yeah !

Here is our actual setup in Task Manager :

This is the Security permission on our QB Shared Folder :

I hope this can help some of you !

Vincent

Thanks for sharing, @vhubert.

The resolution you've provided is of great help to other users who are also experiencing the same issue about automatic backup.

I'm also adding this article to further guide you in effectively manage your business using QuickBooks Desktop: Help Articles. It contains topics about advanced accounting, banking, and data security to name a few.

Additionally, there are new features in the system that'll surely benefit you and your business. To learn more about it, kindly refer to this article: What’s new in QuickBooks Desktop.

Please let me know if you have other concerns. I'm just around to help. Take care always.

We are on QB 2021, and the problem STILL exists!  Every time we upgrade software versions, the backups stop working, so we have to reconfigure them.  It is shocking to me that Intuit is ignoring this problem, especially since it demands users to use Windows 10 now.

To add to the frustration, since QB2021, even with the "Configure For:" setting changed to "Windows 10", the backups still fail, as I keep getting the following error in the QBBackup.log file:

Backup Error: QuickBooks encountered a problem attempting
to backup C:\DATABASES\QB_XXXXXXX\XXXXXXX.qbw
 - Drive specified could not be accessed. Error ID
 202: Last System Error: The system cannot find the path
 specified.

The path/drive most certainly exists.

I was finally able to work around this by checking the "Run only when user is logged in" option (as suggested earlier in this thread).....we run QB on a fileserver that is always logged in and locked away.  This is not ideal, but its the only thing I could come up with after 4 hours of troubleshooting.

Rant: Intuit.....your company has a reputation for ignoring users, and extremely poor customer support/knowledge.  The fact that this problem has existed for 3+ years, and CONTINUES to exist despite you mandating Windows 10 installations is unacceptable.

I get the feeling that Intuit is really trying to aggravate its Desktop users to the point of moving to QB Online.  We have tried it, and we hate it.  Rest assured that if QB Desktop becomes unusable, we will be investigating the plethora of other options out there, knowing the history of how Intuit treats its customers.

There is NOTHING worse than being a long time / subscription paying client that feels ignored and unappreciated.

Can you please tell me how to get to this screen to change it to windows 10.   I have tried to figure it out, but I cannot.  

thank you in advance

Running Win Server 2019, we had to 1st create/schedule the local backup job in QB.  Then to Windows TASK SCHEDULER to modify them.  Click on the TASK SCHEDULER LIBRARY, then see all the tasks in the middle pane.  Find your QB backup task and then right click to PROPERTIES.  Modify:

1.  Bottom left: check the box that enables RUN WITH HIGHEST PRIVILEGES

2.  Bottom middle: select the Windows version you are running (I selected Windows Server 2019)
3.  Click OK

Right hand pane of the TASK SCHEDULER: you can click the RUN button if you want to test your new task...
Note: do not modify your tasks inside of QB; use the task scheduler to modify them.

Nearly 2 years later, this post was super helpful for us running an automatic backup on Windows Server 2019.  The default in the Task Scheduler was Windows Server 2003.  👍

I can attest that - yes - this bug still exists in QB Enterprise v21. And yes - Quickbooks is still ignoring their user base and refusing to fix this major issue.  I mean - I am only paying thousands of dollars every year for an Enterprise license - and a major system bug like this goes ignored for going on 4 years now.  The fix offered in this thread works.  It works a lot better than management of support at Intuit.  

What a joke.  Just installed QB 2022, and the problem still exists.  Windows 2003, XP, 2000 aren't even supported my MS anymore and this setting is still how QB configures the scheduled backups.

Talk about an out of touch company.

Frustrated that this backup feature does not work...and it looks like this has been going on for years!

After many hours of reading and trying different solutions to make this work...finally got it working thanks to ivorytux.   I did NOT change anything else in the task window:

I'm using Quickbooks Pro (Canadian), latest versions of both QB and Win10 Pro, and I'm using MS OneDrive.  Tried to set up a scheduled backup to my OneDrive so that my QB would be backed up to the cloud automatically.  I created the QB backup task and changed the default task in the scheduler to "Run only when user is logged on".  I did NOT change anything else in the taks window:

Frustrated that this backup feature does not work...and it looks like this has been going on for years!

After many hours of reading and trying different solutions to make this work...finally got it working thanks to ivorytux.   I did NOT change anything else in the task window:

I'm using Quickbooks Pro (Canadian), latest versions of both QB and Win10 Pro, and I'm using MS OneDrive.  Tried to set up a scheduled backup to my OneDrive so that my QB would be backed up to the cloud automatically.  I created the QB backup task and changed the default task in the scheduler to "Run only when user is logged on".  I did NOT change anything else in the taks window:

Hope this helps someone else!

Well, there are a variety of techniques to get QuickBooks Scheduled Backup Not Working. But running the verify and  Rebuild Data Utility tool is one of the most successful and convenient ways to restrict such an issue. Here's how: 

• At first, open the QuickBooks Desktop application and head to the File menu.

• Now, select the Utilities tab and then tap on the Verify data option. 

• After that, go to the option that states QuickBooks scan all the company files & data, and search for the damage. 

• Later on, you might get a pop-up saying your data has lost integrity. Close the message tab and press the File tab again. 

• Move your cursor to the Utilities sections and select Rebuild data. 

• Furthermore, press OK at the Backup Company Data pop-up window and get a backup of your company filer data on the desktop. 

• Next,  the QuickBooks Rebuild Data tool will repair the damage in the company file. 

• Once you see the message Rebuild has Completed, you would have to hit the OK tab and try to schedule the automatic backups once again.

Thank you very much for your posting, I had the same problem using Quickbooks Desktop 2021Pro   I can't believe that this is still a problem 4+ years after Intuit was notified of the problem and solution!

Yes, this issue has persisted over the years.  I really don't think Intuit is interested in any support or development on the desktop software as I'm convinced they are trying to force users into the Online platform.

Another hint: if you are backing up to a network drive, you MUST use a UNC path.  Since QB 2022, for some reason the scheduled backups won't work if you select a mapped drive.  This isn't obvious until the scheduled backups fail.  The log messages aren't clear at all.