SQL Server 2016 Dev edition (and many others) fails during setup

October 12, 2016, 12:03 am

≫ Next: Install SSDT 2012 and VS2013 Pro on workstation?

≪ Previous: TempDB Placement in SQL Cluster : Local SSD or Shared SAN?

I have a new laptop with windows 10 and wanted to install a SQL Server version. But every single version I try to install is failing when it is checking the setup rules. I tried a lot of things, also cleaning up the registry. But maybe I missed something.

Part of the Detailed logfile:

(07) 2016-10-11 22:36:09 Slp: Rule 'FacetWOW64PlatformCheck' results: Supported32bitSetup=True
(07) 2016-10-11 22:36:09 Slp: Evaluating rule : FacetWOW64PlatformCheck
(07) 2016-10-11 22:36:09 Slp: Rule running on machine: ALTEN-L428
(07) 2016-10-11 22:36:09 Slp: Rule evaluation done : Succeeded
(07) 2016-10-11 22:36:09 Slp: Rule evaluation message: SQL Server Setup is supported on this operating system platform.
(07) 2016-10-11 22:36:09 Slp: Send result to channel : RulesEngineNotificationChannel
(07) 2016-10-11 22:36:09 Slp: Saving results to datastore...
(07) 2016-10-11 22:36:09 Slp: Saved to directory.......C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161011_223606\SystemConfigurationCheck_Report.htm
(07) 2016-10-11 22:36:09 Slp: Sco: Attempting to create directory C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161011_223606\resources
(07) 2016-10-11 22:36:09 Slp: Sco: Attempting to create directory C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161011_223606\resources, security descriptor
(07) 2016-10-11 22:36:09 Slp: Sco: Directory 'C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161011_223606\resources' already exists, skipping creation, moving to set security descriptor.
(07) 2016-10-11 22:36:09 Slp: Sco: Attempting to set security descriptor for directory C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161011_223606\resources, security descriptor
(07) 2016-10-11 22:36:09 Slp: Sco: SDDL is NULL/empty and overwriteSecurityDescriptor is false, so nothing to do, return.
(07) 2016-10-11 22:36:09 Slp: Generating HTML report by applying XsltTransformation and saving to Log folder...
(08) 2016-10-11 22:36:09 Slp: Search for updates completed as 'Succeeded', number of updates found: 0
(01) 2016-10-11 22:36:09 Slp: Error: Action "Microsoft.SqlServer.Configuration.UIExtension.WaypointAction" threw an exception during execution.
(06) 2016-10-11 22:36:09 Slp:
(06) 2016-10-11 22:36:09 Slp: Microsoft Update Details:
(06) 2016-10-11 22:36:09 Slp: Category ID searched on Microsoft Update: 892C0584-8B03-428f-9A74-224FCD6887C0
(01) 2016-10-11 22:36:09 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-10-11 22:36:09 Slp: at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-10-11 22:36:09 Slp: at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-10-11 22:36:09 Slp: (06) 2016-10-11 22:36:09 Slp: Major version of the Windows Update Agent: 8
(01) 2016-10-11 22:36:09 Slp: (06) 2016-10-11 22:36:09 Slp: Major version of the Windows (06) 2016-10-11 22:36:09 Slp: Minor version of the Windows Update Agent: 0
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(06) 2016-10-11 22:36:09 Slp: Version of Wuapi.dll: 10.0.14393.0
(06) 2016-10-11 22:36:09 Slp:
(06) 2016-10-11 22:36:09 Slp:
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-10-11 22:36:09 Slp: --- End of inner exception stack trace ---
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-10-11 22:36:09 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-10-11 22:36:09 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-10-11 22:36:09 Slp: at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-10-11 22:36:09 Slp: at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-10-11 22:36:09 Slp: at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-10-11 22:36:09 Slp: --- End of inner exception stack trace ---
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(06) 2016-10-11 22:36:09 Slp: Completed Action: SearchUpdatesAction, returned True
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-10-11 22:36:09 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-10-11 22:36:09 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.

If more information is needed, please let me know.

Hopefully someone can help me out.

Shane

↧

Install SSDT 2012 and VS2013 Pro on workstation?

October 12, 2016, 8:51 am

≫ Next: LinkId=94001

≪ Previous: SQL Server 2016 Dev edition (and many others) fails during setup

Our server has Windows Server 2008, Sql Server 2008 R2 and VS2008 Pro installed. They're used to create Business Intelligence Projects such as SSRS reports and SSIS packages. We already have SSRS and SSIS deployed, and we're already using ReportServer to view the reports. Unfortunately, we need to connect to the server via Remote Desktop to create these packages and reports.

These tools were already installed when I got here and we don't have the CDs for any of them.

So I just received the MSDN CDs for SQL Server 2012 and VS2013 Professional. I want to install in my workstation so that I can work locally and then deploy/copy the projects to our server. From my understanding, I need both SQL Server 2012 and VS2013 Pro to create SSDT packages, but I'll be deploying to the server.

Is this something that's possible?

Thanks.

↧

LinkId=94001

October 12, 2016, 8:55 pm

≫ Next: Install SQL 2014 Server (+cal) version

≪ Previous: Install SSDT 2012 and VS2013 Pro on workstation?

Hi all, I would like to know what the warning with linkid 94001 is all about and how to solve this?

i've created an exception for the tcp 1433 and udp 1434 and also an exception for the database engine service but still didnt solved.

can anybody please help me?

↧

Install SQL 2014 Server (+cal) version

October 13, 2016, 8:28 am

≫ Next: Trying to install SQL Server 2016 Express on Windows 10

≪ Previous: LinkId=94001

I have SQL Server Server licenses (not the core version) available from way back and software assurance. I need to do an install of SQL 2014 using one of those licenses. The only way I see to run with that license (which has CPU limitations) is this:

install SQL 2008r2 Enterprise
Upgrade to SQL2012, specifying the server license during setup
Upgrade to 2014.

Is there a way to do this directly without all the steps?

Thanks

ZzZz

↧

Trying to install SQL Server 2016 Express on Windows 10

October 13, 2016, 12:15 pm

≫ Next: Why won't SQL Server install?

≪ Previous: Install SQL 2014 Server (+cal) version

I'm trying to install SQL Server 2016 Express 2016 on a new Windows 10 Laptop. I have made sure I have the latest Windows updates installed and the machine is not on any Network but the install process keeps failing. The install error log file is below.

Can anybody please provide any assistance?

Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068052081
Start time:                    2016-10-13 19:58:20
End time:                      2016-10-13 20:00:49
Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
Next step for AdvancedAnalytics: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.

Machine Properties:
Machine name:                  DESKTOP-NNQQPQJ
Machine processor count:       4
OS version:                    Microsoft Windows 10 Home (10.0.10586)
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

Package properties:
Description:                   Microsoft SQL Server 2016
ProductName:                   SQL Server 2016
Type:                          RTM
Version:                       13
SPLevel:                       0
Installation location:         C:\Users\paul\Downloads\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition:          Express

Product Update Status:
None discovered.

User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      true
AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Disabled
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:         Disabled
CLTCTLRNAME:                   <empty>
CLTRESULTDIR:                  <empty>
CLTSTARTUPTYPE:                0
CLTSVCACCOUNT:                 <empty>
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 <empty>
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    true
ENU:                           true
EXTSVCACCOUNT:                 NT Service\MSSQLLaunchpad$SQLEXPRESS
EXTSVCPASSWORD:                <empty>
FEATURES:                      SQLENGINE, REPLICATION, ADVANCEDANALYTICS, FULLTEXT, RS, CONN, BC, SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD:                 <empty>
HELP:                          false
IACCEPTROPENLICENSETERMS:      true
IACCEPTSQLSERVERLICENSETERMS: true
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:                    SQLEXPRESS
INSTANCENAME:                  SQLEXPRESS
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:                          AllFeatures_WithDefaults
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  Latin1_General_CI_AS
SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
SQLSVCINSTANTFILEINIT:         false
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           DESKTOP-NNQQPQJ\paul
SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS
SQLTELSVCPASSWORD:             <empty>
SQLTELSVCSTARTUPTYPE:          Automatic
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBFILECOUNT:            1
SQLTEMPDBFILEGROWTH:           64
SQLTEMPDBFILESIZE:             8
SQLTEMPDBLOGDIR:               <empty>
SQLTEMPDBLOGFILEGROWTH:        64
SQLTEMPDBLOGFILESIZE:          8
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED:                    0
UIMODE:                        AutoAdvance
UpdateEnabled:                 true
UpdateSource:                  MU
USEMICROSOFTUPDATE:            false
X86:                           false

Configuration file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\ConfigurationFile.ini

Detailed results:
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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

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 Batch Parser
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\sql_batchparser_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=sql_batchparser.msi%40PublishProduct%401935%3a0x800736B3

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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

Feature:                       Reporting Services - Native
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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

Feature:                       Full-Text and Semantic Extractions for Search
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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

Feature:                       R Services (In-Database)
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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

Feature:                       SQL Server Replication
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 2008 Setup Support Files
Component error code:          1935
Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SystemConfigurationCheck_Report.htm

↧

Why won't SQL Server install?

October 13, 2016, 2:19 pm

≫ Next: TDE ( Encryption ) in SQL Server 2016

≪ Previous: Trying to install SQL Server 2016 Express on Windows 10

