none
Issue installing SQL SERVER EXPR 2012/2016 on Server 2012 R2

    Question

  • I have been running SQL SERVER Express 2008 on Server 2012 R2 for some time. I recently began researching the migration process to move to SQL SERVER EPXRESS 2016. Because the original DB was migrated from Express 2005 the compatibility level was 90 and I need to stop at 110 in order to migrate to 130. 110 provided new object types and query advances such as IIF clause. They Data Migration Tool identified these necessary updates.

    Yet regardless of the approach to install, repair, add a new instance, I get this error:

    In the process upgrading the SQL, I am now getting the following error :

        TITLE: SQL Server Setup failure.
        ------------------------------

        SQL Server Setup has encountered the following error:

        Version string portion was too short or too long..

        For help, click: http://go.microsoft.com/fwlinkLinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0x6343E456%25400x294A9FD9

    the link is useless as MS reissued it.

    The error appears after selecting the "New SQL Server Stand-alone installation or add features to an existing installation" at the top of the SQL SERVER Installation Center window. Just as test I tried SQL 2016 Express as well. Same error.

    I found some posts about changing the registry, delete older version of the .Net referenced in the following key:

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\User Agent\Post Platform

    this did not work.

    I have tried numerous .Net Framework test tools to validate each version. No errors found, but then these tools appear to have not yet been updated for Server 2012 R2.

    Currently my server is sunk, no working DB.

    I have confirmed that the .Net Framework 3.5 and 4.5 Features are in fact installed, via Server Manager.

    Also I have tried the REPAIR option and virtually every other available feature in the SQL Server Installation Center.

    Any insightful help would be a pleasure to review.


    • Edited by march111 Monday, November 7, 2016 6:03 PM
    Monday, November 7, 2016 4:56 PM

Answers

  • Hello Teige Gao,

    Thank you for the reply. Those versions had previously been installed. They were removed through Control Panel and where that was unsuccessful via the method you described in your link from Aaron Burtrand. That process had already been attempted.

    Currently I have scrubbed the hard drive and started over with a clean install from the OS up.

    I have one more server that needs to be updated, we will see if the same issues arise.



    • Marked as answer by march111 Friday, November 10, 2017 4:42 PM
    • Edited by march111 Friday, November 10, 2017 4:42 PM
    Thursday, November 10, 2016 1:02 PM

