Error Accessing The System Registry Excel 2003
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 08 Oct 2016 21:49:57 GMT by s_ac5 (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 Excel spreadsheet for a user but when he error accessing the system registry oracle workflow builder went to test it he said he was getting an error when he
Vb6 Error Accessing The System Registry Windows 8
tried to check the project references. Specifically when he went to Tools > References in the VBA IDE he got the
Microsoft Visual Basic Error Accessing The System Registry Windows 7
message ‘Error accessing the system registry': This error had nothing to do with the spreadsheet I'd built for him: obviously he hadn't tried to reach the project references menu for a little while. 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 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 problem? The answer is to run Process Monitor (which must be run under an admin account) because it will https://colinlegg.wordpress.com/2015/08/01/error-accessing-the-system-registry/ 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:Like Loading... Related About Colin Legg RAD Developer Microsoft MVP - Excel 2009 - 2014 View all posts by Colin Legg → This entry was posted in Microsoft Excel and tagged Error Accessing The System Registry, ProcMon, VBA IDE, {57A0E746-3863-4D20-A811-9
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java http://visualbasic.ittoolbox.com/groups/technical-functional/visualbasic-l/error-accessing-the-system-registry-203836 Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management https://www.daniweb.com/programming/software-development/threads/435246/error-accessing-the-system-registry SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries Inside-ERP MacProTX VoIP_News Inside-CRM maxwellarnold I_am_the_dragon PCMag error accessing Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker JoeTorre bracke Locutus Ramnath.Awate Craig Borysowich Dennis Stevenson DukeGanote Richard mircea_luca Nikki Klein AbhaiTripathi knowscognosdoi Clinton Jones blrvenkat bluesguyAZ59 iudithm COMPANIES RSA Conference UC4 Apperian Sophos View All Topics View All Members View All Companies Toolbox for IT Topics Visual Basic Groups Ask a New error accessing the Question Visual Basic – General Discussions The VB - General Discussions group is a forum where peers share technical expertise, solve problems, and discuss issues related to the use of the Visual Basic programming language. Home | Invite Peers | More Visual Basic Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Error accessing the system registry pakrishnakumar asked Jan 29, 2003 | Replies
a component or Referrence to vb6 Project it give me this error msg : error accessing the system registry how i can fix that ??? sry again Hiba Alkhatib HibaPro -3 127 posts since Jun 2012 Community Member 2Contributors 1Reply 2Views 4 YearsDiscussion Span 4 Years Ago Last Post by AndreRet 0 AndreRet 362 4 Years Ago Here is a few solutions... This is because it runs a service which creates registry keys under the SYSTEM account. When VB tries to enumerate the keys under HKCR\TypeLib it fails and gives the error because the user running VB6.EXE (even if it set to run as administrator) does not automatically have READ rights to the key. At that point you get the "Error accessing the system registry" dialog. To workaround/fix this: Download Procmon and PsExec from sysinternals. Run Procmon and add a "ProcessName" filter with VB6.EXE as the process name. Then Select Project->References. And the error dialog should pop up. Switch to procmon and scroll to the end of the events list - you're looking for the last "ACCESS_DENIED" message for opening a registry key under HKCR\TypeLib. Thats the first key you need to change permissions on - so you'll need to run regedit in the same account context that the keys were created in - the SYSTEM account. to do this install psexec on the windows PATH somewhere then run: psexec -i -d -s c:\windows\regedit.exe (obviously change the path if yours is different) this will run regedit through the SYSTEM account. You can verify that even the administrator account does NOT have permission to edit these keys by running regedit through a Start->Run dialog as this elevates the priv' level to administrator. Find the key you identified in step 4 - right click it and select Permissions. Find the current logged on user that you use to run VB6 with and add them with full control to the permissions list. Repeat steps 3-7 because there may be more keys that exhibit this behaviour, until the Project->References dialog appears in VB6 without error. You could also open the .vbp in notepad to see the references if you're stuck and dont have time to do the above..... <----- OR -----> Select the Microsoft Visual Basic 6.0 shortcut from the Start menu and right-click on it. Select Properties, and the property sheet for the shortcut will be displayed. Next, click on the Compatibility tab. It is recommended that you make the following changes: 1. Enable compatibility mode and select Windows XP (Service Pack 2) ..... 2. Check the "Disable visual themes" option ..... 3. Check the "Disable desktop composition" option..... 4. Check the "Run this program as an administrator" option