I'm a developer who has bought a reconditioned Samsung NC110 x64 netbook to mess around on during otherwise dull train journeys. I upgraded it from Win7 Starter edition to Win10 Home. I have installed VS2016 Community edition without any problems (other than speed!). Why can't SQL Server 2016 Express edition install?Win 10 Home is one of the supported OSes.

Thanks in advance.

↧

TDE ( Encryption ) in SQL Server 2016

October 14, 2016, 3:53 am

≫ Next: SQL 2016

≪ Previous: Why won't SQL Server install?

Hi ,

i am using sql server 2016 enterprise edition ( evaluation ) , in which i am supposed to use TDE on DB level,

Can you please help me to understand the steps to perform the same on 10 Different User DB's in that instance.

It would be great if you can share me the informative URLs to understand the concepts

Thank you

hemadri

↧

SQL 2016

October 14, 2016, 9:05 am

≫ Next: Please help me with the installation of SQL Server 2016

≪ Previous: TDE ( Encryption ) in SQL Server 2016

I am trying to download SQL 2016 from virtual studio and I am unable to do so. I first download the information on a disk but I am not sure where go go from there. Can anyone provide some guidance?

↧

Please help me with the installation of SQL Server 2016

October 14, 2016, 8:13 am

≫ Next: How to remove Windows server core from PC with command line

≪ Previous: SQL 2016

I had a problem while installing sql server 2016 and the error message is " Setup Account Privileges", searched it for solutions and still the same, in my laptop there isn't Local Security Policy in administrator tools but i already run as administrator, please help me fix this problem. my windows is 8.1 Single Language in 64-bit, Thank You

↧

How to remove Windows server core from PC with command line

October 14, 2016, 9:13 am

≫ Next: SQL VSS Writer not in list

≪ Previous: Please help me with the installation of SQL Server 2016

Hello ,

I installed the 2016 Windows Server Technical Preview 4 (which is Server Core without GUI), I have access only to command line.

How do I remove the core server installation from my PC with command line?

↧

SQL VSS Writer not in list

October 14, 2016, 12:50 pm

≫ Next: Windows Internal Database Service Pack 4 (2463332) & Windows SBS 2003 R2

≪ Previous: How to remove Windows server core from PC with command line

Hello,

running vssadmin list writers does not show the SQL Server Writer.

SYSTEM is sysadmin (even put in local admin group to test). under services, the service is running.

SQL Server VSS Writer Service is added to the sysadmin role

ran select ‘#’ + name +’#’ from sys.databases - no spaces appear

tried to use the administrator account - no luck.

uninstalled sql vss rebooted and then reinstalled sqlwriter.msi - no luck

running server 2012 R2 in a vmware vm. SQL 2012 SP3 Std 64bit. We do have SSL enabled for SQL.

any thoughts?

Thanks in advance.

↧

Windows Internal Database Service Pack 4 (2463332) & Windows SBS 2003 R2

April 4, 2011, 5:42 pm

≫ Next: Newbie: I have installed SQL Server 2016 and Management Studio but there is no SQL Server name to choose from

≪ Previous: SQL VSS Writer not in list

RE: Windows SBS 2003 R2 with Windows Internal Database Service Pack 4.

I tried to install Windows Internal Database Service Pack 4 (2463332) as it had been offered by Windows for several months. Seemed to install too quick, but said successfully installed. However, Windows then immediately offers to reinstall it again, i.e., reappears in system tray. Windows update history shows no indication that said service pack was installed.

In doing some research, I thought perhaps that I need to:

1. Download/run standalone version. Although standalone version appears to be almost 10 times the size of the update offered by Windows; or

2. Stop SQL Server before running Windows update.

Any help guidance would be appreciated as my knowledge is somewhat limited and next course of action is to contact our firm’s network consultant.

Thanks

Kristopher

kristopherk09

↧

Newbie: I have installed SQL Server 2016 and Management Studio but there is no SQL Server name to choose from

October 16, 2016, 2:10 am

≫ Next: SQL Server 2016 Developer edition throws "evaluation period has expired" error

≪ Previous: Windows Internal Database Service Pack 4 (2463332) & Windows SBS 2003 R2

Hi,

I have installed SQL Server 2016 and Management Studio with success but when I try to connect to a Server on SSMS, the combo is empty.
Do I need to start a service manually? I could only found the SQL Writer service running.

Thanks/Brgds
joao

↧

SQL Server 2016 Developer edition throws "evaluation period has expired" error

October 15, 2016, 3:13 pm

≫ Next: Failed to install WIndows update KB3045313

≪ Previous: Newbie: I have installed SQL Server 2016 and Management Studio but there is no SQL Server name to choose from

Hello,

I have installed an SQL Server 2016 RC 2Developer Edition, but now I get the following error when trying to start the service:

2016-10-14 01:34:31.84 Server SQL Server evaluation period has expired.