All replies

  • Where does that error message appear? Can you please post the relevant portion of the log?
    Monday, November 7, 2016 10:03 PM
  • That is the dialog message that pops up. The summary.txt file from the install folder, top portion here....

    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2147024809
      Exit facility code:            7
      Exit error code:               87
      Exit message:                  Version string portion was too short or too long.
      Start time:                    2016-11-08 11:00:18
      End time:                      2016-11-08 11:00:35
      Requested action:              Install
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1601.5&EvtType=0x6343E456%400x294A9FD9&EvtType=0x6343E456%400x294A9FD9
    Machine Properties:
      Machine name:                  ASPDEMOSVR2
      Machine processor count:       4
      OS version:                    Microsoft Windows Server 2012 R2 Standard (6.3.9600)
      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:\SQLServer2016Media\ExpressAdv\x64\setup\
      Installation edition:          Express
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      false
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                <empty>
      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:         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:                    false
      ENU:                           true
      EXTSVCACCOUNT:                 <empty>
      EXTSVCPASSWORD:                <empty>
      FEATURES:                      SQLENGINE, REPLICATION, ADVANCEDANALYTICS, SQL_SHARED_MR, FULLTEXT, DQ, AS, RS, RS_SHP, DQC, CONN, IS, BC, SDK, BOL, SSMS, DREPLAY_CTLR, DREPLAY_CLT, ADV_SSMS, SNAC_SDK, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTROPENLICENSETERMS:      false
      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:                    <empty>
      INSTANCENAME:                  <empty>
      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:                  <empty>
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 <empty>
      SQLSVCINSTANTFILEINIT:         false
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTELSVCACCT:                 <empty>
      SQLTELSVCPASSWORD:             <empty>
      SQLTELSVCSTARTUPTYPE:          0
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBFILECOUNT:            0
      SQLTEMPDBFILEGROWTH:           -1
      SQLTEMPDBFILESIZE:             -1
      SQLTEMPDBLOGDIR:               <empty>
      SQLTEMPDBLOGFILEGROWTH:        -1
      SQLTEMPDBLOGFILESIZE:          -1
      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\20161108_110017\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161108_110017\SystemConfigurationCheck_Report.htm
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: System.ArgumentException
        Message:
            Version string portion was too short or too long.
        HResult : 0x80070057
        Data:
          HelpLink.EvtType = 0x6343E456@0x294A9FD9
          DisableWatson = true
        Stack:
            at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
            at System.Version.TryParseVersion(String version, VersionResult& result)
            at System.Version.Parse(String input)
            at System.Version..ctor(String version)
            at Microsoft.SqlServer.Configuration.MsiExtension.MsiProductProvider.get_Version()
            at Microsoft.SqlServer.Configuration.MsiExtension.MSIDetectionEngine.FillInstallPropertyByProductCode(PackageInstallProperty pkg, IWindowsInstallerProduct product, PackageAttribute pkgAttrib)
            at Microsoft.SqlServer.Configuration.MsiExtension.MSIDetectionEngine.DeterminePackageInstalledState(PackageId pkg, PackageAttribute pkgAttrib)
            at Microsoft.SqlServer.Configuration.PackageChainerExtension.SetPackageInstallStateAction.DetectPackageInstalledState(PackageAttribute packageData)
            at Microsoft.SqlServer.Configuration.PackageChainerExtension.SetPackageInstallStateAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.GetFeatureInstallState(ServiceContainer context, String mediaPath)
            at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.CreateFeatureTreeFactory(String instanceName)
            at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinition(String instanceName)
            at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase..ctor(ServiceContainer context, FeatureEdition featureEdition)
            at Microsoft.SqlServer.Configuration.SetupExtension.ExpandInstallFeatures.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

    • Edited by march111 Tuesday, November 8, 2016 4:05 PM entire summary.txt
    Monday, November 7, 2016 10:05 PM
  • Monday, November 7, 2016 11:03 PM
  • Hi Martch111,

    see this following thread .

    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4cf08e9f-80c7-4a1d-aa3f-e4a2182b05af/sql-server-2008-express-install-fails-with-version-string-portion-was-too-short-or-too-long?forum=sqlsetupandupgrade


    Please click Mark As Answer if my post helped.

    Tuesday, November 8, 2016 1:21 AM
  • Vishe, that thread is from 2011, its 5 years old, this server does not have SQL 2005 installed.

    Tuesday, November 8, 2016 1:35 AM
  • That thread is from 2011 and does not pertain to this issue. SQL SERVER 2005 is not installed on this server.

    I had already posted in that thread before creating this one that the solution does not work for a failing 2016 installation.

    Tuesday, November 8, 2016 1:38 AM
  • Can you post the relevant portion of the setup log here?

    C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log

    Look for the most recent directory and post the error portion of the details.log file here, or host all of it somewhere where we can get to it.

    Tuesday, November 8, 2016 3:36 AM
  • I only found the word "failed" listed 3 times in the detail.txt file so here is the content with some surrounding enteries. If you need anything else please let me know. I can post more if needed.

    (10) 2016-11-07 12:57:26 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.NoRebootPackageFacet
    (10) 2016-11-07 12:57:26 Slp: Rule applied features  : ALL
    (10) 2016-11-07 12:57:26 Slp: ----------------------------------------------------------------------
    (10) 2016-11-07 12:57:26 Slp: Skipping rule NoRebootPackageDownLevel
    (10) 2016-11-07 12:57:26 Slp: Rule will not be evaluated due to the following failed restriction(s):
    (10) 2016-11-07 12:57:26 Slp: Condition "Is the OS version equal or higher than 6.1" did not pass as it returned true and false was expected.
    (10) 2016-11-07 12:57:26 Slp: Rule is not applicable in the current scenario.
    (10) 2016-11-07 12:57:26 Slp: Loading rule: ServerCorePlatformCheck
    (10) 2016-11-07 12:57:26 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetOsInfo
    (10) 2016-11-07 12:57:26 Slp: Rule applied features  : ALL
    (10) 2016-11-07 12:57:26 Slp: ----------------------------------------------------------------------
    (10) 2016-11-07 12:57:26 Slp: Skipping rule ServerCorePlatformCheck
    (10) 2016-11-07 12:57:26 Slp: Rule will not be evaluated due to the following failed restriction(s):
    (10) 2016-11-07 12:57:26 Slp: Condition "IsServerCore" did not pass as it returned false and true was expected.
    (10) 2016-11-07 12:57:26 Slp: Rule is not applicable in the current scenario.
    (10) 2016-11-07 12:57:26 Slp: Loading rule: ServerCore64BitCheck
    (10) 2016-11-07 12:57:26 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetWOW64PlatformCheck
    (10) 2016-11-07 12:57:26 Slp: Rule applied features  : ALL
    (10) 2016-11-07 12:57:26 Slp: ----------------------------------------------------------------------
    (10) 2016-11-07 12:57:26 Slp: Skipping rule ServerCore64BitCheck
    (10) 2016-11-07 12:57:26 Slp: Rule will not be evaluated due to the following failed restriction(s):
    (10) 2016-11-07 12:57:26 Slp: Condition "IsServerCore" did not pass as it returned false and true was expected.
    (10) 2016-11-07 12:57:26 Slp: Rule is not applicable in the current scenario.
    (10) 2016-11-07 12:57:26 Slp: Loading rule: FacetWOW64PlatformCheck
    (10) 2016-11-07 12:57:26 Slp: Creating rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetWOW64PlatformCheck
    (10) 2016-11-07 12:57:26 Slp: Rule applied features  : ALL
    (10) 2016-11-07 12:57:26 Slp: Send result to channel : RulesEngineNotificationChannel
    (11) 2016-11-07 12:57:26 Slp: Executing rules engine...
    (11) 2016-11-07 12:57:26 Slp: Start rule execution, total number of rules loaded: 12
    (11) 2016-11-07 12:57:26 Slp: Initializing rule      : Setup administrator
    (11) 2016-11-07 12:57:26 Slp: Rule is will be executed  : True
    (11) 2016-11-07 12:57:26 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetAdminCheck
    (11) 2016-11-07 12:57:26 Slp: Rule 'ThreadHasAdminPrivilegeCheck' Result: Running thread has administrator privilege.
    (11) 2016-11-07 12:57:26 Slp: Evaluating rule        : ThreadHasAdminPrivilegeCheck
    (11) 2016-11-07 12:57:26 Slp: Rule running on machine: ASPDEMOSVR2
    (11) 2016-11-07 12:57:27 Slp: Rule evaluation done   : Succeeded
    (11) 2016-11-07 12:57:27 Slp: Rule evaluation message: The account running SQL Server Setup has administrator rights on the computer.
    (11) 2016-11-07 12:57:27 Slp: Send result to channel : RulesEngineNotificationChannel
    (11) 2016-11-07 12:57:27 Slp: Initializing rule      : Setup account privileges
    (11) 2016-11-07 12:57:27 Slp: Rule is will be executed  : True
    (11) 2016-11-07 12:57:27 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.FacetPrivilegeCheck
    (11) 2016-11-07 12:57:27 Slp: Rule 'HasSecurityBackupAndDebugPrivilegesCheck' Result: Running process has SeSecurity privilege, has SeBackup privilege and has SeDebug privilege.
    (11) 2016-11-07 12:57:27 Slp: Evaluating rule        : HasSecurityBackupAndDebugPrivilegesCheck
    (11) 2016-11-07 12:57:27 Slp: Rule running on machine: ASPDEMOSVR2
    (11) 2016-11-07 12:57:27 Slp: Rule evaluation done   : Succeeded
    (11) 2016-11-07 12:57:27 Slp: Rule evaluation message: The account that is running SQL Server Setup has the right to back up files and directories, the right to manage auditing and security log and the right to debug programs.
    (11) 2016-11-07 12:57:27 Slp: Send result to channel : RulesEngineNotificationChannel
    (11) 2016-11-07 12:57:27 Slp: Initializing rule      : Restart computer
    (11) 2016-11-07 12:57:27 Slp: Rule is will be executed  : True

    Tuesday, November 8, 2016 2:06 PM
  • I also found this section which contains the error I was getting....

    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1033: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1036: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1040: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1041: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1042: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1046: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1049: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_2052: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_3082: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Package ID sql_ssms_loc_2008_Cpu64_1053: NotInstalled
    (01) 2016-11-07 12:57:30 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.ExpandInstallFeatures" threw an exception during execution.
    (01) 2016-11-07 12:57:30 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Version string portion was too short or too long. ---> System.ArgumentException: Version string portion was too short or too long.
    (01) 2016-11-07 12:57:30 Slp:    at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
    (01) 2016-11-07 12:57:30 Slp:    at System.Version.TryParseVersion(String version, VersionResult& result)
    (01) 2016-11-07 12:57:30 Slp:    at System.Version.Parse(String input)
    (01) 2016-11-07 12:57:30 Slp:    at System.Version..ctor(String version)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.MsiProductProvider.get_Version()
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.MSIDetectionEngine.FillInstallPropertyByProductCode(PackageInstallProperty pkg, IWindowsInstallerProduct product, PackageAttribute pkgAttrib)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.MSIDetectionEngine.DeterminePackageInstalledState(PackageId pkg, PackageAttribute pkgAttrib)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.PackageChainerExtension.SetPackageInstallStateAction.DetectPackageInstalledState(PackageAttribute packageData)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.PackageChainerExtension.SetPackageInstallStateAction.ExecuteAction(String actionId)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.GetFeatureInstallState(ServiceContainer context, String mediaPath)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.CreateFeatureTreeFactory(String instanceName)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinition(String instanceName)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase..ctor(ServiceContainer context, FeatureEdition featureEdition)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.ExpandInstallFeatures.ExecuteAction(String actionId)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2016-11-07 12:57:30 Slp:    --- End of inner exception stack trace ---
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    (01) 2016-11-07 12:57:30 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    (01) 2016-11-07 12:57:31 Slp: Received request to add the following file to Watson reporting: C:\Users\Administrator\AppData\Local\Temp\2\tmp5C58.tmp
    (01) 2016-11-07 12:57:31 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2016-11-07 12:57:31 Slp: Inner exceptions are being indented
    (01) 2016-11-07 12:57:31 Slp:
    (01) 2016-11-07 12:57:31 Slp: Exception type: System.ArgumentException
    (01) 2016-11-07 12:57:31 Slp:     Message:
    (01) 2016-11-07 12:57:31 Slp:         Version string portion was too short or too long.
    (01) 2016-11-07 12:57:31 Slp:     HResult : 0x80070057
    (01) 2016-11-07 12:57:31 Slp:     Stack:
    (01) 2016-11-07 12:57:31 Slp:         at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
    (01) 2016-11-07 12:57:31 Slp:         at System.Version.TryParseVersion(String version, VersionResult& result)
    (01) 2016-11-07 12:57:31 Slp:         at System.Version.Parse(String input)
    (01) 2016-11-07 12:57:31 Slp:         at System.Version..ctor(String version)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.MsiProductProvider.get_Version()
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.MSIDetectionEngine.FillInstallPropertyByProductCode(PackageInstallProperty pkg, IWindowsInstallerProduct product, PackageAttribute pkgAttrib)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.MSIDetectionEngine.DeterminePackageInstalledState(PackageId pkg, PackageAttribute pkgAttrib)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.PackageChainerExtension.SetPackageInstallStateAction.DetectPackageInstalledState(PackageAttribute packageData)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.PackageChainerExtension.SetPackageInstallStateAction.ExecuteAction(String actionId)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.MsiExtension.SetFeatureInstallStateAction.GetFeatureInstallState(ServiceContainer context, String mediaPath)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.CreateFeatureTreeFactory(String instanceName)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinition(String instanceName)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase..ctor(ServiceContainer context, FeatureEdition featureEdition)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.ExpandInstallFeatures.ExecuteAction(String actionId)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2016-11-07 12:57:31 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2016-11-07 13:01:01 Slp: Watson Bucket 2
     Original Parameter Values

    (01) 2016-11-07 13:01:01 Slp: Parameter 0 : SQL Server 2016@RTM@
    (01) 2016-11-07 13:01:01 Slp: Parameter 1 : System.Version.VersionResult.SetFailure
    (01) 2016-11-07 13:01:01 Slp: Parameter 2 : System.Version.VersionResult.SetFailure
    (01) 2016-11-07 13:01:01 Slp: Parameter 3 : System.ArgumentException@-2147024809
    (01) 2016-11-07 13:01:01 Slp: Parameter 4 : System.ArgumentException@-2147024809
    (01) 2016-11-07 13:01:01 Slp: Parameter 5 : ExpandInstallFeatures
    (01) 2016-11-07 13:01:01 Slp:
     Final Parameter Values
    (01) 2016-11-07 13:01:01 Slp: Parameter 0 : SQL Server 2016@RTM@
    (01) 2016-11-07 13:01:01 Slp: Parameter 1 : 0x6343E456
    (01) 2016-11-07 13:01:01 Slp: Parameter 2 : 0x6343E456
    (01) 2016-11-07 13:01:01 Slp: Parameter 3 : 0x294A9FD9
    (01) 2016-11-07 13:01:01 Slp: Parameter 4 : 0x294A9FD9
    (01) 2016-11-07 13:01:01 Slp: Parameter 5 : ExpandInstallFeatures

    • Edited by march111 Tuesday, November 8, 2016 2:14 PM
    Tuesday, November 8, 2016 2:13 PM
  • Tuesday, November 8, 2016 4:08 PM
  • System Configuration Check Report comes up clean.
    Tuesday, November 8, 2016 4:09 PM
  • Can yo do this on the SQL 2008 r2 express instance

    select @@Version

    Tuesday, November 8, 2016 4:48 PM
  • There is no installation of SQL running on this server at this time. It was previously Sql Express 2008 R2, then 2012, trying to install 2016, after removing 2008 R2 caused this mess.

    Now I am trying to get back to ground zero I guess and just install SQL 2016.



    • Edited by march111 Tuesday, November 8, 2016 4:52 PM
    Tuesday, November 8, 2016 4:50 PM
  • If you bingle the error message, you will see multiple topics popping up and they all describe situations where you have mutiplle versions of some product installed, may it be SQL Server or .NET framework or whatever. It's hard to tell which one you are facing.

    I think you should be tracing your installation process with something like process monitor from sysinternals. It should tell you which registry key fails to be updated / created.

    I know that the specific error message is for 2005, but you should read beyond what's in the page.

    Tuesday, November 8, 2016 4:52 PM
  • spaghettidba when I check those keys there are no older versions of SQL listed. I have been using procmon to try and locate missing registry entries but have not located any.

    Tuesday, November 8, 2016 9:29 PM
  • I have successfully installed Sql Server Management Studio 2016 but I can not get the Database Engine installed.
    • Edited by march111 Wednesday, November 9, 2016 1:12 PM
    Wednesday, November 9, 2016 1:12 PM
  • Hi march111,

    Could you please share the full detail.txt to us for analysis? You can share it with onedrive. As mentioned by you, you have only met three ‘Fail’ in the installation log, based on my test, when I install SQL Server on Windows Server 2012 R2, I will meet the same failure, it means the installation service is running role check and getting the best configuration for installation.

    Besides, according to your description ‘There is no installation of SQL running on this server at this time. It was previously Sql Express 2008 R2, then 2012, trying to install 2016, after removing 2008 R2 caused this mess.’ , this issue can be caused by that SQL Server 2008 R2 has not been uninstalled completely. We can use the following steps:

    1.    Uninstall the existing SQL Server 2008 R2 Express and all the components from the control panel.
    2.    Go to the register ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\’ and get the value related to SQL Server 2008.
    3.    Then use the command ‘rem DisplayName msiexec /x "{guid}"’ to uninstall them.

    For more information, please review this article.

    Best Regards,
    Teige

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, November 10, 2016 5:17 AM
  • Hello Teige Gao,

    Thank you for the reply. Those versions had previously been installed. They were removed through Control Panel and where that was unsuccessful via the method you described in your link from Aaron Burtrand. That process had already been attempted.

    Currently I have scrubbed the hard drive and started over with a clean install from the OS up.

    I have one more server that needs to be updated, we will see if the same issues arise.



    • Marked as answer by march111 Friday, November 10, 2017 4:42 PM
    • Edited by march111 Friday, November 10, 2017 4:42 PM
    Thursday, November 10, 2016 1:02 PM
  • Hi Dan,

    Apologise for not helping you solving this problem, have you tested it on another machine and what result did you get? We are looking forward to the result.

    Best Regards,
    Teige

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, November 15, 2016 7:31 AM
  • New install is working as expected. Second server migration is schedule for the next week.

    Tuesday, November 15, 2016 1:02 PM
  • Hi march111,

    It's very pleasant that your problem has been solved, sometimes an all new installation can be a workground if we have tried many methods. Could you please mark your reply and any other reply which can help you as "Answered"? I think more people will benefit from it.

    Best Regards,
    Teige

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, November 17, 2016 11:29 AM