Sql ошибка 2068578304

Hello everyone!

I am having a problem where some machines (both virtual and real), running Win7 (both 32 and 64 bit) fail to install SQL Server 2008 R2 SP1.

The exit code is -2068578304 and in the log file for the SQL installation I find the following: 

———————————————-

———————————————-

and then also

—————————————-

—————————————-

However, if the sa password is not strong enough, why does the installation succeed on many machines but not on a few?

I am not getting consistent behaviour across machines, but the behaviour seems so far to be consistent on specific machines.

Any ideas (except for changing the pwd)?

Hello everyone!

I am having a problem where some machines (both virtual and real), running Win7 (both 32 and 64 bit) fail to install SQL Server 2008 R2 SP1.

The exit code is -2068578304 and in the log file for the SQL installation I find the following: 

———————————————-

———————————————-

and then also

—————————————-

—————————————-

However, if the sa password is not strong enough, why does the installation succeed on many machines but not on a few?

I am not getting consistent behaviour across machines, but the behaviour seems so far to be consistent on specific machines.

Any ideas (except for changing the pwd)?

Description

During the installation, this error will appear: We are sorry but installation failed. MS SQL Server returns following error: -2068578304.

If you try to install MS SQL Server manually and you are following these instructions, you will experience an error during the step 8 from these instructions. The error is related to the password that is evaluated as not strong enough.

It was experienced on the Basic version of eWay-CRM, but it is possible to happen on Premium version, too.

Version

All versions of eWay-CRM

Difficulty

Medium

Resolution

The error is related to the eWay-CRM123 password that is standard for eWay-CRM SQL database. The password doesn’t meet some of the security settings.

Option 1: The change of the Local Security Policy

Insert secol.msc to the search field in the Start menu of Microsoft Windows. You will get to the Local Security Policy. Go to the path Security Settings > Account Policies > Password policy, where you can change password settings of your operating system. Restricting items are:

• Minimum password length — it sets the number of signs in the password
• Password must meet complexity requirements — the password should meet a specific requirements that are even needed by MS SQL Server itself (the password must contain at least one lower-case letter, one upper-case letter, one number and one other sign — more can be find on official website).

Temporarily, set the Minimum password length to 10 and Password must meet complexity requirements to Disabled.

When you change settings, the installation should proceed without this error. The procedure will be completed correctly even if you are installing eWay-CRM from installation file without necessity of the manual installation of MS SQL Server as is described in this article.

Option 2: Change of the standard eWay-CRM database password (in the case the option 1 cannot be done)

It is possible that you won’t be able to change the local security setting because of missing user permissions. The option 2 is a solution for the current installation.

In the case the user hasn’t permissions to change security policy, there is need to set a password in the step 8 of this manual, the password that will meet all security requirements. Instead of standard eWay-CRM123, the password should be longer (other requirements for a strong password should be met by eWay-CRM123).

I am working on an installer project where we are replacing an old WISE based installer with innosetup.

One of the install scripts that is being ported to the new installer kicks of SQLEXPR.exe which is SQL Server Express.

During testing some computers get %ERRORLEVEL% = -2068578304

A bit of googling and I have been unable to work out the exact meaning. This is not in the range of error codes produced by MSI based installers. Does anyone have any idea what the cause of error here is and how to correctly parse it? I am seeing other large negative error codes that can be split into multiple pieces. e.g. exit code and facility code? any ideas?

After finding the log file, I’ve found a bit more info. And when converting that number to hex I can now see the problem. The batch file that is used to kick off the SQL Server Express installation is treating the result as a 32bit number but it’s really a 16bit one. So if I mask -2068578304 to 0xffffffff
I will get the result 0x84b40000. The script looks currently looks at the bottom 4 bits to determine error or success (this is zero) so the question now becomes what does the Facility Code mean? as it appears it largely installed but the default instance is missing.

I guess I’m really wanting to know what values Facility Code can be returned. Our installation script is just looking at ErrorCode but that is not enough in other words. Is there a list of descriptions somewhere for FacilityCode?

Update:
It turns out that this is a problem with SQL2012 and earlier that the actual ErrorCode is not propagated to the SQLEXPR return code. It should really return the inner result 0x851a0013. SQL2014 and newer does the right thing.

Exception summary:
The following is an exception stack listing the exceptions in outermost to inner
most order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidatio
nException
    Message:
        The specified sa password does not meet strong password requirements. Fo
r more information about strong password requirements, see "Database Engine Conf
iguration - Account Provisioning" in Setup Help or in SQL Server 2012 Books Onli
ne.
    HResult : 0x84b40000
        FacilityCode : 1204 (4b4)
        ErrorCode : 0 (0000)
    Data:
      SQL.Setup.FailureCategory = InputSettingValidationFailure
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAll
ValidationErrorsAndThrowFirstOne(ValidationState vs)
        at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSetti
ngsAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String acti
onId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteAc
tionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContain
er context)
    Inner exception type: Microsoft.SqlServer.Configuration.SqlEngine.Validation
Exception
        Message:
                The specified sa password does not meet strong password requirem
ents. For more information about strong password requirements, see "Database Eng
ine Configuration - Account Provisioning" in Setup Help or in SQL Server 2012 Bo
oks Online.
        HResult : 0x851a0013
                FacilityCode : 1306 (51a)
                ErrorCode : 19 (0013)

