Post reply

Can''t open table with SSMS

  • February 1, 2006 at 9:54 am

    #113276

    When you right-click on a table it gives you the option to "open table" but it gives me an error, "Object reference not set to an instance of an object. (SQLEditors)" 

    Do I have something setup wrong?

  • February 6, 2006 at 8:00 am

    This was removed by the editor as SPAM

  • February 6, 2006 at 11:58 am

    #619050

    It appears that I am unable to perform this option running SSMS remotely, but using SSMS on the server works fine.  Is this a limitation of SSMS or just a security issue?

  • February 14, 2006 at 3:09 pm

    #620853

    I removed then re-install SSMS and now it works perfectly.

  • February 15, 2006 at 5:43 am

    #620979

    Ooh, that's cheating! Now we'll never know what the problem was

  • July 5, 2006 at 1:55 pm

    #647614

    I am having the same problems, but in my case it all seems related to registry access.

    I wasn't the one who setup SQL Server 2005, that may be part of it. I am, through group permissions, a local admin on the (virtual) machine. The error I see, when simply starting the "Management Studio" is:

    "System.UnauthorizedAccessException: Access to the registry key 'HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell' is denied.

    ...(and a whole bunch of other message info...).

    I was able to run regedit, find the user tree that did install it, I exported the entire MS SQL Server branch out to a file, edited the file, and changed the specific "user" reference to "HKEY_CURRENT_USER" and tried to merge it, but again, access was denied. So it seems that my problems are related to the registry and access to it, or not in this case. Maybe I should try a different login...

  • October 27, 2006 at 11:40 am

    #668579

    I am having somewhat of the same problem, the error I get is <Access to the registry key 'HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell' is denied>.  I am in the local admin group, however, I did not install SQL Server 2005 on this server, nor did I configure the server.  Were you able to get your's resolved?

    Thanks

    Roy

  • November 2, 2006 at 12:24 pm

    #669591

    Sorry all, I've been away from this issue for so long, that I can't remember anything about it as far as whether I resolved the issue I was having or not, although I may be revisiting it again shortly.

  • November 13, 2007 at 4:46 pm

    #750885

    If you find out how this was resolved, please post it. I have been working on this issue for 2 days.

    Regards...php

  • November 13, 2007 at 11:02 pm

    #750939

    This should be a problem with the client tools installation. also check for the registry permissions in the client machine.

    Cheers,
    Sugeshkumar Rajendran
    SQL Server MVP
    http://sugeshkr.blogspot.com

  • November 14, 2007 at 5:09 pm

    #751309

    Roy Laws (10/27/2006)

    I am having somewhat of the same problem, the error I get is <Access to the registry key 'HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell' is denied>. I am in the local admin group, however, I did not install SQL Server 2005 on this server, nor did I configure the server. Were you able to get your's resolved?

    Using regedt32.exe, have you checked permissions on that hive as well as the same one for HKEY_LOCAL_MACHINE? If so, is the Administrators group listed?

    K. Brian Kelley
    @kbriankelley

  • March 20, 2008 at 11:57 am

    #792168

    FYI: I currently have this issue and the error only happened with my Domain admin account. My local admin account works like normal.

  • March 20, 2008 at 3:22 pm

    #792270

    Mine turned out to be security issues that were introduced with a new rule. Resolved that and everything is humming along fine.

  • November 18, 2009 at 3:31 am

    #1080778

    I had the same issue, and you may not believe me, but at least on my machine it was caused by the current user not having any sort of permission on the HKCU keys. Actually, even Administrators and System were having Read only access to HKCU and his children. I don't know when that happened and why, but I fixed it simply fixing the permissions (usually Administrators and System and the current user as well have full control over HKCU), then merging an export file from HKLM where I had renamed all the keys (basically I exported HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools on a SqlTools.reg file, then I renamed each HKEY_LOCAL_MACHINE in HKEY_CURRENT_USER in there, and then I merged the saved version of that file on the registry), but I would not recommend this, it is a quick and dirty shortcut, the proper solution, after fixing the issue with the registry permission, is to reinstall the Sql Server client software. To say the truth, no single software installed since the corruption of the HKCU permissions may be correctly installed, therefore the really correct solution would be to delete the current user (after backing up whatever local data there may be) and to start with a new one (and in certain scenarios, the only really safe things to do would be to rebuild the machine from scratch, I wouldn't really like to see something like this happening on a production server).

  • November 20, 2009 at 12:19 pm

    #1082421

    Hi,

    I'm having kinda same issue, but different though 🙂

    fist i got SSMS 2005 installed and everything worked fine,

    Then i installed SSMS2008 so i could make some tests on our development 2008 sqlserver machine.

    But ever since i installed SSMS2008 i can no longer view the properties of Jobs neither in SSMS 2005 nor in SSMS2008

    The jobs itself i can see, but no properties whatsoever..

    If anyone got a solution for that it would be evrry appreciated cause it kinda sucks to have to RDP to the server and start SSMS on the server itself to see Job properties

    Tnx in advance,

    Wkr,

    Eddy

Viewing 15 posts - 1 through 14 (of 14 total)

You must be logged in to reply to this topic. Login to reply