I bought a copy of SQL Server 2012 Developer Edition, and no matter what I try, I can't seem to be able to install SQL Server Management Studio 64-bit from the install disc. I've tried installing and uninstalling several times, and only the 32-bit version shows up. Even the C:\Program Files\Microsoft SQL Server\110\Tools\Binn\ManagementStudio folder exists, but not the 64-bit executable. Anyone know what I'm doing wrong?
I'm running Windows 7 Enterprise 64-bit SP1 with 16 GB of RAM...
Edit: a little further info... sqlservr.exe is running in 64-bit. Just not ssms.exe...
There is no such thing. The application itself, like Visual Studio, only ships as a 32-bit application, regardless of the operating system and regardless of the instance(s) you use it with.
Related
We have SSMS 2012 installed on several servers (mix of physical and virtual hardwares) with the 64-bit DTExec.exe Version 11.0.2100.60 that we use to run SSIS packages. The SSIS packages are stored in a Microsoft SQL Server 2016 on another physical server.
On one of the SSMS 2012 servers, I installed SQL Server Data Tools for VS2017. Since then, one of our SSIS packages would not run to completion. It aborts about halfway, specifically, when it is about to run (or already running?) the script component of the package. When it aborts, %ERRORLEVEL% is set to a high negative number (-1073741819). I make sure the 64-bit DTExec.exe Version 11.0.2100.60 is the one being used to run the package by putting its path, C:\Program Files\Microsoft SQL Server\110\DTS\Binn, ahead of any other versions’ paths in the PATH environment variable. (It also shows “64-bit” and the version number inside the DOS box where the package is running.)
If I run the same failing package from another SSMS 2012 server using its local copy of the same 64-bit DTExec.exe 11.0.2100.60, the package runs fine. So I suspect the 64-bit DTExec.exe 11.0.2100.60 on the server where I installed SSDT 2017 somehow got “corrupted” (?).
I have uninstalled SSDT 2017 but still the package fails.
Curiously, if I use the 32-bit version instead of DTExec.exe with the same version 11.0.2100.60, the package runs fine. So all the more reason for me to suspect that the 64-bit DTExec.exe version was “corrupted”.
Is there any way to “repair” the 64-bit DTExec.exe Version 11.0.2100.60 to restore it to its former glory? I realize we can just use the 32-bit version but we’d like to use the same version of DTExec.exe across all our SSMS 2012 servers so they all share identical PATH environment variables, .BAT files, etc..
Any leads appreciated – thank you!
EDIT: I'd also like to add that before failing, a DOS window pops up then very quickly closes. The DOS window seems blank but it could be that it just closes very fast for me to see. On other SSMS servers where the packages runs to completion, no DOS window pops up.
Post was rewritten after additional investigation. The error message was:
Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation.
The installation target is a Hyper-V guest machine as follows: 2G RAM, 14.5 GB free on the C: drive, 2.5 GHz CPU. .NET 3.5 is turned on.
On this page https://www.microsoft.com/en-us/download/details.aspx?id=42299 the following note was confusing to me (bold is my emphasis):
Note: Microsoft® SQL Server® 2014 Express includes both 32-bit and 64-bit versions. SQLEXPR32_x86 is a smaller package that can be used to install SQL Server 2014 Express onto only 32-bit operating systems. SQLEXPR_x86 is the same product but supports installation onto both 32-bit and 64-bit (WoW) operating systems. SQLEXPR_x64 is a native 64-bit SQL Server 2014 Express and supports installation onto only 64-bit operating systems. There is no other difference between these packages. Microsoft® SQL Server® 2014 Express is not supported on IA64 systems.
The wording seemed to indicate the x86.exe would work on both 32/64 bit systems which was consistent with my findings. But I thought that also indicated the 32bit.msi would also work on both 32/64 bit systems. I am beginning to believe I misunderstood and would appreciate confirmation the error is my reading of the note.
Your error message answers your question. Your trying to install it on an unsupported OS. Check out https://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx which lists the requirements. It appears that in a Hyper-V Environment all versions of SQL 2014 are only supported on a Windows 2008 SP2. 2008 R2 SP1, or 2012 OS.
My particular problem was the misunderstanding that the 32 bit MSI would work on a 64 bit OS. Once I changed to the 64 bit MSI SQL Express 2014 loaded just fine into the VM. The 32 bit x86 .exe setup file did in fact work on the 64 bit OS, just not the MSI setup file.
Note there are two different _x86 file names: SQLEXPR32_x86 only works on 32-bit systems. SQLEXPR_x86 (note the missing "32") will work on both 64-bit and 32-bit systems, but still runs as a 32-bit process.
I'm learning PHP and I'm a newbie in apache, mysql,etc.
I tried to install WAMPServer (The current newest version 2.5) but I get the error:
msvcr110.dll is missing.
I have followed some instructions given here: WAMP shows error 'MSVCR100.dll' is missing when install
However, none of the advice worked for me. I have already installed Visual C++ for windows 32 bits and Visual C++ Redistributable for Visual Studio 2012. After that I installed Visual C++ 2008, it didn't worked either.
And even after that I installed vcredist_x86.exe. This gave me an option to repair my Visual C++, and so I did.
In all my tries I restarted my computer.
I didn't install Visual c++ for windows 64 bits because my os is running a 32 version.
Any ideas?
Thanks for your attention,
berga007
Please make sure you have the latest version of all of these Microsoft C/C++ Redistributable runtime libraries. You dont need the whole compiler, just these C/C++ runtime libraries.
The 2008 Redist (32bit) is used by wampmanager even if you installed the 64bit WAMPServer.
The 2010 Redist is used by some versions of Apache ( depending on compiler used ).
The 2012 Redist is used by some versions of Apache ( depending on compiler used ).
FOR WAMP 32bit
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
If you are using WampServer 2.4/2.5 32bit and therefore Apache 2.4.x
Microsoft Visual C++ 2012 is required And select vcredist_x86.exe
Due to the naming convention used by Microsoft dowmloading these libraries can get a little confusing so download them one at a time and install that download before downloading the next and installing that.
To check that you have all the required runtimes, launch 'Programs and Features' by
Start -> Control Panel -> Programs and Feature
For a 32bit system it should look something like this, ignore the fact that mine has what look like multiple versions of the same library, its just because when you download a newer version it does not remove the older revisions :-
32bit System example
UPDATE FOR 2018 (WAMPSERVER 3.x)
You need the following Visual Studio Redistributables:
2008
2010
2012
2013
2017
Get both the x86 and x64 versions if you're on a x64 machine.
Also, make sure you set skype to NOT use port 80, otherwise WAMP won't start when Skype is open.
Microsoft Visual Studio
Could not load file or assembly
'Microsoft.SqlServer.Management.Sdk.Sfc, Version=11.0.0.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its
dependencies. The system cannot find the file specified.
I cannot "see" the referenced DLL even though it is in the proper spot. I can therefore not bind the datasource to the control. What might I be failing to do?
Please see original question and answer here: Could not load file or assembly Microsoft.SqlServer.management.sdk.sfc version 11.0.0.0
Problem: This issue happens when assembly Microsoft.SqlServer.management.sdk.sfc version 11.0.0.0 not found by visual studio 2012.(Sql server 2012)
Solution: just go to http://www.microsoft.com/en-us/download/details.aspx?id=35580 and download:
ENU\x64\SharedManagementObjects.msi for X64 OS or
ENU\x86\SharedManagementObjects.msi for X86 OS,
then install it, and restart visual studio.
Problem: This issue happens when assembly Microsoft.SqlServer.management.sdk.sfc version 10.0.0.0 not found by visual studio 2010.(Sql server 2008)
Solution: just go to http://www.microsoft.com/en-us/download/details.aspx?id=26728 and download:
1033\x64\SharedManagementObjects.msi for X64 OS or
1033\x86\SharedManagementObjects.msi for X86 OS,
(In most cases downloading this is better http://go.microsoft.com/fwlink/?LinkId=123708&clcid=0x409)
then install it, and restart visual studio.
From here:-
From the error message, we can see there is some missing component in
VS 2012 installation. The assembly in question -
Microsoft.SqlServer.Manangement.Sdk.Sfc version 11 - is a component
DLL for SMO assemblies (even though SFC was originally created for
more ambitious SSMS extension), and it is included in SQL Server 2012
Shared Management Objects.
[SQL 2012 Shared Management Objects] has dependency on [SQL System
CLR types] component, so you have to install SQL Server System CLR
Types first.
[SQL Server 2012 System CLR Types] can be found in the middle of SQL
2012 Feature Pack web page (
http://www.microsoft.com/en-us/download/details.aspx?id=29065 )
Just want to share my experience on this.
I, too, encountered this error. I'm using MS Visual Studio 2013 and I have an MS SQL Server 2008, though I have had MS SQL Server 2012 Installed before.
I was banging my head on this error for a day. I tried installing SharedManagementObject, SQLSysClrTypes and Native Client, but it didn't work. Why? Well I finally figured that I was installing 2008 or 2012 version of the said files, while I'm using Visual Studio 2013!! My idea is since it is a database issue, the version of the files should be the same with the MS SQL Server installed on the laptop, but apparently, I should have installed the 2013 version because the error is from the Visual Studio and not from the SQL Server.
I had this problem after installing SQL Server Express 2014. Apparently 2012 points to some files that are in 2014 and I completely erased all old versions of SQL Server. After much frustration I ended up reloading Visual Studio 2013 and it set up all of the files it needed and now works with SQL Server Express 2014
I have VS2012 Ultimate installed. In the Installed products it states I have SQL Server Data Tools 11.1. When I go to SQL Server 2012 and click on the SQL Server Data Tools Menu option, VS2010 starts up.
I changed the target to point to C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe instead of C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
So now VS2012 starts up but under new projects I DO NOT have the option to create a new SSIS package. Nor the option to download the data tools off the web.
I did go through VS2010 and download DataTools for 2010 and also selected the download for 2012. VS2010 now has Business Intelligence but VS2012 still does not have this template.
Please help. Slowly going mad.
SQL Server Data Tools part for Business Intelligence (SSAS, SSIS, SSRS) has been released as an add-on for Visual Studio 2012 in March 2013.
It can be downloaded here
If you are running on a 64 bit system and have any error message, use option 1 during the installation (New install). It will only add the BI Studio and not try to reinstall anything else.
Cnfusingly Microsoft have 2 different products called SQL server data tools, the one from the installation media which gives you the BI templates in VS2010 and one that you can download, which just adds the database project type to VS2010/12. Currently there are no BI templates available for VS2012, which is incredibly frustrating, it's due to the version of the Visual Studio Shell used by the tools on the installer only supporting 2010. I guess we'll just have to wait for an update to that :(
New download and more compatibility languages as of January 2019.
SQL Server Data Tools in Visual Studio 2012
Supported Operating Systems:
Windows 10 (x86 and x64)
Windows 8, 8.1 (x86 and x64)
Windows 7 SP1 (x86 and x64)
Windows Server 2012 (x64), R2 (x64)
Windows Server 2008 R2 SP1 (x64)