::LoadFrom("Full Path to .8.0.dll").GetName()įor a. To try to figure out, what was going on, I ran the following command in PowerShell to check for the Assembly version of both library files. C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PrivateAssemblies\Interopīoth files had the same size of 168KB and both showed the same 7.938 version when checked the information under Properties:īut, even though, those two files looked identical, by examining the content of the files, it was obvious that they were not the same.C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\PublicAssemblies.
dll library inside the installed "Microsoft SQL Server Management Studio 18" folder and found two files located at the following path: So it seemed, the issue had something to do with the .8.0.dll file. In both cases, they had the same detailed description of the error: All those errors in a log file happened when the two tasks below were attempted: Looking at the generated ssms.exe log file, it consisted of multiple tags and some of them were Errors showing 80004005 - E_FAIL. When the application fails to open again, find the log file and open it using a text editor, like notepad.Įxamining the content of the SSMS log file.Simply modify it to the path of your choice. This will create a log file at d:\log.txt. We need to specify the full path to the log file, something like this: We do this by using -log argument, followed by the location and the name of the log file. The executable file for the SQL Server Management Studio is ssms.exe and we need to run it with the logging enabled. The command prompt will open at that specific path.Once there, type cmd in the address bar and press enter:.In my case using Windows 10, this was at C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE Open Windows Explorer and go to the installed folder of the SQL Server Management Studio.It turns out, there indeed is a logging feature available, but to use it, we need to run the executing file using a -log argument.
Using the SQL Server Management Studio log file Next, I wanted to see if there is some sort of log file for the SQL Server Management Studio, so I could examine it and find out why the application doesn't want to open. Now if we are lucky, the problem would be solved by now, but in my case, there was no change.
0 kommentar(er)
