I have a requirement to deploy both Access 97 nand 2003 during a desktop project rollout. I have an issue with the operation of these. The applications install (97 then 2003) and work fine logged on as admin. However the registry is locked down for users and when I launch Access 97 after launching Access 2003 I get an error message stating "MS Access was unable to initilaise the registry, please re-install this product. I can repair the install using "msiexec.exe /qn /fm {Product ID}" but when the user launches Access 2003 and then 97 the problem recurrs.

I know this is a permissions issue as if I give the user temporary full control of the HKEY_CLASSES_ROOT key the problem is resolved. I have used Regmon to try and identify the registry keys concerned so I can drill it down and reset the permissions on them but when I make the changes it still doesn't work.

Any ideas or further areas to help nail this down would be appreciated.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Lockdowns can be fun because the registry permissions sometimes have to be very open in order for applications to work because they will delete keys rather than modify or constantly write out COM registrations with every launch. I personally think it is a bad idea to lock down HKCR because developers assume this isn't going to be locked down. So I know this might not be the answer you are looking for but I would call this a special case and be more lax with the registry security.
Answered 02/13/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Thanks for the reply kkaminsk, it is a special case....

We have a workaround in place but its not as clean as I'd like - I'll persevere and post any results. That may take a few days though.
Answered 02/15/2006 by: fritoz
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity