Here's what happened:
install sql express 2008
install sql 2008 sp1
download and install SSMSE x64. There is a popup re incompatibility with the OS, and the help takes you back to the sp1 download page. It won't install... in fact the install that comes up appears to be for sql server express and I see no mention of SSMSE anywhere in the tangle of dialogs.
There appears to be no version of SSMSE for Win7-64 at this time. Do you know any way to fix this?
What a joke. It's a crapped out installer. You have to choose to install a new instance of sql express... but it actually installs SSMSE instead. Probably a new low in installer design.
Related
I've installed SQL Server 2014 Enterprise on a VM and am trying to install the Upgrade Advisor.
Directions indicate that I should run SqlUA.msi but I get the following error:
Setup is missing prerequisites:
Microsoft SQL Server 2014 Transact-SQL-ScriptDom, which is not installed by Upgrade Advisor Setup. To continue, install SQL Server 2014 Transact-SQL ScriptDom from below hyperlink and then run the Upgrade Advisor Setup operation again :
http://go.microsoft.com/fwlink/?LinkID=296473.
That just takes me to the download page. There is no ScriptDom file, but a further search showed me that they mean SQLDOM. So I installed SQLDOM.msi from that page above and got the following error:
Microsoft SQL Server 2012 Transact-SQL-ScriptDom
Installation of Microsoft SQL Server 2012 Transact-SQL-ScriptDom failed because a higher version already exists on the machine. To proceed, uninstall the higher version and then run Microsoft SQL Server 2012 Transact-SQL ScriptDom Setup again.
Well, that was pretty confusing. First I'm told I don't have it, then I'm told I'm trying to install an older version. I've rebooted the VM and my local laptop a bunch but without assist. Microsoft Support told me they don't support upgrade advisor.
Go to the Microsoft® SQL Server® 2014 Feature Pack page, here:
http://www.microsoft.com/en-us/download/details.aspx?id=42295
Click the Download button, then look for the download named "SqlDom.msi"; the x64 version is about 1/3 of the way down, the x86 version is about 80-85% of the way down.
These should be the latest versions of the ScriptDom.
I had the same issue, installed x64 sqldom.msi - it didn't work. So I then installed x86 version and the upgrade advisor worked. This was on server 2012R2 with SQL2012 x64.
The file Eng_Microsoft_SQLServer_TransactSql_ScriptDom_dll_32 cannot be installed because the file cannot be found in cabinet file redist.cab. This could
indicate a network error, an error reading from installation media, or a problem with this package.
Does anyone know if there is some type of bug in the installation of SQL Server 2008 R2? It seems if you have Express edition installed, then upgrade to anything (developer, enterprise, etc.) the SQL Server tools that don't come with Express will never show up because the Express edition is installed on your computer. *Even though you just paid for Enterprise edition
This has happened to me on 3 different computers. I have to copy the binn folder from a computer that actually works. Just today I decided to try to uninstall the Express edition before upgrading - instead of letting Microsoft handling the upgrade and it worked. I'm thinking maybe this is a bug...
When you upgrade from Express version, need to install Management Tools - Complete -
I know this question is old and answered, but I was having the same problem. I wanted to upgrade from Express to Developer and none of these answers helped me.
What I´ve done to be able to add features is:
Open the SQL Server Installation Center.
Click on Maintenance > Edition Upgrade and follow the steps.
Click on Installation > New installation or add features to an existing installation and follow the steps.
There you can add all the new features from your new version of SQL Server. Hope that helped..
(Instructions for 2008 R2)
If you installed Express before Enterprise/Developer you most likely have Management Tools - Basic installed. I used the following steps to get SQL Server Profiler Installed, which is bundled with the Management Tools - Complete tool set.
Step 1: Remove Management Tools - Basic
Control "Panel -> Programs -> Programs and Features"
Uninstall/Change "Microsoft SQL Server 2008 R2"
Select "Remove"
In the "Select Instance" dialog, "Instances to remove features from:" drop-down choose Remove shared features only
Check "Management Tools - Basic"
Follow the rest of the uninstall dialogs
Step 2: Install Management Tools - Complete
Run setup from the Enterprise\Developer Edition installation media
Choose "New installation or add features to an existing installation"
A few screens later choose "SQL Server Feature Installation"
Check "Shared Features -> Management Tools-Complete"
Follow the rest of the dialogs to install.
You should now have SQL Server Profiler installed.
You need to select full management tools in the features during install I believe. Just go run the installer again, select modify existing instance, and add the checkboxes for management tools
SQL Server installation, when doing an upgrade, is only going to upgrade those components currently installed. If you want the additional tools available with a higher edition you will have to rerun the installation and select to add addtional components. Then as Darren suggested select the full management tools option.
I am rebuilding my development machine. This issue is not new to me, but I don't remember the solution.
I started with SQL 2008 Developer, then VS 2008 Pro, then the SQL SP1, then VS SP1. The result is that I cannot open SSIS projects (see the error below). What is the correct order so that I can avoid the installation of SQL Server Express and still have all the features working?
---------------------------
Microsoft Visual Studio
---------------------------
Package Load Failure
Package 'DataWarehouse VSIntegration layer' has failed to load properly ( GUID =
{4A0C6509-BF90-43DA-ABEE-0ABA3A8527F1} ). Please contact package vendor for
assistance. Application restart is recommended, due to possible environment
corruption. Would you like to disable loading this package in the future? You
may use 'devenv /resetskippkgs' to re-enable package loading.
---------------------------
Yes No
---------------------------
You should install SQL 2008 Developer first, this will rule out the need for VS installing SQL which comes with it. Or you could do like others suggested and choose custom VS installation.
My favorite way is this:
SQL 2008 Developer
Visual Studio Professional 2008
Run Windows Updates
Install Resharper :-)
Install RedGate SQL ToolBelt
But it seems that to get some features to work the proper order is:
Visual Studio Professional 2008 (with SQL Unchecked)
SQL 2008 Developer
Run Windows Updates
Install Resharper/Redgate Tools
Resharper and Redgate in my opinion are far the best tools for developing in C#/SQL.
It turns out I was missing 2 important pieces of information in my question that make this installation such a pain:
I was installing the 64 bit version of SQL Server
I was installing to a non-standard location (i.e. the D: drive, because C: is an SSD with not all
that much space)
This was not successful. Here is what I ended up doing in my first (second, and third) attempt:
Install VS 2008 Professional on D:
Install VS 2008 SP 1
Install SQL Server 2008 Developer Edition (instance and shared components on D:)
Install SQL Server SP 1
Apparently VS 2008 Pro does not require a database. I am not sure why I remembered that it does. While the Visual Studio installation was eventless, I encountered the following errors during the SQL Server installation:
The INSTANCESHAREDWOWDIR command line value was not specified.
I was able to resolve that be starting setup from the command line (thanks to this MSDN forum post):
setup.exe /INSTALLSHAREDWOWDIR="D:\Program Files(x86)\Microsoft SQL
Server" /INSTALLSHAREDDIR="D:\Program Files\Microsoft SQL Server"
/ACTION=install
Then towards the end of the installation, I got this error:
Upgrade Failed due to the following Error.The error code is :-2147467259.Message:Unspecified error
There is no solution, but a workaround, described in this post on connect.microsoft.com. It consists of copying a VS config file around before and after the installation, and re-running the installer just for BIDS (which is the one component that failed).
The SQL Server SP1 installation ran without issue. VS Studio, when trying to load a solution with an SSIS project, still threw the error that I posted in my original question.
I had ignored this error that popped up towards the end of the BIDS installation:
Microsoft Visual Studio Tools for Applications 2.0
Cannot find one or more components. Please reinstall the application.
However, there was no error in the install log and it completed "successfully", so I thought it would be ok to ignore the error.
It seems that my configuration is not possible (but I know with certainty that I had the 2005 versions of VS and SQL Server on a D: drive).
I uninstalled everything once again, manually deleted whatever folders were left, and reinstalled on the C: drive, including the SQL Server shared components. I put the instance folder on the D:.
Install VS 2008 Professional on C:
Install VS 2008 SP 1
Install SQL Server 2008 Developer Edition (instance on D:, shared components on C:)
Install SQL Server SP 1
This time everything installed and I can open my SSIS project.
If you are trying to install SQL-2008 and you also have visual studio 2008 installed with service pack one (SP1) and get the error
A previous release of Microsoft Visual Studio 2008 is installed on
this computer. Upgrade Microsoft Visual Studio 2008 to the SP1 before
installing SQL Server 2008”
Then welcome to the Microsoft beta testing program even if you purchased the faulty software.
With XP the most common solution seem to be renaming the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DevDiv\VS\Servicing\9.0
and replacing 9.0 with 9.0Old. However this does not solve the problem if you are using windows 7 and the only solution I managed to find that worked was to uninstall VS2008 and all the components and to then install SQL-2008 and finally reinstall VS2008.
Install Visual Studio Professional 2008.
Install SQL 2008 Developer
Apply SQL SP1
Apply VS SP1
Then all should be good.
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.