OS: Windows 10 64 Bit
I ran the SQL Server 2016 Express ISO setup. All the components installed except for R Services. I guess it couldn't download that installation package from destination. When I connect to this instance via SSMS and click on Polybase, I get the following error.
Object reference not set to an instance of an object.
(Microsoft.SqlServer.Management.PolybaseManagement)
How can I rectify this? Please advise. Repair SQL Server instance also didn't work.
Extract from RSetup Log file.
2018-04-10T06:30:24 INFO Command invoked: E:\Dev Tools\en_sql_server_2016_express_with_advanced_services_with_service_pack_1_x64_9540756\x64\RSetup.exe /install /component SRS /version 8.0.3.15000 /language 1033 /destdir C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\R_SERVICES /logfile C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20180410_114432\RSetup.log /instance SQLEXPRESS
2018-04-10T06:30:24 INFO Searching for cache dir: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\R_SERV_CACHE
2018-04-10T06:30:24 INFO Using default cache dir: C:\Users\balaji.v\AppData\Local\Temp\
2018-04-10T06:30:24 INFO Backing up source dir: C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\R_SERVICES\ => C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\R_SERVICES_4d040c58-b12e-414b-82d1-5a11dde969b7
2018-04-10T06:30:24 ERROR Error renaming source dir: Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\R_SERVICES\' is denied.
2018-04-10T06:30:24 INFO Exiting with code 5
Feature: R Services (In-Database)
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component error code: 0x84B40002
Error description: The SQL Server feature 'sql_inst_mr' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.4001.0&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
Feature: SQL Server Replication
Thanks
Balaji.V
Related
it is the first time and my first post in "stackoverflow" and I hope, that you can help me regarding my project.
Once I start the corresponding Job in SSMS, which I have created, I get the following error message:
Executed as user: XXXX Microsoft (R) SQL Server Execute Package
Utility Version 13.0.5026.0 for 32-bit Copyright (C) 2016 Microsoft.
All rights reserved. Started: 15:36:23 Error: 2021-10-11
15:36:23.51 Code: 0xC0011007 Source:
{BE14993C-9347-4920-8C3C-97E254866D05} Description: Unable to
load the package as XML because of package does not have a valid XML
format. A specific XML parser error will be posted. End Error Error:
2021-10-11 15:36:23.51 Code: 0xC0011002 Source:
{BE14993C-9347-4920-8C3C-97E254866D05} Description: Failed to
open package file "D:\Test\XXX.dtsx" due to error 0x80070003 "The
system cannot find the path specified.". This occurs when loading a
package and the file cannot be opened or loaded correctly into the XML
document. This can be the result of specifying an incorrect file name
when calling LoadPackage or the specified XML file has an incorrect
format. End Error Could not load package "D:\Test\XXXX.dtsx" because
of error 0xC0011002. Description: Failed to open package file
"D:\Test\XXXX.dtsx" due to error 0x80070003 "The system cannot find
the path specified.". This occurs when loading a package and the file
cannot be opened or loaded correctly into the XML document. This can
be the result of specifying an incorrect file name when calling
LoadPackage or the specified XML file has an incorrect format.
Source: {BE14993C-9347-4920-8C3C-97E254866D05} Started: 15:36:23
Finished: 15:36:23 Elapsed: 0.016 seconds. The package could not be
found. The step failed.
I have already tried the following points:
The permissions which I log in on the appropriate server, etc.
I have created a "Credential" & "Proxy" and configurated/managed it
Check the "DelayValidation" in Visual Studio (is "True")
TargetServerVersion is on "SQL Server 2019"
Security => ProtectionLevel is on "EncryptSensitiveWithUserKey"
Many thanks for your assist.
Best Regards,
Safak
I see that the path of the package using is a path server server. If that's the case replace it with UNC path in format //machinename/ c$/...
The account executing package from job has no access to path. If that's the case give account access to the path
I'm trying to install sql server 2016 standard version on windows 10 enterprise and it keeps giving me this error on installation.
There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
The summary file contains the information below:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068052293
Start time: 2016-10-14 11:45:41
End time: 2016-10-14 11:47:08
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: DESKTOP-ARR1KHB
Machine processor count: 8
OS version: Microsoft Windows 10 Enterprise (10.0.14393)
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2016 MSSQLSERVER MSRS13.MSSQLSERVER Reporting Services - Native 1033 Standard Edition 13.0.1601.5 No Yes
SQL Server 2016 Data Quality Client 1033 Standard Edition 13.0.1601.5 No Yes
SQL Server 2016 LocalDB 1033 Express Edition 13.0.1100.286 No Yes
SQL Server 2016 Reporting Services - SharePoint 13.0.1601.5 No Yes
Package properties:
Description: Microsoft SQL Server 2016
ProductName: SQL Server 2016
Type: RTM
Version: 13
SPLevel: 0
Installation location: E:\Documents\Programs\Microsoft.SQL.Server.2016.Standard.x64\x64\setup\
Installation edition: Standard
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161014_114540\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTROPENLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Persian_100_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DESKTOP-ARR1KHB\masoud-pc
SQLTELSVCACCT: NT Service\SQLTELEMETRY
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 8
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161014_114540\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161014_114540\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161014_114540\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161014_114540\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=sqlncli.msi%40RollbackCleanup%401723
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161014_114540\SystemConfigurationCheck_Report.htm
here is the link to log file:
sqlncli_Cpu64_1.log
can anyone help?
I struggled with this error a couple of days, when trying to install SQL Server 2016. Finally got it working by removing MS Visual C++ 2010 Runtime from Programs and Features. SQL Server installs this in setup process again. So, my advise is to remove C++ 2010 Runtime. This solution fixes same installation that occurs with SSMS.
So, check if there is MS Visual C++ 2010 Runtime installed and uninstall it.
I faced same issue on my windows 10 machine, After checking error log in event viewer I found following detail for error
"Product: Microsoft SQL Server 2012 Native Client -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor. Action SNAC_SetClientSSNLDefaults_32, entry: SNAC_SetClientSSNLDefaults, library: C:\WINDOWS\Installer\MSI4206.tmp"
On googling further i found that the entry for 32-bit sql native client dll in sqlncli.msi file is not pointing to the actual dll for sql server native client 2012 dll in system32 folder. You can view or edit this entry using ORCA MSI Editor. On opening the sqlncli.msi file using ORCA editor and searching for SNAC_SetClientSSNLDefaults_32 key you can see that the value could be $DP_sqlncli10_dll_32 = 3 or $DP_sqlncli_dll_32 = 3 or any previous version of native client but for sql server native client 2012 it should be $DP_sqlncli11_dll_32 = 3. I changed and saved this value on every sqlncli.msi file found on my system using ORCA editor. You can search in C:\ProgramData.. folder and setup installation folder for sqlncli.msi file or better if you can use any search tool like everything. Thereafter I was able to successfully install SQL Server native client 2012 without any error.
For more details you can refer this link
Installing Microsoft SQL Server 2012 Native Client
As one can't uninstall sql server completely, and there always will be some components remained, I just reinstalled my windows and this time I installed sql first (before vs2015) and the problem solved. I think there are some issues installing this kind of software and has problem with some dlls.
I had this issue trying to update from 2008 -> 2017. I had to update to 2012 SP4 first and then to 2017.
I have been using SonarQube for code analyzing at a basic level however now I would like to measure the code against FX-COP rules. Hence I am attempting to use MSBuild SonarQube scanner. I read the documentation thoroughly and have setup my project likewise however when I execute it gives me error.
Below is the extract from the log:
MSBuild SonarQube Runner Bootstrapper 1.0.2.0
Default properties file was found at C:\....\1c36691bf5270463\SonarQube.Analysis.xml
Loading analysis properties from C:\....\1c36691bf5270463\SonarQube.Analysis.xml
Pre-processing started.
Preparing working directories...
Checking for updates...
MSBuild SonarQube Runner Pre-processor 1.0.2.0
Loading analysis properties from C:\...\1c36691bf5270463\SonarQube.Analysis.xml
Updating build integration targets...
Fetching analysis configuration settings...
Generating rulesets...
Pre-processing succeeded.
Microsoft (R) Build Engine version 12.0.21005.1
[Microsoft .NET Framework, version 4.0.30319.34209]
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
Build started 11/20/2015 1:46:41 PM.
Project "C:\Project1.sln" on node 1 (rebuild target(s)).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
Build succeeded.
9 Warning(s)
0 Error(s)
Time Elapsed 00:01:07.86
MSBuild SonarQube Runner Bootstrapper 1.0.2.0
Default properties file was found at C:\...\1c36691bf5270463\SonarQube.Analysis.xml
Loading analysis properties from C:\...\1c36691bf5270463\SonarQube.Analysis.xml
Post-processing started.
MSBuild SonarQube Runner Post-processor 1.0.2.0 gives several warnings similar to one below:
WARNING: File is not under the project directory and cannot currently be analysed
by SonarQube.
File: C:\Users\...\AppData\Local\Temp\2\.NETFramework,Version=v4.0.AssemblyAttributes.cs,
project: C:\...\1c36691bf5270463\SOURCE\x\y.csproj**
Calling the sonar-runner:
SONAR_RUNNER_OPTS is not configured. Setting it to the default value of -Xmx1024m
C:\...\1c36691bf5270463\.sonarqube\bin\sonar-runner\bin\..
SonarQube Runner 2.4
Java 1.8.0_51 Oracle Corporation (64-bit)
Windows Server 2008 R2 6.1 amd64
SONAR_RUNNER_OPTS=-Xmx1024m
INFO: Error stacktraces are turned on.
INFO: Runner configuration file: C:\...\1c36691bf5270463\.sonarqube\bin\sonar-runner\bin\..\conf\sonar-runner.properties
INFO: Project configuration file: C:\TeamCity\buildAgent\work\1c36691bf5270463\.sonarqube\out\sonar-project.properties
INFO: Default locale: "en_US", source code encoding: "UTF-8"
INFO: Work directory: C:\...\1c36691bf5270463\.sonarqube\out\.sonar
INFO: SonarQube Server 5.1.1
13:47:51.150 INFO - Load global repositories
13:47:51.743 INFO - Load global repositories (done) | time=593ms
13:47:51.758 INFO - Server id: 20151120125423
13:47:51.758 INFO - User cache: C:\...\cache
13:47:51.758 INFO - Install plugins
13:47:51.836 INFO - Install JDBC driver
.
.
.
13:47:55.518 INFO - ------------- Scan file1
13:47:55.534 INFO - Load module settings
13:47:55.658 INFO - Load rules
13:47:56.017 INFO - Base dir: C:\...\1c36691bf5270463\SOURCE\xxx
13:47:56.017 INFO - Working dir: C:\...\1c36691bf5270463\.sonarqube\out\.sonar\AC1_AC1_497EBFF2-C710-4843-8263-F534AF803D3E
13:47:56.017 INFO - Source encoding: UTF-8, default locale: en_US
13:47:56.532 INFO - Quality profile for cs: Sonar way
13:48:00.635 INFO - Sensor org.sonar.plugins.csharp.CSharpFxCopProvider$CSharpFxCopSensor#73c82ec1
INFO: -----------------------------------------------------------------
INFO: EXECUTION FAILURE
INFO: -----------------------------------------------------------------
Total time: 10.156s
Final Memory: 16M/306M
INFO: -----------------------------------------------------------------
13:48:00.791 Creating a summary markdown file...
Press any key to continue . . .
You need to run all your commands in a Developer Command Prompt for Visual Studio 2013 or higher and:
use at least MSBuild 12.0
have .NET 4.5.2+ installed
You have this error because the FxCop Results are not generated.
Do you see in the MSBuild's logs, execution of FxCop? This is visible inside the RunCodeAnalysis section of MSBuild's logs.
You need to run this from command line and use the "-X" flag on your command, this will give you verbose debugging, I would highly reccomend doing the following for troubleshooting.
sonar-runner.exe <arg> <arg> -X > sonar-runnerLog.txt
Then read or dump that log back here. either way you'll know a lot more about what the actual problem is.
You can get Visual Studio Express 2013 (or 15) for free and both of those come with their respective developer command prompts.
I have an SSIS package that reads data using a custom query and stores it into a target excel source. I am able to run the SSIS package successfully on a server where no excel is installed by doing a right click and selecting the Run Package option. When I add the same SSIS package to Integration services and run the package, it still executes successfully. But, when I schedule the package using SQL Server agent job, it fails with the below error:
"Executed as user: Username. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Argument "Excel" for option "connection" is not valid. The command line parameters are invalid. The step failed."
Specification of SQL Server: SQL SERVER 2008 R2
Executing as SQL Server Agent Job.
Tried the following:
1) Checked the 'Use 32 bit' check box under Execution options tab in Step menu and unchecked all the check boxes in Datasources tab. Got the below error:
"Executed as user: Username. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 9:44:03 PM Error: 2015-06-08 21:44:04.21 Code: 0xC002F304 Source: File System Task File System Task Description: An error occurred with the following error message: "The device is not ready. ". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 9:44:03 PM Finished: 9:44:04 PM Elapsed: 1.219 seconds. The package execution failed. The step failed."
2) Created a proxy account that had sysadmin, public, serveradmin roles. Modelled the package to run as proxy account. Got the below error:
"Executed as user: Username. The process could not be created for step 1 of job (reason: 1314). The step failed."
The command line looks almost similar to the below:
/DTS "\File System\PackageName" /SERVER SERVERNAME /CONNECTION "InputFileConn.xlsx";"F:\Folder\InputFile.xlsx" /CONNECTION "OutputFileConn.xlsx 1";"F:\Folder\Output\OutputFile.xlsx" /CONNECTION "Excel Connection Manager 1";"\"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=F:\Folder\Output\OutputFile.xlsx;Extended Properties=""EXCEL 12.0;HDR=YES"";\"" /CONNECTION "SERVERINSTANCE.DBName";"\"Data Source=ServerInstance;Initial Catalog=DatabaseName;Provider=SQLNCLI10.1;Integrated Security=SSPI;Auto Translate=False;Application Name=SSIS-Package-{D4E09BF5-DF25-3DE7-BCAE-B667C38F85B7}SERVERNAME\SQLSERVER.DatabaseName;\"" /X86 /CHECKPOINTING OFF /REPORTING E
Is it necessary to install excel in the server to make the SQL Server agent job work?
Based on the discussion above, the job was referring to F drive but F is a different drive to expected when running on the server.
I'm installing SSMS 2014 but while installing I'm getting below error:-
"There is a problem with this Windows Installer package. A DLL required
for this installation to complete could not be run. Contact your
support personnel or package vendor."
Can anyone tell me what is the problem?
Here is the error log:
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2331
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2331.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_common_core.msi%40Do_LogInstallStart_64%402331
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Common Files
Component error code: 2331
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sql_common_core_Cpu64_1.log
Error description: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2331.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sql_common_core.msi%40Do_LogInstallStart_64%402331
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Native Client Access Component
Component error code: 1723
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150528_153228\sqlncli_Cpu64_1.log
Error description: There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=sqlncli.msi%40RollbackCleanup%401723
I solved this problem by NOT putting in a DEFAULT target server URL when prompted. It is an optional field, so leave it blank, click next, and the installation completes without issue. You can add that link later once the application installs.
Try installing it as administrator. Right click on setup.exe file and click run as administrator.