I recently got a new computer and installed all of the programs again that I use every day when developing. When I tried using DBComparer (that I've used for years with no problems) suddenly I keep getting this error (see picture) over and over when I try to select database.
I've read a couple of threads where the answers were only "uninstall" or "use another program".
Solutions I've tried so far:
Uninstall and install again.
Tried both x86 and x64.
Run as admin.
Switched authentication metod.
Double checked the authentication (logged in with the same on SSMS17).
Edit Uninstalled SSMS17 and installed SSMS16.
https://www.microsoft.com/en-us/download/details.aspx?id=42299
Install SSMS2014. Do it by click download on Microsoft® SQL Server® 2014 Express, then scroll down to the bottom and install SQL Server 2014 Management Studio. Then suddenly DBComparer started working again.
Installing SQL Server 2014 developer edition worked for me.
The DB Comparer 3.0 needs something that SQL Server 2014 or SSMS 2014 has. It would be nice to know which thing.
Related
I'm trying to install SQL Server 2014 but it stays in the same spot (Install_VCRuntime_Cpu32_Action) for hours. It's already the third time I'm trying to install so I don't know what else to do.
SQL Server 2014 Installation
I observed this very same issue in one of my colleague's windows 10 box with SQL Server 2014 Enterprise installer as well. As mentioned in this MS connect bug you can try either of the below mentioned options:
As mentioned by KevinMS in comments tab :
I used task manager and killed the Windows Installer instances,
clicked Retry and the installation completed. What a beat down.
You can kill the Windows Installer process as shown below:
As mentioned by Jonathan Dyke in workarounds tab:
It's fixed!
http://support.microsoft.com/kb/2820068
I tested this solution with 2014 express and can confirm that using
/SkipInstallerRunCheck works as advertised. The installer no longer
goes into an endless loop when it can't shut down msiserver.
For my colleague who was facing this issue with SQL Server 2014 setup, solution # 1 above worked.
Regarding SQL Server 2017 : My colleague faced exactly same issue on SQL Server 2017 also. We didn't see the "Windows Installer" app in processes tab on his machine. So we went with solution # 2 i.e. launch the installer as Setup.exe /SkipInstallerRunCheck and it worked for him. While running from PowerShell console the command looks like .\Setup.exe /SkipInstallerRunCheck.
I had this same issue on SQL express 2014. When I went to check there was indeed a Windows Installer running. I killed that process & SQL proceeded to install just fine.
Found this here:
https://community.spiceworks.com/topic/483582-ms-sql-2014-install-freezing
I recently installed the client tools for SQL Server 2016. This seemed to hose the COM classes for SSIS in my VS 2013 install, as well as my SSMS 2014 install.
I get a COM class not found {guid} error. I don't have a screenshot because I have since uninstalled VS 2013. I've uninstalled SQL Server 2014 as well. The problem is I'm pretty sure SSDTBI is still installed somewhere, and it does not have an entry in the control panel.
I don't want to waste my time installing VS 2013 again if those templates and everything are still going to be there.
Running the SSDTBI installer shows the SSDTBI features as grayed out (meaning they are already installed) and offers no option to remove.
Does anyone know what files are installed and their locations? I really would like to do a clean install.
Thank you.
Well - After googling some more and seeing all the code for command line installs - I had a revelation that worked:
setup.exe /ACTION=UNINSTALL
Did the trick.
This might be a stupid question. But I have to be sure because I have major problem setting up a simple database in VS2013 using Entity Framework Model First.
I'm trying to complete this tutorial step by step: http://msdn.microsoft.com/en-us/data/jj205424
I got stuck at step 3 - Generating the database, and I got this error message when I tried to enter the Server Name:
I really need to know this because right now I can't even get into SQL Server Management Studio without getting the Errormessage "Please reinstall the application". When I installed Sql Server 2012, My OS was Windows 8 and then it worked just fine with windows authentication. But when I upgraded to windows 8.1, this problem occured. I don't know if this is relevant or not...
So, is SQL Server 2012 really needed to make an ASP.NET MVC 5 project in VS2013 with a database solution?
No it's not needed, as both VS2012 and 13 comes with the smallest db integrated (localdb). Although you have to make sure it's set up and running:
sqllocaldb start v11.0
Use the localdb in your application:
(localdb)\v11.0
Then you can check its status with a command sqllocaldb info. After the configured in your application, you can manage it through VS2013 - SQL Server Database tab.
I always seem to battle with this so on my new Windows 7 dev PC build, I thought I'd try and get it right!
Do you install VS 2008 first and then SQL Server 2005 developer or the other way around? And for either way, are there any special options/settings that have to be enabled/disabled?
I've just take an Acronis image of my PC, configured IIS for use with SQL Server 2005 (see below) and proceed to install SQL Server 2005 developer. It's warned about SQL Server 2005 needing SP3 (no problem) but it's also warned about VS 2005 not been compatible. Can I ignore this and go ahead and install VS 2008?
Cheers, Rob.
PS. The page to configure IIS features for use with SQL Server 2005 is http://support.microsoft.com/default.aspx/kb/920201
I always install in the following order
IIS
Windows Installer
Sql Server
VS any version
whenever i tried to go the other way, i always faced a problem approx thrice i faced this problem. Usually some components becomes missing in other way
I'm trying to do a SQL Server 2008 setup and I've been given a Cross Language Installation failure. More specifically:
Rule "cross language installation: failed.
the Setup language is different than the language of existing SQL Server features. To continue, use SQL Server Setup installation media of the same language as the installed SQL Server features.
I do not have SQL Server Express installed and I browsed through "Add or Remove Programs" and was unable to find anything that looked like it was a previous version of SQL.
Any tips?
I restarted the setup after facing the same problem, and I realized that man should not close the installation center till the setup process is completed. If you leave it open it will work.
Ensure that you have uninstalled all of your old SQL Server versions. Also you must restart the installer if you have not done that when you began installation.
All I had to do was exit the installer and start the process again. For some reason it worked the second time around.
I had the same problem today when installing SQL Server 2008 Express on a computer that has never had an instance of SQL Server installed.
I found that "Microsoft SQL Server 2005 Backward compatibility" was installed. I removed this via Add/Remove Programs and was able to successfully install SQL Server 2008 Express afterwards.
Change the Current Windows Language interface for the needed language you want to install.
That will make it possible for the Installer to launch the Localized version.
If you've previously installed SQL on the machine (or apparently some RedGate tools) have you checked for any SQL detritus in the registry?
If not then the MS forums have details of some reg keys to look out for, and some of the links are worth following for advice on what to delete from the registry.
On my installation of Sql Server 2008 Express, this was caused by having Sql Server 2005 Express Tools installed while trying to install 2008. Uninstalling 2005 Tools fixed the problem. I was able to keep Sql Server 2005 Express, including Sql Server 2005 Backward compatability; only had to nuke tools.