I'm getting the exact same error message as see in this blog post:
http://shawndowler.com/blog/2012/06/25/microsoft-sql-server-installation-issue-fix/
I ran the SQL Server 2012 setup exe (renamed it to setup.exe it was the expresss edition) as Admin from the command prompt specifying to install the updates prior which exists in my 'C:\Updates' and got the exact same error message as the blogger "An error occurred during the installation of an assembly"
Someone commented it resolved their issue for SQL 2012 in Windows 10 (I'm using express, they didnt specify which version).
Anyone else had issues with SQL 2012 or other installing on Windows 10 complaining about Microsoft.VC80.MCF or similar?
For Windows 10, you need at least SQL Server 2012 Service Pack 2 - RTM version isn't supported. For some reason, it is only mentioned in documentation regarding SQL Server 2014: Hardware and Software Requirements for Installing SQL Server.
Hopefully, with Express edition you can download the correct version with SP already integrated into it. However, it might be wiser to install SP3 instead and save yourself some hassle in the future.
Related
I had an old version of SQL Server on my laptop which I uninstalled. Now I am trying to install SQL Server 2019 Developer edition but I get an error:
Error Code(Decimal): 2068052293 Error Description: Please install the Visual C++2017 Redistributable from https://aka.ms/vs/15/releaset..exe before running this installer.
I also installed Visual C++ 2017 Redistributable from the suggested path but still same error is happening.
Environment: HP/Pavilion/Windows 10 Pro/4g/500HDD/Corei5
PS: attaching screenshot for kind reference
Screenshot is missing.
Check for the following,
Is, VC++ 2017 is successfully installed? If yes, its worth doing a restart. Sometimes certain dll's should be registered in Windows environment, which will happen after a restart. Start SQL Server 2019 again after restarting.
Ensure both SQL Server 2019 and VC++ 2017 are installed with same user login. Hopefully you should be local admin for the login.
More suggestion can be provided based on screenshot error. Good luck!
This is my suggestion. It worked for me. Partition your local disk and install MSSQL in the new drive. That's all. Problem solved. This problem often happens with windows 11.
This is probably a trendy question, But I promise you my problem is different.
Lately my server windows crashed and I was forced to install new windows.
I took a backup of the database "ReportServer" and "ReportServerTempDB".
Until then I didn't remember the SQL Server version was installed before the windows crashed.
Now when I try to attach these databases and run the report server, it tells me the following message
"The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'. (rsInvalidReportServerDatabase)"
I've made some research, and understood that my current installed SQL Server version is higher than the database, I tried installing some cumulative updates but when I run the updates it seems not to be recognizing the SQL Server version installed.
Current installed version: Microsoft SQL Server Enterprise: Core-based Licensing (64-bit) 2014 v12.0.2000.8
Previously installed version: Microsoft SQL Server 2012 Enterprise Not sure though.
My problem is that I can't open the ReportServer database because it's version is older and I can't install the right cumulative update to fix this issue. Can anyone point me to the right direction?
Much appreciated Thanksss!!.
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.
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'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.