I previously had sql server 2005 express and uninstalled it.. I also uninstalled any vs related programs and installed visual web developer 2008 express edition with SP1. now that I am trying to install sql server 2008, I am seing error messages like no other and leave that alone without any suggestions..
the latest one which I could not come to a proper solution on the internet is;
consistency validation for sql server registry keys error which suggests
"The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
as you might have guessed nothing so informative in the documentation... Also, when I try to delete any sql server related registry key, it does not let me. (yes I stopped all the related services..)
anybody here that can be of any assistance?
You can try with this procedure :
Stop all SQL Server Services
Remove all SQL Server Services with sc delete servicename
Control Panel - Add/Remove Programs - Select and Remove all Microsoft
SQL Server programs
Open regedit and remove all SQL Server folders in this registry key: HKEY_LOCAL_MACHINE/ SOFTWARE/MICROSOFT
Remove SQL Server folders from Program Files directory
Reboot
This procedure should resolve the issue, i've resolved with this procedure ...
i found this to happen if you had an add-in for SSMS installed which hasn't been uninstalled before ssms was uninstalled.
You may need to change the permissions on the relevant registry keys using regedt32 first so that you can then delete the keys via normal regedit
Well actually, I believe, one should not go through such mess in order to accomplish a simple task like this. In the end, I ended up formatting my PC and re-installing SQL Server.
I know this is an old question and you already said in comments that you reformatted the machine. However, I just ran into this exact message and wanted to share my solution because it was so easy, but the error message didn't help at all!
I was using the wrong installation package. I had a 64-bit Intel Windows 7 computer and I was trying to use the x86 version of SQL Server 2008. Once I found the correct version (x64) I did not get this error and the install proceeded normally.
I had a similar problem because I still had some remnants of SQL Server 2005 left - not the services, it was some parts of the IDE. Anyway, to resolve it I used the option to upgrade (sorry, I can't remember the exact option just now). After running the upgrade portion, which took a few minutes, I could then run the full install with no problems.
Related
I get this error in Management Studio. I don't know what the reason is. I tried repairing SQL Server, but still the issue is not resolved. I read a lot of articles about this, but I don't know how to do this with registry keys.
How to solve permissions issue?
As James suggested, it's time to use a later version of SQL Server Management Studio.
If you can run the latest (version 18.4), that would be good. It still has support for SQL Server 2008.
However, it has more recent dependencies. If you look at the list of dependencies, you might decide that an earlier version would be better on the older system. SSMS 18.4 was based on a more recent Visual Studio shell. SSMS v17.9.1 is also available for download still, works fine with SQL Server 2008, and uses the older shell, so you might have less friction when trying to install it.
I have heard other developers (i.e., not db administrators) complain over the years about the complexity of getting SQL Server installed and configured properly. I installed SQL Server 2014 about six months ago for a project that I'm no longer working on. I tried installing 2008 R2 with a named instance for a new project but something went wrong and I now have an inaccessible instance. My instinct is to remove everything and to just start fresh. Is this the right instinct?
If it is the right instinct, any advice on how to fully, fully, fully uninstall all instances of SQL Server? Seems every time I try to do so, there are some bits and pieces left behind and that gets me wondering if those leftover bits are causing trouble for subsequent re-installs.
If this is not the right instinct, please set me straight. I'm hoping that all of the answers will not be "db administrators are paid to be good at this so go find one." Of course, this is probably the best and most accurate response; but I would also like to solve my problem so if this is your response then I would be grateful if you could point me to a reliable, on-demand SQL Server admin service that I can consult to get this right -- I'm happy to pay for some high quality and efficient help.
Thanks for any advice.
Bob
If you are having problems accessing the server it's a good instinct to remove the name instance and install a new one. The reason you could not access the name instance could be compatibility problem b/n sql2014 and SQL 2008R2 or configuration problem. why do you really want to install SQL 2014 instead of sql2008? my be it's better to install SQL 2014 name instance.
please look at this link to remove the name instance SQL 2008.
http://thoughtsonopsmgr.blogspot.com/2012/10/how-to-remove-sql-server-instance-from.html
I discovered that SQL Server 2008 R2 isn't supported on Windows 10: https://support.microsoft.com/en-us/kb/2681562
So I uninstalled everything related to 2008 (which required a couple of reboots and further uninstall attempts) and then uninstalled everything I could find for 2014... and then I reinstalled 2014 from scratch... and I'm golden.
I have an instance titled 'SQLEXPRESS' remaining, when I try to install SQL 2014.
I have uninstalled every program with SQL in the name from Add/remove programs.
I cannot remove this, how can I perform a complete uninstall?
Maybe try to restart your machine.
Also you can find help on the Microsoft website
I'm trying to run a schema comparison using Visual Studio 2013.5 with SQL Server Data Tools 12.0.50730.0 against a SQL Server 2016 (13.0.300) Express database.
I can configure the source connection OK, and when I hit 'Test Connection' in the connection properties dialog it says "Test connection succeeded."
However, when I hit 'Compare' in the schema comparison window it says "Initializing Comparison..." for a few seconds, then "Source is unavailable: "
This only happens if I use a SQL Server 2016 as the source, other servers work fine.
Is this a bug?
EDIT: I have also tried using SSDT 14.0.50730.0 in VS2015 and I get the same error.
In Visual Studio 2017 I had the same issue and the only solution that worked for me was:
Close Visual Studio, open it and try again :) It seems to be a caching issue. Another option is to rename the DB but that's not a nice way of workarounding this issue.
SQL Server Data Tools support for SQL Server 2016 is now GA and the latest update through Extensions and Updates in VS2013 and VS2015 will resolve this issue for you. You can also download directly from this page for VS2015, and this page for VS2013.
I had this error. Once I changed the server name from "pcname" to its IP "192.168.1.xxx" it worked.
The tools for SQL Server 2016, like the database engine itself, are still in preview. The July RTM release of SSDT doesn't include support for SQL Server 2016. You'll need to download and install the "SSDT June Preview" release from here: https://msdn.microsoft.com/library/mt204009.aspx
I have found that using username#servername as the username for connecting will fix the issue when it happens against Azure databases. Not sure if this works for non-Azure. I've had connections that have historically worked without doing this suddenly stop and then this has fixed it for me.
For instance, when using a login of mylogin and connecting to myserver.database.windows.net, if I instead use mylogin#myserver.database.windows.net as the username I won't get the "Source is unavailable" issue.
I was having the same problem connecting to AWS RDS instance. The only changes that I can tell caused the problem were upgrading to VS2015 and SSDT 14.0.61021.0
I added the following to the connection string and some combination of them fixed the problem:
;Connect Timeout=60;Encrypt=False;TrustServerCertificate=True;Persist Security Info=True
I figured this out by recreating the comparison then comparing the two .scmp files
When I had this error message, the solution was to use a login that had the sysadmin server role.
It seems to be a cache issue. I get it resolved by
Connect to some other Database on the same server
Compare schema against target project
Remove history of your main database from the connections
Restart Visual Studio
Create connection with your main database and compare schema again
Hope it works for you!
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.