SSMS Solution queries prompt HRESULT E_FAIL error when trying to connect to servers
-
This is a weird one that I haven't seen until recently. As in after I upgraded my PC from Windows 7 to Windows 10. I've got an old SSMS solution from SQL 2008 with a bunch of "daily scripts" that prove useful in troubleshooting issues. Before my PC upgrade, I could open the solution, the scripts would open, sometimes without a connection and sometimes with, and then I could change their connections via the Query menu without issue.
Once I upgraded, suddenly I'm getting failure messages on the first script's attempt to connect (but other open scripts connect just fine). And when I change connections to a new server (for the first time only), I also get these errors. I tried creating a new SSMS solution, but that hasn't resolved the issue. Error pics are below in order of popping up. Any thoughts on what could be causing this?
EDIT: I've been working in SQL 2012 with the 2008 solution for 9 months without issue. It was only when my OS got upgraded (and the hardware) that this issue popped up.
- Brandie Tarvin - Tuesday, May 8, 2018 9:34 AMThis is a weird one that I haven't seen until recently. As in after I upgraded my PC from Windows 7 to Windows 10. I've got an old SSMS solution from SQL 2008 with a bunch of "daily scripts" that prove useful in troubleshooting issues. Before my PC upgrade, I could open the solution, the scripts would open, sometimes without a connection and sometimes with, and then I could change their connections via the Query menu without issue.
Once I upgraded, suddenly I'm getting failure messages on the first script's attempt to connect (but other open scripts connect just fine). And when I change connections to a new server (for the first time only), I also get these errors. I tried creating a new SSMS solution, but that hasn't resolved the issue. Error pics are below in order of popping up. Any thoughts on what could be causing this?
EDIT: I've been working in SQL 2012 with the 2008 solution for 9 months without issue. It was only when my OS got upgraded (and the hardware) that this issue popped up.
You get some of the weirdest errors. I would try running Process Monitor - use where Process = ssms.exe and it may lead you to where it is getting the error from. At the very least, it should show you what it is accessing when getting the error. Hit the error, don't do anything other than check Process Monitor to see what it was accessing.
That error used to be from corrupt Visual Studio caches but I have no idea which ones and can't remember the exact fix. I think it was deleting the corrupt cache and then running devenv.exe /setup or something along those lines. Using process monitor may lead to the corrupt cache though.
It's an easy enough thing to try and see if it leads you to anything helpful.Sue
- Brandie Tarvin - Tuesday, May 8, 2018 9:34 AMThis is a weird one that I haven't seen until recently. As in after I upgraded my PC from Windows 7 to Windows 10. I've got an old SSMS solution from SQL 2008 with a bunch of "daily scripts" that prove useful in troubleshooting issues. Before my PC upgrade, I could open the solution, the scripts would open, sometimes without a connection and sometimes with, and then I could change their connections via the Query menu without issue.
Once I upgraded, suddenly I'm getting failure messages on the first script's attempt to connect (but other open scripts connect just fine). And when I change connections to a new server (for the first time only), I also get these errors. I tried creating a new SSMS solution, but that hasn't resolved the issue. Error pics are below in order of popping up. Any thoughts on what could be causing this?
EDIT: I've been working in SQL 2012 with the 2008 solution for 9 months without issue. It was only when my OS got upgraded (and the hardware) that this issue popped up.
You say you "upgraded" the OS, so this was not a "clean" install of Win10 followed by a fresh install of SSMS?
If that's the case, I'd try either a repair of SSMS or uninstall and re-install SSMS. I'm speculating, but from the messages mentioning problems with COM, it feels like it's failing to find a COM component (which likely during the upgrade of the OS either was removed or changed.) -
I probably shouldn't have used the word "upgraded." I did get a new box entirely, fresh install of the OS.
Sorry for the length of time to respond to this thread. Many fires to put out.
- Brandie Tarvin - Tuesday, May 15, 2018 12:46 PM
In that case, I'd lean towards giving Sue's idea a try.
As another quick test though, can you create new solutions and then load them without problems?No worries, it's good to see you back around!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply