Error opening quicken.chm

Use Add/Remove Programs to uninstall IE7 and revert back to IE6.

Use Add/Remove Programs to uninstall IE7 and revert back to IE6.

Reverting to IE6 is not an option.

Intuit chose to be very platform dependent and heavily integrated their software with Microsoft's. If you follow that path you should be in all of the Beta programs and make sure that your software works with the latest general release of Microsoft's software. Once you grab the tiger by the tail you cannot let go.

I also noticed that only Quicken's CHM file seems to have this problem. So they must be doing something strange.

F>

Why do you say that?

I'd suggest you try, in the listed order:

1. Uninstall and reinstall Q04.
2. Upgrade from Q04 to Q06 or Q07.
3. Revert from IE7 to IE6, as Laura suggested.
4. Upgrade from XP to Vista.
5. Don't blame me if none of the above work.

You can skip the following long winded and rambling set of unsubstantiated opinions and hypotheses that follow if you like.

I know essentially nothing about CHM files or how or when they are created and used by Quicken. Only what I read in a brief Internet description about them in general - that they are compiled HTML files and that they are highly susceptible to corruption. You almost certainly know a lot more than that about them than that.

I am somewhat familiar with how Quicken uses HTML files that are stored on your machine as an integral part of the Quicken menu and Help systems.

I'm just kinda guessing here, but from my experience with Q05 with IE6 and Q06 with IE6 and IE7, all on Windows XP, and from various posts in this NG, I've formed the following impressions:

(1) This area of Quicken, where it uses the IE/HTML interface for its Help menus as well as many of its interface forms (e.g. the file backup form) is susceptible to corruptions. I've had it happen to me twice and I know it happened once to a poster to this group.

I'd recommend you first backup your Quicken data then uninstall and reinstall Quicken. If Quicken corruption is your problem, this should fix it.

(2) I've found IE7 to be less stable than IE6, on my XP platform at least, although I've had no definite functional problems with IE7. However, a friend of mine, and many others, had functional problems with IE7 on their XP platforms. The point is that IE7 is new enough that it may have glitches on some vendors machines and some users' machines.

If your machine is in this category then reverting back to IE6, as Laura suggested, is the most straightforward approach.

(3) I'm not a strong defender of Intuit/Quicken and I'm sometimes a harsh critic. But I feel your criticism of their tight binding to the IE/HTML interface is unfair to them.

I've seen from past Windows releases that MS tends to have to hack their way to a (never-) final solution on security issues breaking many user programs on many users' machines in the process. I saw MS stomp all over online banking interfaces a few years in an attempt to stumble their way to fixes for security holes - it's often difficult to track their patches, some of which they don't even make public. You're right - Intuit is tightly bound to these issues. But using the IE/HTML interface probably saved them a lot of programming cost and effort with a gain of simplicity and reliability. I don't think it's fair to blame them for this design decision that was probably made at a time long before even MS realized this interface might be a hackers' paradise for HTML files stored on the users' machines. MS' belated solution (called Local Machine Zone Lockdown as I recall) is a mess.

(4) If you're going to stick with IE7 and reinstalling Q04 doesn't fix your problem, you might consider upgrading to Vista and/or a later Quicken release.

Speaking far from my areas of expertise, I'd strongly suspect that IE7 works far more reliably with Vista than with XP, especially on CHM/HTML security issues, simply because IE7 was probably designed to work with Vista but just patched for backward compatibility with XP. I have no expertise or inside knowledge to support this hypothesis, only my past computing experience on working with interfaces between large systems.

Vista, IE7 and Q04 might work for you.

A better and cheaper solution might be to upgrade to Q06 or Q07. Intuit is more likely to be fixing their IE/HTML issues in these releases than in Q04. Besides Q04 is soon due for sunset (semi-retirement). You may have to upgrade soon anyway and you can probably get Q06 dirt cheap on eBay, with little to lose even if the upgrade doesn't fix your problem.

And don't moan to me about the Quicken sunset policy. I'm on your side there. But somewhere deep in my heart I realize that this policy is absolutely necessary to keep Quicken alive and financially viable.

Hope some of this helps,

Jerry

P.S. The real experts in this group avoid responding to this type of the problem like the plague but I, like other fools, rush in where angels fear to tread :-)

For starters, you did not bother to mention Vista in your original post. Secondly, Intuit as well as Sage, have chosen to not develop patches for their older versions of their software. In both cases 2007 is vista compatible. Why should these companies spend $$ on a version that will be unsupported in the next few months.

So, back to your original post. If you are using 2004 with IE7 and you wish to get rid of the error messages, you must uninstall IE7. IE7 is a beta program that is full of bugs. Pure and simple.

P.S.

Double clicking on quicken.cfm works fine for me.

Quicken 2006 Primier Home & Business Release QA 5 (Note the "QA"!) Quicken installed/used under non-Admin account with Admin privileges

Windows XP Media Center SP2 IE 7 Version 7.0.5730.11. Norton AntiVirus 2005

