This post has been closed and is not open for comments or answers.

Quicken home and business 2004 crashes after clicking backup

Hi,

For the past week now I have been wrestling with Quicken 2004 on my company's server (Microsoft server 2003) in a vain attempt to correct what appears to be a problem that is occurring for no reason at all.

After working on the data file for an hour or so, the employee will click backup and close the program. Upon closing or Reopening of QuickenCashbooks Home and Business 2004, quicken will sometimes display the following error:

"Quicken has encountered an unexpected problem and needs to close. Please restart your computer before opening quicken again."

The file has been sent to Reckon for reconstruction, which fixed a smaller issue with a "phantom" account and 27 missing transactions, so the file validate function reveals no errors to speak of, and Reckon have not yet provided a solution.

The file size is 39mb and at present the employee is trying to purge the file as he believes this will make the file size smaller and fix the problem, but I believe, seeing as I have tried and restored many backed up copies of the file, that it is almost like a ticking fuse, something that shuts off at a certain time for some unknown reason.

I have tried installing quicken clean on a windows 2007 computer and it yielded the same error.

I have tried restoring backups and it yielded the same error.

I have tried almost everything, does anyone have any thoughts?
    To my knowledge, none of the regular responders here use a non-US version of Quicken; so, to the extent that your problem has anything to do with the non-US characteristics of your product, we're not likely to have many insights.

    Part of your problem description confused me. I don't understand what a backup (the act of backing up) has to do with the file that was backed up. 

    If there is a problem with your regular data file, that problem should have been apparent, whether you did a backup of the file or not. Unless you were backing up, then opening the backup file ... which is a no-no.

    It's also not clear whether you can process normally after getting the error message and rebooting. Have you attempted to determine whether the data is correct? Whether Quicken can produce correct displays, reports, etc.? Do you have the correct number of accounts, with the correct names, correct number of transactions, correct total "dollar" amount of debits and credits in each account?

    As I recall, having a "phantom account" is a sign of file corruption ... corruption which can reach the point of making the file unusable.

    I can't tell from your post how many backups you keep; but, if you have them, I would investigate older backups - specifically backups made before the first occurrence of the problem.

    Also what happens when backing up to the local hard drive?

    [And if you reinstalled Quicken, you should insure you then updated to the most current release of Quicken (which is likely not the same as the most current release for other country versions).]
    • Hi,

      The backup button on quicken 2004 simply compresses and copies the file to a specified location on your hard drive, and quicken does not continue to use that. Also it copies over the old backup made unfortunately.

      All the data is correct to my knowledge, and the file works perfectly until you reach a specific number of transactions (I think) once it locks up, there's no way of checking it at all either.

      Our company backs up files daily, so one of the other things I tried was restoring a file from July to see if the same thing occurred. Unfortunately it still contained the "phantom" copy which reckon fixed last week, so I do not believe the problem to be a corruption issue, but more somewhat of a size or transaction limit issue.

      Thanks for your quick reply!
    "The backup button on quicken 2004 simply compresses and copies the file to a specified location on your hard drive, and quicken does not continue to use that. Also it copies over the old backup made unfortunately".

    I made the suggestion about backing up on the local hard drive only to try to determine whether there was something wrong with the backup process - to try to rule out any involvement from backing up to your server.

    There's an option in Quicken to warn about overwriting backup files. And newer versions of Quicken (U.S., anyway) have the option to suffix the date/time to the backup file name.

    Quicken should never "continue" to use a backup file - no matter where the backup is placed. Neither Quicken, nor the user, should "use" a backup file. If it becomes necessary to access a backup, the Restore feature should be used.

    It's possible that the limits mentioned in the following FAQ may not apply to your country-version - though I can't think of a specific reason why they wouldn't. Perhaps Recon can verify.

    http://quicken.intuit.com/support/help/account-transaction-issues/size-or-capacity-limitations-of-a-...
    • This link will be helpful, thank you. And yes as far as the backup files go, they were being backed up and then left be and the original file used. One of my previous attempts to resolve the issue was to restore an older version of the backup file using our recovery software then restore it with quicken, which again yielded the same result.

      It could be that the file has exceeded it's limitations, I will investigate this today.
    • Is there any way to make the file size smaller to deal with the fact that the file may be nearing its limits?
    • Typically, no. Once you've "occupied" the space, it's considered locked. Any attempt to delete or compress data in order to free up that occupied space will not clear that lock. Basically, once the space is used, it cannot be vacated.  When US or Canada files reach one of the limits, we advise our customers the best option is to start a new Quicken Data File with balances forward from the old file, and keep that old file as an Archive copy - for reports & such, but not data entry.
    • Thank you Tamara, may I ask what Purging a file does exactly then? As my colleague believes this to be the solution.