Can't open file - could earlier

Old version 2003 installed on a laptop, while main PC (that runs the same version) was in the shop.  Read in the Qdata from an external drive.  Worked fine.

Laptop developed problems, so restored a system image made just prior to when Quicken had been loaded. The install was good but no data file will load. Tried various files, made at different times from both the laptop and PC.  Won't validate any that succeeded earlier.

Attempting a back-up restore generates errors.  "Cannot open file" - "unable to open selected file" - you cannot restore a file from the current directory" (that file is on the external drive) etc.

When NEW is chosen, the interface does appear, and allows import of new data.  Then, if a restore from backup is attempted it says it succeeds but instead of displaying the saved file it requests to OPEN it.  That leads to "cannot open file."

Clean reinstalled (Revo) the program a number of times with the same result.  In one instance the log file reported that the files were from an earlier version - which is definitely not the case.  What in the world is going on here?

Comments

  • splashersplasher SuperUser ✭✭✭✭✭
    edited December 2018
    After installing your QW2003, run the appropriate final patch release for your version found at this link: Quicken Patches 
    -splasher  using Q since 1996 -  QW2016, 2017 & Subscription  -  Win7/Win10
    -Questions? Check out the  Quicken Windows FAQ list

  • b slurryb slurry Member
    edited December 2018
    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018
    b slurry I think the only way you can reinstall this program is from the original installation disks/CD.  Evidently there are safeguards in place to prevent restoring the program without them.
  • b slurryb slurry Member
    edited December 2018
    Originally, an earlier version of Quicken was installed from floppies.  Some years later Quicken 2003 was downloaded from the net and the older files were converted.

    It's that same file that is being used as the current installer  If the install/restore hadn't worked once it would hint at safeguards.

    But when a NEW file is created, data can be added and that file can be saved and the backup restored, so the program itself appears to be fine.  Very strange.
  • splashersplasher SuperUser ✭✭✭✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    QW2003 used a multi-file data set, do you have all of the pieces?

    Quicken Data File Extensions 
    -splasher  using Q since 1996 -  QW2016, 2017 & Subscription  -  Win7/Win10
    -Questions? Check out the  Quicken Windows FAQ list

  • b slurryb slurry Member
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    Must have, because the downloaded file has been running on the old PC for a decade, following conversion of the data files from the Quicken 19xx era..

    This single file installed on the laptop two days ago and read in every backup file - each from a different date - without problems. Today it won't read any of them.
  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    When was the image restored?
  • b slurryb slurry Member
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    Here's the history...

    Old Desktop PC - Quicken had been backed up and restored countless times over the years using data saved to USB and external drives.

    On December 16th it was installed onto the laptop and several backups were tested.  All succeeded in restoring to the dates on which they had been created. Added data and saved to a USB.  (Don't recall if I confirmed that this newly saved data was good.)

    Laptop had problems, so did a system image restoration to a time just before Quicken had been installed.  All was as it had been.

    Quicken reinstalled successfully, but won't read the data that it accepted just days ago. As mentioned, it does read back data saved from a new file.  Of course, no way can the old data be reentered. ^_^

    Thanks.
  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    I see.  So it was the system restore feature within Windows, and not from an image file.  All I can say about that is that when I have tried using it, it never worked and I would end up restoring Windows from scratch.  
  • b slurryb slurry Member
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    The fix wasn't done using a restore point which, I agree, can be problematic  This was a complete system image, created by Windows 10 and launched via the recovery environment.

    Bottom line:  Quicken worked fine days ago on the laptop.  But, after reinstalling it precisely in the same manner, same computer ostensibly in the same state, the program succeeds but the old data can't be read.
  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    I think in the reimage process you lost a "key" that allowed you to open the old file.  Just a guess.
  • b slurryb slurry Member
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    Perhaps??  But a complete system backup (an image file made just days ago) and subsequent restore should result in everything being just as it was on the day the BU was made.  Thanks for your responses.
  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    For security reasons, a system image doesn't include "everything" that allows access to protected files.  This is so someone can't make an image of your computer and gain access to your protected and confidential files.
  • b slurryb slurry Member
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    Sounds logical.  Still, on the old PC images have been restored endless times, and Quicken has never had a problem loadng its backup data.  In but a few instances has there been corruption, and the program itself repaired that quickly.

    One of the backup sets tested on the laptop was made on the laptop, when things were fine just days earlier.  The others, which also succeeded, were made on the other PC.

    So, the image that was restored was not from another PC but created just days before on the same PC, where Quicken backups initially succeeded.  Crazy.
  • SherlockSherlock SuperUser ✭✭✭✭✭
    edited December 2018
    Are you able to open the data file set (or restore a data file set backup) after you copy the files set to a local drive?

    Are you attempting to run Quicken 2003 in a compatibility mode?
    Quicken user since 1997 
    Premier on Windows 7 
  • Arctic Hare (H&B 2019 Canadian)Arctic Hare (H&B 2019 Canadian) SuperUser ✭✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    @SimonSezSo: Unless you edit a particular registry key, the imaging tool that is built into Windows (i.e. Create a System Image backup) does capture all content from the actively used portions of the selected volume(s).

    In order to discuss/address whether or not "protected" files can be read from a system image, you would have to be specific as to what type of protection you are referencing. If, for example, the files are protected with NTFS encryption then the files cannot be read from a mounted image.

    I will suggest, however, that most people do not have protection in place that would prevent there files from being read from a mounted image. If your HDD was stolen/removed from your PC, your files can be read by connecting that HDD on another PC unless you've used some form of additional protection, like NTFS encryption. This carries over to the image. Bitlocker is a different case as it doesn't carry over to the image.

    This discussion can get pretty technical, pretty quickly.

    It would be easy to read most people's files, and I mean all of their files, by physically "borrowing" the HDD or imaging the HDD and mounting the image elsewhere.  
  • Arctic Hare (H&B 2019 Canadian)Arctic Hare (H&B 2019 Canadian) SuperUser ✭✭✭
    edited December 2018
    @b slurry: If I followed your explanation correctly, which I'm not certain that I did, then it is possible that the problem is that the working version of Quicken was a patched version and the version that doesn't work is a lower patch level. If you need to apply the patches for your version of Quicken. The patches can be found here:
    http://www.quicknperlwiz.com/quickenpatches.html



  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    Arctic Hare  you are right, it does get very technical.  I am just going by the LAN tech guys at my former employer had to do when they loaded an image to a computer.  It seemed like not everything was provided with the image and they had to load certificates, and other credentials after the image was loaded.

    Thanks for the information, it's good to know.  I use Bitlocker on my own hard drive, and any removeable drive I have, for encryption.  That is where I got "key" from.
  • SimonSezSoSimonSezSo Member ✭✭
    edited December 2018

    @b slurry: If I followed your explanation correctly, which I'm not certain that I did, then it is possible that the problem is that the working version of Quicken was a patched version and the version that doesn't work is a lower patch level. If you need to apply the patches for your version of Quicken. The patches can be found here:
    http://www.quicknperlwiz.com/quickenpatches.html



    Arctic Hare, I think he has tried patching his file and it still didn't work.  See the first couple of posts in this thread.  But that doesn't mean it's not worth another try.
  • Arctic Hare (H&B 2019 Canadian)Arctic Hare (H&B 2019 Canadian) SuperUser ✭✭✭
    edited December 2018
    b slurry said:

    Good try.  Checked both the QIF and QSX boxes, though none of the backup files have those extensions.  Perhaps an earlier version did. Then ran the patch.  No change.

    One error that appears when attempting to validate is... "QDF:
    Incorrect file size.
    Cannot attempt data-specific validation.
    Your file is from an earlier version of Quicken."

    Not the case, as these files validated and imported without a hitch just yesterday. If this scenario repeats when the newly built PC is out of the shop we're in deep deep trouble.

    The tech guys you spoke with were probably making reference to a deployment image and were likely using a combination of the Windows Deployment Toolkit (MDT) and/or the Microsoft Deployment Image Servicing and Managing (DISM) command line tool. MDT and DISM are tools that can be used to create a deployment image. When doing deployment you can create a thin image or a thick image, where the thinness or thickness of image refers to how much "stuff" you include in the image. The thinner the image, the more that you need to load after writing the image.

    A deployment image is different from a backup image. The backup image that is created using MS Windows Create System Image backup is, for all practical purposes, a fully complete image. No missing credentials, no missing certificates, etc.

    A deployment image typically does not include Windows user profiles, which include certificates, but a user created backup image does include profiles and the corresponding certificates.

    Regarding Bitlocker - A volume must be unlocked (from Bitlocker) in order to be imaged. Therefore, Bitlocker does not afford any protection to an image made from a Bitlocked. The solution is to use imaging software that encrypts the image on the fly. Note: encrypting a deployment image would not normally be required, because deployment images usually don't contain confidential files.
  • b slurryb slurry Member
    edited December 2018
    Sherlock said:

    Are you able to open the data file set (or restore a data file set backup) after you copy the files set to a local drive?

    Are you attempting to run Quicken 2003 in a compatibility mode?

    No compatibility mode initially, though that mention prompted a test.  Windows suggested XP mode, which had problems.  Win 7 mode is best.   And, no, placing the files on the local drive didn't help.

    The O/S and programs/files had been migrated to the new PC, which initially was displaying the most recent entries. When a backup was restored to that machine - "can't load file" corruption!

    The problem was thankfully overcome by first backing up data that was still being displayed on the old PC.  It apparently sees it as 'new' data.

    That was the last drive not overwritten by bad files, which would have been curtains...for an issue that defies logical explanation.
Sign In or Register to comment.