Now I have checked in the installer that I definately chose the Developer edition, so basically this should not happen. Is this a known issue and is there a way of fixing that? I tried running an "Upgrade edition" to Developer again, but this didn't work.

I also have a 2008 Express installation running which I need for a specific program, but that shouldn't really matter.

For those who wish to see the whole error log, here it is:

2016-10-14 01:34:31.84 Server Microsoft SQL Server 2016 (RC2) - 13.0.1300.275 (X64)
Mar 26 2016 03:43:12
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows 10 Pro 6.3 <X64> (Build 14393: )

2016-10-14 01:34:31.84 Server UTC adjustment: 2:00
2016-10-14 01:34:31.84 Server (c) Microsoft Corporation.
2016-10-14 01:34:31.84 Server All rights reserved.
2016-10-14 01:34:31.84 Server Server process ID is 8784.
2016-10-14 01:34:31.84 Server System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2016-10-14 01:34:31.84 Server Authentication mode is WINDOWS-ONLY.
2016-10-14 01:34:31.84 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\Log\ERRORLOG'.
2016-10-14 01:34:31.84 Server The service account is 'NT Service\MSSQL$DEV_TABULAR'. This is an informational message; no user action is required.
2016-10-14 01:34:31.84 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\DATA\mastlog.ldf
2016-10-14 01:34:31.84 Server Command Line Startup Parameters:
-s "DEV_TABULAR"
2016-10-14 01:34:31.84 Server Error: 17051, Severity: 16, State: 1.
2016-10-14 01:34:31.84 Server SQL Server evaluation period has expired.
2016-10-14 01:34:31.84 Server SQL Server shutdown has been initiated

↧

Failed to install WIndows update KB3045313

September 1, 2016, 2:47 am

≫ Next: Some updates of SQL Server 2008 and SQL Server 2014 were not recommended in Microsoft Update

≪ Previous: SQL Server 2016 Developer edition throws "evaluation period has expired" error

Environment

Our machine is running Windows Server 2012 R2 Standard and SQL Server 2008 R2 (SP2) - 10.50.4000.0 (Intel X86).

Problem encountered

When installing the update for KB3045313 in Windows Update, the following error was prompted (error screen attached):

Error(s) found:

Code 80246013 Windows Update ran into a problem.

Then I tried to download the update from Microsoft and install the update manually, the following error was prompted (error screen attached):

The following feature couldn't be installed:

.NET Framework 3.5 (includes .NET 2.0 and 3.0)

As .NET framework is not compulsory for SQL Server 2008 R2, how can we install the update for KB3045313 when SQL Server development using NET Framework 3.5 is not required for us.

↧

Some updates of SQL Server 2008 and SQL Server 2014 were not recommended in Microsoft Update

October 17, 2016, 3:48 am

≫ Next: Adding new node to existing SQL Server AlwaysOn

≪ Previous: Failed to install WIndows update KB3045313

Problem summary

----------------------

We are running SQL Server 2008 R2 (SP2) and SQL Server 2014 in a Windows Server 2012 R2 server. .NET framework 4.5 was enabled and .NET framework 3.5 was not enabled. Some updates on SQL Server was not shown after checking for updates in Windows Update.

Versions of SQL Server installed

--------------------------------------

In Program and Features, the following installed versions were shown:

- Service Pack 2 for SQL Server 2008 R2 (KB2630458) (Version 10.52.4000.0)

- Microsoft SQL Server 2014 Setup (English)

Updates not shown after checking for updates in Windows Update

------------------------------------------------------------------------------

- GDR 4042 for SQL Server 2008 R2 (KB3045313) (Version 10.52.4042.0)

- Microsoft SQL Server 2014 Service Pack 2 (KB3171021)

Anyone can share experience. Thank you.

↧

Adding new node to existing SQL Server AlwaysOn

October 17, 2016, 1:19 pm

≫ Next: Sql server encountered an error on installing or unistalling it.

≪ Previous: Some updates of SQL Server 2008 and SQL Server 2014 were not recommended in Microsoft Update

Hi,

Our AlwaysOn SQL Server 2012 already running with 2 Nodes on Windows Server 2012 R2 from past 1 year.

Now we are planning to add NEW 3rd node. Does it requires any downtime for adding 3 Node to existing cluster? ]

Please suggest.

ENVIRONMENT: (VM Virtual Machines)

Node1 PrimaryManual --> Main Data Center

Node2 SecondaryManual --> DR Location

Node 3 Primary Automatic --> Main Data Center

↧

Sql server encountered an error on installing or unistalling it.

October 17, 2016, 2:27 pm

≫ Next: SQL Server 2016 Installation ERROR

≪ Previous: Adding new node to existing SQL Server AlwaysOn

When i am installing the sql server 2008 r2 it was showing an error : "The given was not present in the dictionary." Same problem is coming when i am uninstalling it. I am facing so much problem due to this. Please help me.

↧