Details of the scenario you tried and the problem that is occurring:
Following the example of default named sql2017 installation.
The DSC configuration that is using the resource (as detailed as possible):
#region Install SQL Server
SqlSetup ‘InstallDefaultInstance’
{
InstanceName = ‘MSSQLSERVER’
Features = ‘SQLENGINE,AS’
SQLCollation = ‘Latin1_General_CI_AS_KS_WS’
SQLSvcAccount = $SqlService
AgtSvcAccount = $SqlAgentService
ASSvcAccount = $SqlService
SQLSysAdminAccounts = ‘COMPANYSQL Administrators’, $SqlAdmin.UserName
ASSysAdminAccounts = ‘COMPANYSQL Administrators’, $SqlAdmin.UserName
InstallSharedDir = ‘C:Program FilesMicrosoft SQL Server’
InstallSharedWOWDir = ‘C:Program Files (x86)Microsoft SQL Server’
InstanceDir = ‘C:Program FilesMicrosoft SQL Server’
InstallSQLDataDir = ‘C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData’
SQLUserDBDir = ‘C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData’
SQLUserDBLogDir = ‘C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData’
SQLTempDBDir = ‘C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData’
SQLTempDBLogDir = ‘C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData’
SQLBackupDir = ‘C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLBackup’
ASServerMode = ‘TABULAR’
ASConfigDir = ‘C:MSOLAPConfig’
ASDataDir = ‘C:MSOLAPData’
ASLogDir = ‘C:MSOLAPLog’
ASBackupDir = ‘C:MSOLAPBackup’
ASTempDir = ‘C:MSOLAPTemp’
SourcePath = ‘C:SQL2017’
UpdateEnabled = ‘False’
ForceReboot = $false

        PsDscRunAsCredential = $SqlSetup

        DependsOn            =  '[WindowsFeature]NetFramework35', '[WindowsFeature]NetFramework45', '[File]InstallDirshortTemp'
    }

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Server 2012R2
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
sqlserverdsc 11.0.0.0
Version of the DSC module you’re using, or ‘dev’ if you’re using current dev branch:
PSDesiredStateConfiguration version 1.1

Powershell version:
Version : 5.0.10586.117

Log:

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068578304
Exit facility code: 1204
Exit error code: 0
Exit message: COMPANYSQL Administrators — User or group does not exists.
Start time: 2018-03-02 09:14:06
End time: 2018-03-02 09:14:22
Requested action: Install

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for AS: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Machine Properties:
Machine name: SQL1
Machine processor count: 1
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 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: C:SQL2017x64setup
Installation edition: Standard

Product Update Status:
User selected not to include product updates.

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: contosoSQLAgentService
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:MSOLAPBackup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:MSOLAPConfig
ASDATADIR: C:MSOLAPData
ASLOGDIR: C:MSOLAPLog
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: contosoSQLService
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: COMPANYSQL Administrators, contosoSQLAdmin, contosoSQLSetup
ASTELSVCACCT: NT ServiceSSASTELEMETRY
ASTELSVCPASSWORD:
ASTELSVCSTARTUPTYPE: Automatic
ASTEMPDIR: C:MSOLAPTemp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME:
CLTRESULTDIR:
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT:
CLTSVCPASSWORD:
CLTWORKINGDIR:
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT:
CTLRSVCPASSWORD:
CTLRUSERS:
ENABLERANU: false
ENU: true
EXTSVCACCOUNT:
EXTSVCPASSWORD:
FEATURES: SQLENGINE, AS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME:
FTSVCACCOUNT:
FTSVCPASSWORD:
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISMASTERSVCACCOUNT: NT AUTHORITYNetwork Service
ISMASTERSVCPASSWORD:
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN:
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT:
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD:
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT:
ISTELSVCPASSWORD:
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITYNetwork Service
ISWORKERSVCCERT:
ISWORKERSVCMASTER:
ISWORKERSVCPASSWORD:
ISWORKERSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME:
MATRIXNAME:
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT:
PBDMSSVCPASSWORD:
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT:
PBENGSVCPASSWORD:
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE:
PBSCALEOUT: false
PID: *****
QUIET: true
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT:
RSSVCPASSWORD:
RSSVCSTARTUPTYPE: Automatic
SAPWD:
SECURITYMODE:
SQLBACKUPDIR: C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLBackup
SQLCOLLATION: Latin1_General_CI_AS_KS_WS
SQLSVCACCOUNT: contosoSQLService
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: COMPANYSQL Administrators, contosoSQLAdmin, contosoSQLSetup
SQLTELSVCACCT: NT ServiceSQLTELEMETRY
SQLTELSVCPASSWORD:
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData
SQLUSERDBLOGDIR: C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLData
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: false
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false

Configuration file: C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20180302_091405ConfigurationFile.ini

Detailed results:
Feature: Database Engine Services
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Feature: Analysis Services
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Feature: Setup Support Files
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Feature: SQL Client Connectivity
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Feature: SQL Client Connectivity SDK
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Feature: SQL Writer
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Feature: SQL Browser
Status: Failed
Reason for failure: Setup was canceled for the feature.
Next Step: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:Program FilesMicrosoft SQL Server140Setup BootstrapLog20180302_091405SystemConfigurationCheck_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: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
Message:
COMPANYSQL Administrators — User or group does not exists.
HResult : 0x84b40000
FacilityCode : 1204 (4b4)
ErrorCode : 0 (0000)
Data:
SQL.Setup.FailureCategory = InputSettingValidationFailure
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.b__b()
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
Inner exception type: System.ApplicationException
Message:
COMPANYSQL Administrators — User or group does not exists.
HResult : 0x80131600

Windows VistaMicrosoft SQL Server 2005MySQL Server