Restore errors

Answer ID 9203   |    Published 06/06/2006 05:19 PM   |    Updated 02/06/2014 12:46 PM
How can I overcome an error when attempting to restore my company file?

Restore errors are rare, but they can and do happen.  There are a number of things that can cause the restore process to fail and in many cases the data can be retrieved.  When restore errors do occur, it is important the problem is worked through calmly and systematically.

Throughout this support note the terms "data file" and "company file" are used interchangeably.

Using AccountRight 2011/2012?  Also see our support note Error when restoring a backup in AccountRight 2011 and later.


What causes restore errors?

Restore errors can be caused by any of the following:

  • Corrupt storage media, for example floppy disk, USB drive, etc. Floppy disks are probably the most unstable of all storage media formats.  Using Windows Explorer, they should be formatted before being used - including new disks.  If any bad sectors are found on a disk, discard it. Floppy disks are easily damaged, so they should be stored safely when used for archiving valuable data.


    Note: Formatting disks erases any data that maybe on that disk.

  • Corrupt backup file - Corrupt backup files are usually a result of not being copied to the storage media correctly, or in their entirety.  Exposing the storage media to magnetism, rough treatment, heat, moisture etc. can also damage the backup file.

  • Program conflicts - These are something that can't be foreseen by program vendors.   The Windows operating system forces many programs to coexist, and on occasions, this forced coexistence creates program conflicts.  This doesn't indicate a fault with Windows or your other software.

  • Hardware failure - This refers to the components of your computer such as hard drives, floppy disk drives, CD ROM drives and USB storage devices.

What is the first step to overcome a restore error?

Identifying the error is the first step, and it is from here that we can begin to work on a solution.  When an error occurs, an error message will usually be given that indicates its cause.  Where no errors are given, the 'characteristics' of the error need to be examined.  For instance, does the computer freeze, or does the restore process prematurely terminate? These error characteristics are then used to identify the error.


What are the most common restore errors?

Listed below are the most commonly known errors and their solutions.  From this point on, 'floppy disks' will refer to other forms of storage media such as Zip Disks.  Any information that is storage media specific will be indicated.  Also, 'CD' will be used where information applies to recordable CDs, DVDs etc.

 

Dynazip error

There are two things that will cause a Dynazip error: faulty floppy disks (except CDs), or, a DLL file conflict.

Floppy disks can be checked by using the Windows ScanDisk utility as follows:

  1. Click on the Windows Start button and then click on Programs > Accessories > System Tools > ScanDisk.

  2. Highlight 3 1/2 floppy (A:)

  3. Select both the Thorough and Automatically Fix Errors options.

  4. Click Start.

 

Any errors found on the floppy disk will be reported.  If errors are found, try using Windows Explorer to copy the backup file to the hard drive and then restore it from there.  The chances are that Windows Explorer will respond with an alert that indicates the disk or data can't be read.  When this happens, the data on the disk is lost.

 

DLL file conflict

The software installs and uses two files called dunzip32.dll and dzip32.dll (dunzip.dll and dzip.dll on FirstAccounts and earlier software versions).  There are other programs that install their own versions of these files.  When the software makes a call to these files, the Windows system points to the wrong DLL file that the software doesn't recognise.  To resolve this conflict, use the Windows Find utility to find the conflicting DLL files and then rename them.

To search using Windows XP:

  1. Close all programs.

  2. Click on the Windows Start button and then click Search.

  3. At the What do you want to search for prompt, click All files and folders.

  4. In the All or part of the file name field type '*dunzip*.dll' (type '*dzip*.dll' if you are receiving the Dynazip error while attempting to backup).

  5. Click on the Look In drop down arrow and select My Computer.

  6. Click Search. See our example below.


     Image

 

To search using Windows 7:

  1. Close all programs.

  2. Press F3 on your keyboard. The Search window will be displayed.

  3. Type '*dunzip*.dll' in the Search box. Type '*dzip*.dll' if you are receiving the Dynazip error while attempting to backup.

  4. Click Computer. See our example below.


    Image

 

After a few moments a list will display the search results.  Any files found that are not in the MYOB installation folder will need to be renamed as follows.

  1. Right-click the file to be renamed and choose Rename.

  2. Rename the extension 'dll' to 'old'.  For example, if a file named dunzip32.dll was found in the 'c:\window\system' folder, rename it to 'dunzip32.old'.

 

Note:  Always rename the extension to 'old' rather than rename the entire file.  Should a program not work correctly after renaming a file, you know that searching for '*.old' will find all the files whose names were changed.  They could then be renamed back to their original name.

Once you have renamed all the files that are not in an MYOB folder, return to the Desktop and restart the computer.  If the computer isn't restarted, Windows will hold the actual file address in memory and continue to point to the *.old file.

 

Unable to Restore (AccountRight 2011 only)