As I recal (it's been a while) the "QA" update to Q06 did address IE/HTML issues. They also changed the "R" to "QA" in the release number for other Quicken versions at the same time, but I don't know whether or not Q04 was among them.

If your problem involves access permission issues that the Quicken "QA" update doesn't fix, you're on your own.

Let me know if this helps.

Jerry

IE7 left beta stage last fall.

Many will still consider it a beta until they release a service pack.

If its any comfort to you Steward, I also have the exact same error. Windows XP SP2 + latest patches IE 7 Version 7.0.5730.11 Australia Quicken PP 2007 R1 The scripts seems to run fine after you accept to continue Regards

Hi Stewart,

I had the same problem. The final piece in the puzzle was here

using "Method2".

Incidentally, I have also been through the IE7 uninstall thing - it's easily done. That was for my bank, not because of Quicken.

Cheers,

BK

I think the above fix allows him to execute the quicken.chm file, but he's already past that point. What I think he needs is permission for the quicken.chm file to access WelcomeToQuickenHelp.htm and other Quicken HTM files.

I know how to do this with the Unix operating system but I'm not a Windows expert and don't know how to do it in Windows.

I'm not even sure what's denying access to the HTM files. It could be (a) IE7, or (b) the general Windows access lock mechanism, or (c) Norton A/V or even (d) the Sygate Security Agent (about which I know nothing).

I suggested an upgrade to Q06 or Q07 because these releases (with the QA update) probably know how to handle at least issues related to (a) and (b).

I know there have been problems with various versions of Quicken because the developers at Intuit assumed everyone would be running as an administrator and that Quicken would be installed using the user id that would later run it. It has been my experience that those problems could usually be worked around by changing the security settings on some registry keys or folders and sometimes by copying a section of the registry from the installing user to the using user.

Are you now forced to actually run Quicken with adm>P.S.

I assume that means that Vista is also effectively a beta versi>

Because Quicken 2004 Premier Home and Business is still a supported product and this issue arose months ago and Intuit's response is always upgrade. Actually, that is not true -- sometimes they just ignore the issue completely:

`0011338&messageID`0055600 I believe I came across a report of the problem in Quicken 2007 running on Vista (but I don't have the reference as it didn't provide a solution) which Intuit will probably not respond to until it has

2008 available at which time the res p>For starters, you did not bother to mention Vista in your original post.

Probably true on any machine. Clicking OK just tells the script interpreter to ignore the access error and continue with the next line of the script, rather than terminating the entire script, which would kick you out of the Quicken Help system entirely.

I'm almost positive you don't have to run Quicken as an Administrator. I only specified how I installed and used it to give you as much detail as I could think of so that you'd have clues as to why things worked for me and not for you.

I probably should let someone else answer this question definitively, but I think if you install and use Quicken under the same non-admin user, you're OK. If you install it under the Admin user I think everyone can use it, but other users may have problems changing some Quicken settings unless you dink with the registry.

Nor for me either. But take a look at

perhaps other articles that a Google of "windows unblock file"uncovers. This article also includes a discussion of how antivirus programsmay be involved.

If you're using *any* Windows group policies, you're way more advanced than I am and perhaps you can get things to work by fiddling with them. I will warn you though that the Quicken QA release, which they delivered concurrently with the rollout of IE7 to the general public, involved massive changes to Quicken files on my machine. A simple dinking of policies may be a big security risk even if it works.

If you want to know more about security for HTM files that are stored on your local machine, you might go to

look at the section titled "Internet Explorer Local Machine ZoneLockdown". LMZL is the security feature that is disabled in IE7 when youcheck "Allow active content to run in files on My Computer". It's a somewhatdangerous security risk even if it works. I have a link to a much betterLMZL article but they apparently removed that article because the link isnow broken.

Another suggestion is to temporarily disable Norton A/V, Sygate Security Agent and any other firewalls you have running, to make sure they aren't the culprits.

After installing IE 7 a friend of mine found that nothing happened when he clicked on a hyperlink from within Outlook Express. Here, verbatim, along with credit to the original source, is the fix for his problem. I had no such problem because my machine was already configured this way (no thanks to me - I don't understand this stuff).

You too are using IE and HTTP and his symptoms also look like they mighthave been an access permission error. Perhaps the experts in an IE newsgroupmight have a similar fix for your problem. My apologies for any typos. I don't have a spell checker and, no matter how carefully I proof read, butchered phrases still get through. The older I get the more I seem to mess up :-)

Jerry

============== If nothing happens when you click a link: Open Windows Explorer, or the Control Panel. Go to Tools | Folder Options | File Types. Scroll down to [NONE] URL:HyperText Transfer Protocol (NOT URL:Internet Shortcut) and select it. Click Edit or Advanced, depending on your Windows version. Select 'open'. Click Edit.

"Application used to perform this action" should read:

"C:\PROGRAM FILES\INTERNET EXPLORER\iexplore.exe" -nohome (Check the path to iexplore.exe to make sure that is correct and use the double quotes.)

DDE should be checked and in the boxes below it you should have:

#1: "%1",,-1,0,,,, #2 IExplore #3 (blank)

#4 WWW_OpenURL

URL:HyperText Transfer Protocol with Privacy should be the same.

Sometimes it is necessary to uncheck Use DDE.