A
azarubkin
Guest
There is a similar thread
I've hit this problem when I updated my Visual Studio 2017 to 15.9.2. It apparently installed new version of C++ redistributable (14.16.27012) which removed the old one.
The reason for this behavior is explained there. But it causes problems with SQL Server Management Studio 17.9. Now SSMS throws the error in Microsoft.SqlServer.Management.SqlStudio.ConnectToOe() on launch:
Object reference not set to an instance of object
It is explained in this StackOverflow answer (recommended to repair Visual Studio 2015 Isolated Shell, which fails for me because a newer version of C++ redistributable is available).
But what are my options now? I would rather not remove this new version of C++ redistributable because I won't be able to build my C++ apps in Visual Studio. And I can't work in SSMS while this new version is installed.
Perhaps new SSMS version will be ready soon which addresses this issue?
Continue reading...
I've hit this problem when I updated my Visual Studio 2017 to 15.9.2. It apparently installed new version of C++ redistributable (14.16.27012) which removed the old one.
The reason for this behavior is explained there. But it causes problems with SQL Server Management Studio 17.9. Now SSMS throws the error in Microsoft.SqlServer.Management.SqlStudio.ConnectToOe() on launch:
Object reference not set to an instance of object
It is explained in this StackOverflow answer (recommended to repair Visual Studio 2015 Isolated Shell, which fails for me because a newer version of C++ redistributable is available).
But what are my options now? I would rather not remove this new version of C++ redistributable because I won't be able to build my C++ apps in Visual Studio. And I can't work in SSMS while this new version is installed.
Perhaps new SSMS version will be ready soon which addresses this issue?
Continue reading...