Vista - Error 14: Can't identify problem key/ path

Been trying to update quickbooks pro 2008 and when 'installation/ repair' halts because it cannot open a registry key, i've been granting permission, start over again until it finds another key it cant open, and so on.

Now the error 1402 message cant open key "hkey_local_machine\...\proxystubclsid". I can't read the full path in the error message window (condensed to \...\). How can I determine which key is the problem key or find the path? so that I can grant that key permission?

Quickbooks was most unhelpful about this and is blaming microsoft, and even if it is partially the fault of microsoft, they do not seem to be interested in publishing a fix, which I feel they could have if only we knew how to determine which registry keys the software installation needs to write to.

The title of this thread should read ERROR 1402 . . .

Hi, blueskyes, and welcome to the forums.

First of all, have you verified that this version is fully Vista compatible,? Also, what version of Vista are you using? Was there any special instructions noted in trying to install this, or a known bugs / FAQ available from the folks at Quickbooks?

What exactly is the update for?

Quickbooks say that pro 2008 should be compatible with windows vista (I have home version 32 bit) and they say on their website that the 1402 error message can be fixed by editing the registry, however, they cannot make any recommendations regarding this. Instead they want people to add user profiles and change the resident directory where quickbooks should be installed, however in my opinion this is not the right way to fix this.

The initial quickbooks install seemed to worked fine, with the exception that when automatic update is attempted, the program can't write to certain registry keys because permission is not granted by default even to administrators. I have been attempting to repair the installation by uninstalling and selecting "repair" but this program initally halted about half way through the action because it couldn't write to a particular registry key, it gives the name of the key in a "error 1402" message window, and then it rolls back to the original installation after the repair failure. I fixed several of these keys in succession by editing the registry and granting permission to administrators for the key named in the error message window, so the next time I try to repair, it writes successfully to that key and then halts on another key, and so on. I have now managed to get about 95% through repair, that is until it failed to write to a key with a long path name. The error 1402 message doesn't spell out the whole path but truncates it so that I can't identify which key now needs to have permission changed.

I talked with a Quickbooks tech about this, but they will not give any assistance with editing the registry and referred me to microsoft! They wanted to bill me $50 for this advice! If I only had a way of finding either on my computer or a log file which key last failed to be written to, I could get past this. Alternatively, if Quickbooks would publish a list of which keys need to be written to, everybody with Quickbooks 1402 errors could resolve their issues. Is there any way to identify the key(s) I need to edit permissions for (see original thread: error 1402 can't open key "hkey_local_machine\...\proxystubclsid", which key is that?)???

Search your registry for proxystubclsid - keep hitting next to make sure how many are found.

More than likely the one in question is in the same area as the last several that you edited.

Hi Blueskyes

Try to run subinacl tool to provide full permission to the registry and then try to install Quickbook 2008

bad idea.

This opens the registry to standard attacks that worked in XP.

Well, a compatible program installs properly without asking to uninstall other programs sharing registry entries....
So, i hope you did not pay for such proggy (trial version?), they have to modify it to fulfil vista requirements.
There is surely a way to install it properly by launching the install so that a log file could be created, indicating the key addresses which fail to be writen but sincerely it is not a way to do it when you pay for a prog.

Ask'em for a free license if you find the solution and i'll help you