Reckon Accounts Home & Business 2016 backup error 7031

Theo Hooft
Theo Hooft Member Posts: 6
edited November 2017 in Reckon Accounts (Desktop)
Reckon Accounts Home & Business 2016 backup error 7031

The backup error is NOT logged in the systems or Applications event log

Windows 7 Professional, Service Pack 1

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/error-code-7031-print-spooler-se... does not appear to give any relevant insight. 

Comments

  • Reckon FAQs
    Reckon FAQs Reckon Staff Posts: 357 Reckon Staff
    edited March 2017
    Hello Theo,

    Welcome to the Reckon Community.

    Could you describe the scenario that leads to this error?
    Are you saving the backup directly to your local drive, a network drive or another device (USB, ext drive, etc)?
    At what point of the process is the error generated?
    Is there a full error message screen that you can share here?


    regards,
    John.
  • Theo Hooft
    Theo Hooft Member Posts: 6
    edited August 2016
    The error occurs when we select Backup. We have tried different path, internal and external locations and it errors out immediately. We assume the error report when we select 'Send Report" go to Reckon? If not we can view the report and copy it here.
    image
  • Reckon FAQs
    Reckon FAQs Reckon Staff Posts: 357 Reckon Staff
    edited March 2017
    Thanks Theo,

    If the problem is not printer related and the guide given in the other post had no effect, then the cause is either with corrupt windows system files or with the Home & Business application.

    A general description of this problem is available in this WkiW article.

    To address possible windows system file errors you can do a System Restore back to a time when Home & Business did backup without error.  Or you can run the System File Checker that will fix any corrupt windows system files.

    If the problem persists then you'll need to uninstall and reinstall in Selective Startup Mode, your Home & Business.  See this article for the steps.

    Hope to have you backing up without issue soon.  


    regards,
    John


  • Theo Hooft
    Theo Hooft Member Posts: 6
    edited August 2016
    We tried the System restore and Reinstall in safe mode. 

    We suspect that the problem could be with the data file itself.  There is a Sample  file available in the Reckon Software so just now I opened it and it backed up without a problem.

    We have a feeling but am not 100% certain that the problem with 7031 arouse when I ran the “end of year” program to eliminate all transactions before 2007 as the whole Reckon was getting very slow due to lots of items such as share names and transactions accumulating. 

    The  process went well according to all results but 7031 appeared shortly after that.  

    We followed the following steps totry resolve the issue.:

    Step 1: CCcleaner registry clean.

    Step 2: Conduct a Full Malware Scan of Your PC (Malware bytes)

    Step 3: Cleaned Out Your System Junk (Temporary Files and Folders) With Disk Cleanup (cleanmgr)

    Step 4: Updated PC Printer Drivers

    Step 5: Utilized Windows System Restore to "Undo" Recent System Changes

    Step 6: Uninstall and Reinstall the Quicken Program in safe mode

    Step 7: Run Windows System File Checker ("sfc /scannow")

    Step 8: Install All Available Windows Updates (none found, WIndows 7, service pack 1)

    regards,

    Theo



     


  • Reckon FAQs
    Reckon FAQs Reckon Staff Posts: 357 Reckon Staff
    edited March 2017
    Hi Theo,

    Sound like you have eliminated all other possibilities.

    Restore a backup and test backup on it.  
    You will need to re-enter data from the date of that backup. 

    regards,
    John
  • Theo Hooft
    Theo Hooft Member Posts: 6
    edited August 2016
    Rather then do that and the problem recurring when we archive the old data, we have started a new blank file just entering this financial year data. We can access the older data from the pre-archive file. The archive run was after the start of the financial year (1/7/2016). Thank you John,  

    Regards  Theo