Error Accessing The System Registry In Vba
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 10:56:59 GMT by s_ac15 (squid/3.5.20)
resident Excel expert at work, I have the privilege of being landed with some weird and wonderful errors which have to be fixed. Last week I developed an
Error Accessing The System Registry Oracle Workflow Builder
Excel spreadsheet for a user but when he went to test it he
Microsoft Visual Basic Error Accessing The System Registry Windows 7
said he was getting an error when he tried to check the project references. Specifically when he went to error accessing the system registry vb6 in windows 10 Tools > References in the VBA IDE he got the message ‘Error accessing the system registry': This error had nothing to do with the spreadsheet I'd built for him: obviously http://answers.microsoft.com/en-us/msoffice/forum/msoffice_other-msoffice_custom/a-step-by-step-procedure-for-fixing-error/3c81197e-a237-4fb7-8c8a-d28145f7428e he hadn't tried to reach the project references menu for a little while. When you try to pull up the project references, Excel goes off and reads a bunch of keys from the registry and this error occurs when the you don't have permission to read one or more of those keys. But how do you figure out which keys are causing the https://colinlegg.wordpress.com/2015/08/01/error-accessing-the-system-registry/ problem? The answer is to run Process Monitor (which must be run under an admin account) because it will show you every key which Excel tries to read and whether it did so successfully. ProcMon has saved my bacon several times over the years so it's worth a look if you haven't come across it before. It's extremely easy to use: simply add a Process Name filter for EXCEL.EXE, clear the display and then, with Excel running under the user's account, go to Tools > References and watch ProcMon burst into a flurry of activity. Once it's calmed down you can stop capturing events and examine the output. You're interested in any results which are ACCESS DENIED so add another filter on the Result column. In this case I have one key, HKCR\TypeLib\{57A0E746-3863-4D20-A811-950C84F1DB9B}, which is causing the problem: A quick Google search on that key reveals it pertains to a Flash Player update which has affected a number of people. The VBA IDE error message will go away once the admin uses the Registry Editor to grant the user read access to the access denied keys listed by Process Monitor. Share this:LinkedInGoogleFacebookTwitterEmailTumblrRedditPinterestPocketLike this
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting http://stackoverflow.com/questions/104383/error-accessing-the-system-registry-in-vb-6-ide ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error accessing the system registry in VB 6 IDE up vote 2 down vote favorite 1 In Visual Basic 6, when I attempt to access Project > References, it throws an error: Error accessing system registry I'm error accessing logged in as the local computer administrator running Windows XP Professional and I can execute regedt32.exe and access all the registry keys just fine. VB6 was installed as the local administrator. Any idea why this happens? I have have already visited that posting before. I'm running crystal reports 8.5 and it supposed to already have fixed that issue but apparently I still have the issue with 8.5 installed. I have also made the attempt of reinstalling crystal reports with no luck on error accessing the the issue. vb6 registry share|improve this question edited May 4 '12 at 10:47 Bill the Lizard 222k138447737 asked Sep 19 '08 at 18:36 phill 3,6602885127 add a comment| 10 Answers 10 active oldest votes up vote 10 down vote Depending on the Windows OS you have (I have Windows 7 Enterprise), you might want to try giving administrator rights to the REGTLIB.EXE (located in C:\Windws). Right click on the REGTLIB.EXE file. Select Properties from the pop-up menu. Then select the Compatiblity tab. On the Compatiblity tab, check/select the Run this program as Administrator checkbox. Click OK to save your changes. It might take take care of the problem for you. It worked for me. Good luck. share|improve this answer answered Nov 12 '09 at 18:36 Big Al 10113 1 How in the heck did you figure this out? I'm (sadly) building some VB6 code on a virgin Windows 7 x64 bit box with a MINIMUM vb6.exe install (I unchecked EVERY option). And got stuck and found this. I'd give you 20 up points if I could. VB6 sucks. COM sucks. This post was awesome. –granadaCoder May 9 '12 at 19:52 I can confirm that this one did the trick for me! The containing folder for me was C:\Windows\Microsoft.NET\Framework\v4.0.30319 –Luc Wollants Oct 29 '12 at 8:45 I think this occurs when VB6 is installed without being the Administrator. I first installed it without being Administrator and the installer didn't com