This error may occur if the zip file you are trying to restore doesn't contain an AccountRight 2011 compatible company file. AccountRight 2011 company files must have the .myox file extension. Also see Not an MYOB file below.

This error can be overcome by restoring the company file, or opening the restored company file with the program that was originally used to back it up.

 

Bad CRC

The Bad CRC error indicates a corrupt or bad backup file.  CRC stands for 'Cyclical Redundancy Check', which is a verification on the stored data.  As part of the restoring process, the restored company file's actual size is compared to the size it was originally.  If there is a variance, the backup is corrupt and unusable.

 

I/O Error

The definition of this error is Input/Output.  It refers to the complementary tasks of gathering data for a computer or a program to work; for example input instructions entered via a keyboard or mouse, and making the results of the computer's activities available to the user; for example output via display, disk or printer.

If you receive this error while restoring your company file, it indicates that the storage media or backup file is damaged, so the data will be lost.  A faulty storage media drive could also cause this error, so try another computer.

 

Not An MYOB File

This error is common where a company file is backed up and then restored with a different program; for example restoring a FirstAccounts company file using MYOB Accounting.  Although this message is given, the company file will have been restored.  This error will arise when the software attempts to open the restored company file, being the last step of the restore process.  Because the restored company file isn't from the same program, it will be rejected by the software and the above message displayed.

Current software versions share the same file structure, so this error mostly relates to restoring earlier versions of MYOB Accounting/Plus (v8 and earlier) and Premier (v2 and earlier) company files.

The AccountRight 2011 database is now on an SQL format whereas previous versions of MYOB Accounting and Accounting Plus (v9 onwards) and Premier (v3 onwards) shared the same database structure.

This error can be overcome by restoring the company file, or opening the restored company file with the program that was originally used to back it up.

 

The data file you have selected is not an MYOB file

This is similar to the 'Not An MYOB File' message.  It indicates that a different version of the software was used to backup the company file.  Although the company file will be restored, it will need to be upgraded to the version that is being used to restore it.

Also, if the version used to restore the company file is prior to the version that created the backup, you won't be able to open the restored company file.  For example, if you create a backup using version 18.5, and that backup is given to your accountant, if your accountant is using version 18 they won't be able to open the file when they restore it.  They will need to install version 18.5 on their computer to open the file.

 

Welcome screen appears and the restore process terminates

This is the similar to the Dynazip error.  You will most likely find that the Dynazip error is in the 'foreground', and may even be showing on the Windows task bar.  This error is caused by a corrupt backup file and the data cannot be recovered.

 

Screen is blank after restoring the company file

When a company file is restored, it is automatically opened by the last step of the restore process.  If you are confronted with a blank window at the end of the restore process, check the Windows task bar.  You will find the company file's log on widow has been minimised.  Clicking on the company file will maximise the window, which will allow you to open the file.

 

BestWare Stuffit engine could not be found (Apple Macintosh only)

When the software installs on a Apple Macintosh computer, it installs the MYOB Stuffit Engine into the System\Extensions folder.  If this file is missing or is corrupt, you will need to reinstall the software.  Alternatively, check for a copy of this file in your MYOB program folder.  If you have a duplicate of this file, copy it into the Systems\Extension folder.


If I am still having problems restoring my company file, what else can I do?

 

Copy the backup file from the storage media to the hard drive

Using Windows Explorer, copy the backup file from the storage media to the computer's hard drive and try restoring it from there.  This will overcome any anomalies that maybe present on the storage media or it's drive.

 

Try backing up and restoring Clearwater

Clearwater is a sample company file that is installed with your program.  Backup Clearwater to the same type of storage media and then try restoring it.  This will test the backup/restore function and the storage media's drive.  If Clearwater backs up and restores, then it will be safe to assume that the backup file is corrupt.

Also, where possible, back up and restore the company file to the same storage media.  Again, if this is successful, then it can be safely assumed that the original backup file is corrupt.  Also, be careful that the original backup file isn't overwritten when backing up to the same storage media.

 

Restore the backup on another computer

This will test the integrity of the backup file, storage media and the computer.

 

Try using WinZip or PkZip to restore the backup

When a company file is backed up, the software uses a third party application to 'compress' the company file. The backup structure of a backup file is compatible with both WinZip and PKZip.  Both these utilities are available for downloading from the internet. Websites hosting these programs can be found by using any of the most common internet search engines.

If the backup restores using one of these programs, it is possible that the dunzip32.dll (dunzip.dll for FirstAccounts and earlier software versions) file is corrupt.  After restoring the company file, reinstall your program using the Repair installation option.


Note for Accountants

If you regularly receive backup company files from your clients, request that they restore the company file back on to their computer before sending it to you.  This will test the integrity of the backup and its storage media.  Also, have them include information regarding the software version they are using.  This will assist you when restoring their file.




Was this support note helpful?
 
Please tell us how can we improve this support note. If you need help from the support team, please post on the Community Forum at community.myob.com

Print