Quicken Deluxe Update R7 Fail

Was notified this morinng that the R7 patch was available, but all attempts to install it (including manually) failed. Reviewing the update.log file, it appears that the patch was sucessful for all files except one called convert_stub.dat. The error message is:

RTPatch error ept0036: Old file not found. However, a file of the same name was found. No update done since file contents do not match:

Any ideas on why this is failing and how to correct it?

Reply to
Robert Neville
Loading thread data ...

I also tried to update to release 7 and it was unsuccessful; I got the error message that "a patching engine error had occured" Did anyone else have the same problem? Where do you find the log file?

Reply to
Barbara Lindholm

It's in the Quicken program directory. Note that the log is cumulative, so you'll need to scroll down to the bottom of the file.

Reply to
Robert Neville

Thanks, I found it and it gave the same message as yours except the file name that failed was listed as wpt0036. That log file dates all the way back to 2003. How do I know that the Release 7 update log refers to Release

7 for version 9? At the very bottom of the log file it says log closed 2004. I see no mention of todays date. I found one of the reasons for a failure is if Quicken is installed in the C:/ drive and not in Program files. Mine did install on the root directory, C: /. It recommeds reinstalling into C:/Program Files/Quicken. I 'd rather not resort to this to risk something else going wrong. Also why did all my other patches install correctly to it's present location?

Reply to
Barbara Lindholm

I assume that the two of you are talking about R7 for Quicken 2009.

It installed here with no problems this morning.

Reply to
Ken Blake

I'm having the same problem with the R6->R7 update. The last few entries in the log are:

======================================= Patching: cashgen.dll .......... Applying MODIFY File Patch for 'cashgen.dll'

Writing New File Verifying - Passed!

Done Patching: convert_stub.dat .......... Applying MODIFY File Patch for 'convert_stub.dat'

error ept0036: RTPatch error ept0036: Old file not found. However, a file of the same name was found. No update done since file contents do not match: PATCH was unable to locate an exact match for the original file to be updated. However, PATCH was able to locate a file Old File not found. However, a file of the same name was found. No update done since file contents do not match.

RTPatchApply32 returned 36 ERROR: Error occurred applying patch to Quicken directory. Unloading RTPatch Engine. Not Rebasing DLLS Displaying Wizard 5

UPDATE FAILURE REASON: ERROR: One or more error(s) occurred with the patching engine, or patch data files.

====================================== Should I assume it is convert_stub.dat that is the old file that can't be found (although a file with the same name was found. How confusing is that)? The convert_stub.dat I have is dataed 10/30/2006, and there is a convert_stub.dll dated 5/26/2009.

Reply to
Tim Johnson

I'm getting the same problem - has anyone found a solution to it - and how to get the update to apply?

Charlie

Reply to
charliech

Same here, on two separate systems with Q9H&B and Vista Home Premium 32 - A patching engine error has occurred when updating Quicken. I tried all of the suggested solutions here, with no success:

formatting link
Has anyone running Vista successfully installed the update to R7?

Reply to
Jim Jensen

Just did, Vista Ultimate 64, updated with no problems.

Reply to
XS11E

There is now a sign-up in Quicken Community so those experiencing the problem can be contacted when Intuit comes up with a solution. Lots of users are affected by this issue, be it XP or Vista.

Reply to
Jim Jensen

Reply to
Barbara Lindholm

formatting link

Reply to
Meebers

Hi, Robert.

Looks like some of us dodged a bullet! I bought Quicken 2010 Deluxe Monday and installed it Tuesday (10/20/09), so I never got the R7 patch.

Or did I? There was an "R" update within the last week or so and it went smoothly for me. I seem to remember that was the R6 patch, but it might have been R7. Too late to check now because Q2009 is gone from my computer.

At any rate, I had no problems with last week's patch - or with installing Q2010, which automatically uninstalled Q2009 (with my permission).

RC

Reply to
R. C. White

I thought the same thing R.C.! Has it occurred to you (like it did to me with a wry smile on my face) that some folks are amazed that some of us install the latest release without even waiting for R1? Here's a good reason why! You might not get crappy 'old' maintenance!

Reply to
Andrew

JJ> can be contacted when Intuit comes up JJ> with a solution.

When Intuit fixes the bug? Which century will that be....

Reply to
Bob Fry

Hi, Andrew.

Fresh-out-of-the-box, mine already says "Quicken 2010 Deluxe Release R 2". ;^}

RC

Reply to
R. C. White

Thanks, I signed up.

formatting link

Reply to
Barbara Lindholm

Thanks so much.

formatting link

Reply to
Barbara Lindholm

Why does Intuit need my e-mail address Name & Phone Number?

If they have a fix post in on their site.

Better yet, include the fix in the Quicken Online Update, and the Quicken manual update file. Just call it REV 7A

Next, Intuit will want my SS# and bank account #'s.

Reply to
Joel

Yup; as far as I know, a first. Because Intuit extended the release date for Q2010 until they could complete a reasonable first-shot at the Quicken-to-Money converter ... they had time to create a bug release before the actual R1 release was finished.

R3 is already scheduled for sometime in November.

But take note: from what I have read, users of Q2010 (and, I infer, users of future versions) will never again be allowed to choose what release they use. As long as you give Quicken online access, you will be forced to accept the most current release.

I think this is related to difficulties Quicken support has had trying to address problems when users are not using the most current release of Quicken. And I think there is no question that trying to solve problems that may not exist in the most current release, poses a significant burden on anyone in that position. I have been burned by it, and seen other responders burned by it, many many times.

But it also prevents users who want to use Quicken to download data, from trying to avoid problems introduced by a new release.

I personally don't like the new policy ... no matter how many difficulties allowing users to chose their Release creates for those trying to solve problems.

Reply to
John Pollard

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.