How do I fix a Cross language installation problem in SQL Server 2008?

Question

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?

Answer 1

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.

Answer 2

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.

Answer 3

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.

Answer 4

This link will solve the cross language installation problem:

http://www.arguingwithmyself.com/archives/106-how-to-install-sql-server-2008-express-with-visual-web-developer-2008-express

Answer 5

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.

Answer 6

All I had to do was exit the installer and start the process again. For some reason it worked the second time around.