I was using VS 2015 CTP to try the migration of my project some time ago. After MS released VS 2015 RC I uninstalled CTP and installed VS 2015 RC. When I start installed VS, I'm getting the window:
License: Prerelease software
This license has expired.
Your trial has expired. Sign in to extend the trial and continue without interruption.
The problem is that my PC is not connected to internet according to corporate security reasons and I cannot change this. So I cannot Sign in, and I cannot "Check for an updated license" (which is another link in this window).
Do I have any chance (workaround) to use VS 2015 RC on this machine?
Related
Today I wanted to open Sql Server Management Studio 18 like every day. But this time an error message popped up:
Cannot find one or more components. Please reinstall the application.
And I reinstalled the application and even reinstalled the Microsoft visual studio 2015 Shell. What also confuses me is the fact that the shell 2017 of visual studio does not even exist yet. I'm working on a windows 11 machine.
Its a reported issued on Windows 11 22H2 (22621).
See https://feedback.azure.com/d365community/idea/6b7d06dc-9bec-ec11-a81b-6045bd7ac9f9
After I uninstalled all Microsoft related Softwares in the control panel and reinstalled all again the SSMS started working. I just found out that you can also use Azure Data Studio as an alternative for SSMS, which is also sometimes preinstalled on windows machines.
EDIT
There is a solution provided in the forum that I'd like to share here:
Download https://github.com/thebookisclosed/ViVe
Run (from elevated cmd prompt):
vivetool /disable /id:36354489
shutdown -r -t0
In my case it returned No features were specified why I used another command:
vivetool /disable /name:SV2Navpane
shutdown -r -t0
If you're currently enrolled in Windows Insider Program and using Beta Channel,a fix for this issue was released just recently.
Windows 11 Insider Preview Build 22621.586 and 22622.586
I have a fully updated Visual Studio Professional 2017 installed, and I am now trying to install SQL Server 2017 Developer Edition, but receive the following error message (translated to English by me) and the installation of the SQL server aborts:
The Visual Studio-Runtime Microsoft "Visual C++ 2019 X64 Minimum Runtime - 14.22.27821" has to be repaired.
The error message points me to a guide how to repair or remove programs, so I tried reinstalling SQL Server 2017 and Visual Studio, but both does not help, the error persists.
Is there anything else I could try to fix that broken runtime library? Does it matter that I also have/had the community version of Visual Studio Code installed?
I am not exactly sure what exactly solved my problem, what I tried doing is the following
Under Apps & features within the Windows Settings, I "repaired" all apps with a similar name to the error message, i.e. everything of the kind Microsoft Visual C++ 20xx Redistributable (x86) with xxbeing a 2-digit year, or a year range such as 15-2019.
Deinstalled the Visual Studio Community Edition.
Reboot the system multiple times afterwards and inbetween.
Point 2 might have just cargo cult to ease my mind, but all of this did not solve the issue yet.
Eventually I decided to install SQL Server 2017 Express rather than SQL Server 2017 Developer which miraculously worked. I can not rule out that my IT department solved it by obtaining additional licenses, since I am not able to figure out the exact time when the new keys got active.
I also ran into this problem.
I just updated my version of Visual Studio 2017 Community edition using the Visual Studio Installer and the issue went away.
I would like to put my database schema and its data in my git repository and have it version controlled, just like my code.
I have SQL Server 2008 R2 and Visual Studio Community 2015 RC. I know that Visual Studio 2010 upwards, Database project templates have been introduced to do just this. Please see this article for example. But I don't find those templates in my Visual Studio Community Edition 2015 RC installation.
Sticking to RC isn't very viable in the long term. Especially now, when Visual Studio 2015 RTM has been released.
Unless you have some really strong incentive to stay on Release Candidate, I would recommend to:
Get RTM Express Edition for free, whichever suits you best. SSDT 2015 is compatible with Web and Windows Desktop;
Get SSDT 2015 (again, for free) and install on top of that.
AFAIR, that should give you SQL Server database projects and everything else you might need. The only catch is that, as usual, it will be a somewhat longer route if you have ever had any CTP / RC versions installed on the same Windows instance before. Then again, it's nothing new.
I installed Microsoft Visual Studio 2013 a while back then uninstalled it because I needed space and a few months later when I tried to reinstall I got this error for SQL database tools and the other SQL packages that come with Visual Studio 2013, error is "the timestamp signature and/or certificate could not be verified or is malformed".
i finally found a solution to my problem. The error is caused be an SHA256 ceritificate thats in the build and the certificate expires on 10/6/2013 therefore when installing Visual Studio 2013 in present day it presents that error. The work around i used was to set the clock on my laptop before that date and then install Visual studio 2013 and the workaround was successful. Credit does not go to me, i only obtain this information from the following web page:
http://blogs.msdn.com/b/ssdt/archive/2013/10/08/known-issue-ssdt-install-fails-validating-certificates.aspx
credit goes to Jill McClenahan the individual that posted the solution. Forgive me explaination i am a newbie.
I have uninstalled Microsoft Visual Studio 2012 Ultimate and install VS professional 2013
after, i tried to Setup Sql Server 2014 but a message say
"Installation blocked due to detection of version of Visual Studio that install SQL Server 2012 client libraries.."
then i have uninstalled all Microsoft programs figured in this link without uninstalling visual studio 2013 .
and always i get the same problem
any solutions Please
At this point in time, you should be using CTP2, not CTP1.
You should be installing the CTP on a clean machine (preferably a VM), not a system with a bunch of pre-existing software - especially from previous versions of SQL Server / Visual Studio. CTP2 might get around this particular issue for you, but it's still best practice IMHO to run beta software in a clean environment.
Please review the release notes, in full, before proceeding.