Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all 7696 articles
Browse latest View live

How to install SQL Server 2008 R2 WITHOUT reboot

$
0
0

I have created a .ini file with all my configuration settings for SQL Server 2008 R2. I need the application to install and not reboot automatically at the end as I am deploying it as a task sequence using MDT. 

How can I suppress the reboot at the end?


MSSQL 2012 How to update to SP3

$
0
0

i use MSSQL 2012 no service pack (sharepoint database) ,

 i have proprem error rbs 211 ,

so i want to update to sp3 ( Error when you run RBS Maintainer in SQL Server 2012 or SQL Server 2014   https://support.microsoft.com/en-us/kb/2979304)

can i update to 2012-->sp3  or update 2012-->sp1->sp2->sp3

best regards



chatchai-netd

SQL Server Cluster installation failing with error message "sesecurityprivilege" missing.

$
0
0

I'm attempting to install a two-node SQL cluster over a Windows Cluster. The windows cluster is up and running and all set. When I run the SQL Server installation wizard, on the Data Directory screen, when using an SMB share, I type \\FS\BBDB, I get the error message reading that the setup account needs to SESECURITY privilege in the target file server.

Now, simple enough, right? Problem is, the setup account DOES have sesecurity privilege already. Not only that, but, the setup account is also:

-A domain admin

-An enterprise admin

-A local admin in both the source and the target machines

-Has full rights to both the share, as well as the NTFS folder

-It also has all the following rights per accesschk sys internals utility:

SeSecurityPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeSystemtimePrivilege
SeShutdownPrivilege
SeRemoteShutdownPrivilege
SeTakeOwnershipPrivilege
SeDebugPrivilege
SeSystemEnvironmentPrivilege
SeSystemProfilePrivilege
SeProfileSingleProcessPrivilege
SeIncreaseBasePriorityPrivilege
SeLoadDriverPrivilege
SeCreatePagefilePrivilege
SeIncreaseQuotaPrivilege
SeUndockPrivilege
SeManageVolumePrivilege
SeImpersonatePrivilege
SeCreateGlobalPrivilege
SeTimeZonePrivilege
SeCreateSymbolicLinkPrivilege
SeChangeNotifyPrivilege
SeInteractiveLogonRight
SeNetworkLogonRight
SeBatchLogonRight
SeRemoteInteractiveLogonRight
SeIncreaseWorkingSetPrivilege

-UAC is deactivated in the target file server. Not only I brought the lever down all the way, but also I edited the registry to actually disable it.

So, what gives??? Help much appreciated. I'm stumped here.

The whole environment is running on Windows Server 2012 R2 Datacenter servers, all fully patched. Attempting to install SQL Server 2012 Enterprise, and yes, I do accept the updates to install setup files when asked.


rferreira


Upgrading a Clustered environment

$
0
0

I am fairly new to the failover clustering of servers and have somewhat been thrown in the mix. What I do know, we have a cluster consisting of two MS Windows Server 2008 R2 Enterprise (x64) physical servers running SQL Server 2008 SP1. We have, on each box, 3 different SQL instances running with a total of 50 databases that have been created. Not to get into to many details, I have a backup created from a SQL Server 2008 R2 SP1 that i cannot restore because the difference in versions which has led me to have to upgrade my version of SQL to match that of the backup.

What is my best course of action to upgrade this clustered environment with minimal faults?

Any and all help is appreciated and if I have left out anything pertinent please let me know. Thank you in advance for any advice. I do not wish to attempt to rush this process however management is always in a hurry.   

The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation

$
0
0

Hi,

 

I asked this qustion in the Windows Powershell section, but mabye someone here can point me in the right direction.

 

Here is the original thread:https://social.technet.microsoft.com/Forums/en-US/ee5ea1c6-1374-428f-8dec-fc6d4a4fd31c

 

I am trying to install SQL Server 2014 on a domain member server (server A) from a remote server within the same domain (server B). This is a simple lab setup consisting of just 1 DC and 2 member servers, so all domain settings are at their default setting. Setup files have been copied over to server A previously. I have attempted to use domain users and local users without success.

 

When the install is triggered through PowerShell from Server B, the install starts fine but after a few seconds I can see the following error in the log files:The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. The SQL summary log file is attached.

 

To work around the issue I have enabled “trust this computer for delegation to any service” in Active Directory on the computer and user object. However, this is not a practical solution. Is there a better way to solve this issue?

$credentials=Get-Credential(credentials are written in UPN format: administrator@lab.local)

$session=New-PSSession-ComputerName"serverA"-Credential$credentials

Invoke-Command-Session$session-ArgumentList"$sqlUser","$pw","$domain"-ScriptBlock {

                          param (

                                  [Parameter(Mandatory=$true, Position= 1)]

                                  [string]$sqlUser,

                                  [Parameter(Mandatory=$true, Position= 2)]

                                  [string]$pw,

                                  [Parameter(Mandatory=$true, Position= 3)]

                                  [string]$domain

                           )

$sqlInstance="MSSQLSERVER”

C:\SQL\Setup.exe /Q /UpdateEnabled="False" /ACTION="Install" /FEATURES="SQLEngine, RS, IS, Tools" /SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS" /SQLSYSADMINACCOUNTS="$domain\Administrator" /IACCEPTSQLSERVERLICENSETERMS="True" /INSTALLSQLDATADIR="D:\$sqlInstance" /SQLBACKUPDIR="D:\$sqlInstance\Backup" /SQLUSERDBDIR="D:\$sqlInstance\Data" /SQLUSERDBLOGDIR="E:\$sqlInstance\Log" /SQLTEMPDBDIR="F:\$sqlInstance\Tempdb" /SQLTEMPDBLOGDIR="E:\$sqlInstance\Log" /SAPWD="123456" /SECURITYMODE="SQL" /INSTANCENAME="$sqlInstance" /INSTANCEID="$sqlInstance" /SQLSVCACCOUNT="$domain\$sqlUser" /SQLSVCPASSWORD="$pw" /SQLSVCSTARTUPTYPE="Automatic" /AGTSVCACCOUNT="$domain\$sqlUser" /AGTSVCPASSWORD="$pw" /AGTSVCSTARTUPTYPE="Automatic" /RSSVCACCOUNT="$domain\$sqlUser" /RSSVCPASSWORD="$pw" /RSINSTALLMODE="FilesOnlyMode"

}

Here is the SQL Summary Log:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068774911
  Exit facility code:            1201
  Exit error code:               1
  Exit message:                  There was an error generating the XML document.
  Start time:                    2015-12-01 15:14:42
  End time:                      2015-12-01 15:15:28
  Requested action:              Install
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xE0C083E6%400xB2215DAC&EvtType=0xE0C083E6%400xB2215DAC

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 RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SSMS:            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 BOL:             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:                  ServerA
  Machine processor count:       1
  OS version:                    Windows Server 2012
  OS service pack:
  OS region:                     Norge
  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 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\SQL\x64\setup\
  Installation edition:          Standard

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

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 LAB\__labsql28
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Automatic
  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>
  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
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, RS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             D:\MSSQLSERVER
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:
  RSINSTALLMODE:                 FilesOnlyMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  LAB\__labsql28
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  D:\MSSQLSERVER\Backup
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 LAB\__labsql28
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           LAB\500000-T15-DBA
  SQLTEMPDBDIR:                  F:\MSSQLSERVER\Tempdb
  SQLTEMPDBLOGDIR:               E:\MSSQLSERVER\Log
  SQLUSERDBDIR:                  D:\MSSQLSERVER\Data
  SQLUSERDBLOGDIR:               E:\MSSQLSERVER\Log
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 false
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151201_151440\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  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:                       Reporting Services - Native
  Status:                        Failed: see logs for details
  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:                       Integration Services
  Status:                        Failed: see logs for details
  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:                       Client Tools Connectivity
  Status:                        Failed: see logs for details
  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:                       Management Tools - Complete
  Status:                        Failed: see logs for details
  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:                       Client Tools SDK
  Status:                        Failed: see logs for details
  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:                       Client Tools Backwards Compatibility
  Status:                        Failed: see logs for details
  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:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  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: see logs for details
  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: see logs for details
  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: see logs for details
  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: see logs for details
  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:                       Documentation Components
  Status:                        Failed: see logs for details
  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: see logs for details
  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 Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151201_151440\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: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
    Message:
        There was an error generating the XML document.
    HResult : 0x84b10001
        FacilityCode : 1201 (4b1)
        ErrorCode : 1 (0001)
    Data:
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
        at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(Object objectToSerialize)
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CalculateSettings(IEnumerable`1 settingIds)
        at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.CalculateAllSettings(Boolean chainerSettingOnly)
        at Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction.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)
    Inner exception type: System.InvalidOperationException
        Message:
                There was an error generating the XML document.
        HResult : 0x80131509
        Stack:
                at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
                at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o)
                at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
        Inner exception type: System.Security.Cryptography.CryptographicException
            Message:
                        The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

            HResult : 0x80090345
            Stack:
                        at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
                        at Microsoft.SqlServer.Common.SqlSecureString.WriteXml(XmlWriter writer)
                        at System.Xml.Serialization.XmlSerializationWriter.WriteSerializable(IXmlSerializable serializable, String name, String ns, Boolean isNullable, Boolean wrapped)
                        at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write6_AgentConfigurationPublic(String n, String ns, AgentConfigurationPublic o, Boolean isNullable, Boolean needType)
                        at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write7_AgentConfigurationPublic(Object o)

12.1.4416 vs 12.0.4416

$
0
0
I have seen version references to SQL Server 2014 SP1 CU1 as being 12.1.4416 and 12.0.4416, I would believe that the later on is the correct one, however since 12.1.4416 is not uncommon to see i was wondering if MSFT did change the naming concept or what is the reason for that ?

[SOLVED] A MOF syntax error occured, installing SQL Server 2012 Advanced Express 64 bit edition

$
0
0

I'm trying to install SQL server on my windows 7 workstation and got this error:

A MOF syntax error occured.

I looked in the SQL setup bootstrap folder and found the detail.txt. It says:

(01) 2015-11-29 19:23:58 Slp: Installing WMI Provider
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\110
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to get registry value SharedCode
(01) 2015-11-29 19:23:58 Slp: SharedDirPath is C:\Program Files (x86)\Microsoft SQL Server\110\Shared\
(01) 2015-11-29 19:23:58 Slp: Attempting to install MOF/MFL file for WMI Provider C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(01) 2015-11-29 19:23:58 Slp: Sco: Attempting to install MOF file
(01) 2015-11-29 19:23:58 Slp: Running: C:\Windows\system32\WBEM\mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof"
(10) 2015-11-29 19:23:59 Slp: Microsoft (R) MOF Compiler Version 6.1.7600.16385
(10) 2015-11-29 19:23:59 Slp: Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
(10) 2015-11-29 19:24:00 Slp: Parsing MOF file: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof
(10) 2015-11-29 19:24:00 Slp: MOF file has been successfully parsed
(10) 2015-11-29 19:24:00 Slp: Storing data in the repository...
(10) 2015-11-29 19:24:03 Slp: An error occurred while processing item 10 defined on lines 73 - 79 in file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof:
(10) 2015-11-29 19:24:03 Slp: Compiler returned error 0x80070005Error Number: 0x80070005, Facility: Win32
(10) 2015-11-29 19:24:03 Slp: Description: Access is denied.
(10) 2015-11-29 19:24:03 Slp:
(01) 2015-11-29 19:24:03 Slp: Sco: Compile operation for mof file C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof failed. Exit code 3
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:03 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:03 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2015-11-29 19:24:03 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-11-29 19:24:04 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-11-29 19:24:04 Slp: Inner exceptions are being indented
(01) 2015-11-29 19:24:04 Slp:
(01) 2015-11-29 19:24:04 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2015-11-29 19:24:04 Slp:     Message:
(01) 2015-11-29 19:24:04 Slp:         A MOF syntax error occurred.
(01) 2015-11-29 19:24:04 Slp:     HResult : 0x84bb0001
(01) 2015-11-29 19:24:04 Slp:         FacilityCode : 1211 (4bb)
(01) 2015-11-29 19:24:04 Slp:         ErrorCode : 1 (0001)
(01) 2015-11-29 19:24:04 Slp:     Data:
(01) 2015-11-29 19:24:04 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2015-11-29 19:24:04 Slp:       WatsonConfigActionData = INSTALL@CONFIGNONRC@COMMONFILES
(01) 2015-11-29 19:24:04 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2015-11-29 19:24:04 Slp:     Stack:
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof()
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_ConfigWMIProvider(Dictionary`2 actionData)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.Install_PostMSI(Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.Slp.SlpConfigurationPrivate.InstallImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-11-29 19:24:04 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-11-29 19:24:04 Slp: Watson Bucket 1
 Original Parameter Values

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : INSTALL@CONFIGNONRC@COMMONFILES

(01) 2015-11-29 19:24:04 Slp:
 Final Parameter Values

(01) 2015-11-29 19:24:04 Slp: Parameter 0 : SQL Server 2012@RTM@

(01) 2015-11-29 19:24:04 Slp: Parameter 1 : 0xA60E3551

(01) 2015-11-29 19:24:04 Slp: Parameter 2 : 0xA60E3551

(01) 2015-11-29 19:24:04 Slp: Parameter 3 : 0xD3BEBD98@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 4 : 0xD3BEBD98@1211@1

(01) 2015-11-29 19:24:04 Slp: Parameter 5 : Slp_Config_Install_Core_WMI_Provider

(01) 2015-11-29 19:24:04 Slp: Parameter 6 : 0x4E91350D

(01) 2015-11-29 19:24:06 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:12 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-11-29 19:24:13 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20151129_184406\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2015-11-29 19:24:50 Slp: A MOF syntax error occurred.
(01) 2015-11-29 19:24:50 Slp: Watson bucket for exception based failure has been created
(01) 2015-11-29 19:38:42 Slp: Error: Action "Slp_Config_Install_Core_WMI_Provider_Cpu64" failed during execution.
(01) 2015-11-29 19:38:42 Slp: Completed Action: Slp_Config_Install_Core_WMI_Provider_Cpu64, returned False

How do I rectify this? Grateful for your advice.


Missing SqlSqmShared.msp when trying to apply hotfix in SQL 2012

$
0
0

Where to find SqlSqmShared.msp?

Below from Summary.txt:

Overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709373
  Exit facility code:            1202
  Exit error code:               3
  Exit message:                  The cached patch file "C:\windows\Installer\5655457.msp" is missing. The original file for this cached file is "SqlSqmShared.msp", which can be installed from "Service Pack 2 for SQL Server 2012 (KB2958429) (64-bit)", version 11.2.5058.0.  For more information about how to resolve this problem, see “Steps to resolve missing media issue with SQL Server 2012” (http://go.microsoft.com/fwlink/?LinkId=144387) in the Microsoft Knowledge Base.
  Start time:                    2015-11-28 15:50:46
  End time:                      2015-11-28 15:56:21
  Requested action:              Patch
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5613.0&EvtType=0xCACAAFBF%400xF762992B%401202%403&EvtType=0xCACAAFBF%400xF762992B%401202%403

Obvioulsy as the error message indicates I looked after it in the extracted SP2. BUT no luck.

Any one know, I'm still trying to find a solution ...


Clean install of SQL Server 2014's Management Tools (SSMS) fails on ScenarioEngine.exe

$
0
0

SqlSetup.log:

Attempting to run user requested action from media ScenarioEngine.exe
Attempting to launch process <Path2Source>\x64\ScenarioEngine.exe
Process returned exit code: 0x84BC051B
Media ScenarioEngine.exe returned exit code: 0x84BC051B

The install is on any Windows 7 image.  Fails when running setup.exe //ConfigurationFile=install.ini or running

setup.exe /ACTION="Install" /IACCEPTSQLSERVERLICENSETERMS /ENU /UpdateEnabled=0 /FEATURES="ADV_SSMS" /QS

Fails if the source is local or on a network.  Tried different sources with same error.

Manual installs without problems.

Images have 6gig available at 2gig memory.  Installing as administrator.  .NET 4.5 is installed.

The error happens at the end of the installation.

Do I need to reinstall SQL 2008 Service Pack 4

$
0
0

I installed SQL Server 2008 on my server, with the features that I required.  I then installed Service Pack 4 and also installed any important SQL updates, that have been released since SP4.

I have since had to add an additional feature to the installation - the 'Management Tools - Complete' feature.  This is because I was unable to modify Maintenance Plans, using SQL Server Management Studio, on the server.

Do I now need to reinstall SQL 2008 Service Pack 4 and the subsequent SQL updates, on my SQL Server?

Thanks.

SQL Server licence agreement cannot be located for the selected edition, EXPRESS

$
0
0

Hello,

I tried to install a new software from a company in Germany and get the following error:

SQL Server Setup has encountered the following error:
The SQL Server licence agreement cannot be located for the selected edition, EXPRESS. THis could be a result of corrupted media or the edition being unsupported by the media.
Error code 0X858C001B

I'd appreciate your help.

Kind regards

Peter

RC license and production

$
0
0

We are developing a project and incorporating a lot of new functionality located in SQL 2016 CTP. Chances are we're going to be ready to put this project into production ahead of the release of SQL 2016. So, the big hairy question is based on licensing terms, will we be allowed to run SQL 2016 CTP in a production environment until it's released at which point we can buy the appropriate license and upgrade the environment?

I get that running CTP doesn't yield us any support if we are not in any type of TAP program, but this is the platform our client has chosen for the functionality and they will need to go into production in early Q1 2016. 

I'm really just looking for approval on using the license until it's released.

Thanks.


SQL Server 2012 Service Pack 3 has broken my SQL Agent and all remote connections

$
0
0

Hello, I am having a problem with Service Pack 3 for SQL Server 2012.  The upgrade appears to have completed successfully according to all the logs.  However, I am having a few issues now.

1) The SQL Agent does not start anymore.  It throws the following set of errors in the Event Log

Application - SQLServerAgent service successfully started.

System - An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.

System - A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows SChannel error state is 1205.

Application - SQLServerAgent could not be started (reason: Unable to connect to server 'MYSERVER\PROD'; SQLServerAgent cannot start).

Application - SQLServerAgent service successfully stopped.

2) I cannot connect to this server remotely from anywhere, regardless if the Windows Firewall is turned on or off

3) I can connect to the server locally and can query data with t-sql in SSMS, but when I try to pull up the SQL Log I get the error message: 

===================================

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.NavigableItemBuilderDataReader.RunQuery()
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.NavigableItemBuilderDataReader.Process()
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.NavigableItemBuilderDataReader.get_PropertyNames()
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItemWithQuery(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.BuildDynamicItem(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItemBuilder.Build(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, IFilterProvider filter)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.RequestChildren(IGetChildrenRequest request)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)

===================================

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Common.ServerConnection.GetExecuteReader(SqlCommand command)
   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand, SqlCommand& command)
   at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query, SqlCommand& command)
   at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)
   at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.GetData(EnumResult erParent)
   at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
   at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)

===================================

A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476

------------------------------
Server Name: ENESQL01\PROD
Error Number: 233
Severity: 20
State: 0


------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
   at Microsoft.SqlServer.Management.Common.ServerConnection.GetExecuteReader(SqlCommand command)

===================================

No process is on the other end of the pipe

It is like it is unable to remotely connect and run a query!

This is my production server so it is rather important that I get some sort of resolution on this problem fairly quickly.

I have read the article about TLS 1.2 errors but I can't understand why it would be affecting my server as this all worked just about a half hour ago...what changed in SQL Server 2012 SP3 that would prevent any remote connections to this server?

One additional piece of information.  Our domain is running at 2003 level in case this matters.


The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to me and deleting it from your computer. Thank you



SQL 2008R2 - Repair with errors - Please help urgent

$
0
0

Hi ,<o:p></o:p>

I have encountered an issue while doing the repair of my current SQL 2008 R2 instance. The error is being shown while repairing Reporting services .  Please see below for the error. <o:p></o:p>

The reason for doing the repair is , the local SQL Server service groups were missing on the server and I have fixed it by doing the repair in the past on a different server. 
Please provide help and let me for any additional info....<o:p></o:p>

Thanks Naz

Error message : <o:p></o:p>

TITLE: SQL Server 2008 R2 Setup<o:p></o:p>

------------------------------<o:p></o:p>

 <o:p></o:p>

The following error has occurred:<o:p></o:p>

 <o:p></o:p>

Value cannot be null.<o:p></o:p>

Parameter name: instanceId<o:p></o:p>

 <o:p></o:p>

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x2070761E%25400x11428655<o:p></o:p>

 <o:p></o:p>

------------------------------<o:p></o:p>

BUTTONS:<o:p></o:p>

 <o:p></o:p>

OK

<o:p></o:p>


Naz DBA


Marking your questions as Answered

$
0
0

 Hi All,

I want to make a pitch to have folks mark their questions as Answered once you've received an Answer that solves your problem. Everyone who posts a question has the ability to mark that question as Answered by clicking the Answered button for the Post that best answers the question.

There are a couple good reasons to do this:

  • Our search engine weights Answered questions more highly. By marking Answers you increase the chances that others searching this forum will find the answer directly rather than re-posting the question.
  • You give credit to the hard working folks who answer your questions. This is peer to peer support, so recognition is our only reward. (Check out the Top Answerers in 30 Days chart at the bottom of the thread list to see who is currently answering questions.)
  • You help me track the health of this forum. I get mail every day telling me how many unanswered questions are in this forum and I work to keep those numbers at a certain level. By marking Answers, I get a more accurate understanding.

I apreciate everyone's participation in the SQL Setup & Upgrade Forum whether you're asking questions, answering question or just reading along. Marking Answers is one way we can all work together to make the forum a little better.

Regards,

Sam Lester

My Blog

This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click"Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Error upgrading a SQL 2012 cluster to 2014

$
0
0

Hi

I keep getting an error whilst trying to upgrade the passive node of a SQL 2012 cluster to SQL 2014 with SP1

The setup fails with this error whilst it's running this part 'ReplConfigAction_upgrade_ConfigNonRC_Cpu64'

The following error has occurred:
The system cannot find the file specified

It doesn't say which file it ca not find.

In the detail.txt the error is documented further with this information:

Any ideas??  It does it every time i run the setup

(01) 2015-12-07 15:14:44 Slp: ---- Flush datastore cache before calling configuration action 'ReplConfigAction_upgrade_ConfigNonRC_Cpu64'
(01) 2015-12-07 15:14:44 Slp: ----------------------------------------------------------------------
(01) 2015-12-07 15:14:44 Slp: Running Action: ReplConfigAction_upgrade_ConfigNonRC_Cpu64
(01) 2015-12-07 15:14:44 Slp: Action Data:
(01) 2015-12-07 15:14:44 Slp:   Feature = SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64
(01) 2015-12-07 15:14:44 Slp:   Scenario = upgrade
(01) 2015-12-07 15:14:44 Slp:   Timing = ConfigNonRC
(01) 2015-12-07 15:14:44 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate
(01) 2015-12-07 15:14:44 Slp:   FeatureName = SQL_Replication_Core_Inst
(01) 2015-12-07 15:14:44 Slp:   FeatureCpuType = Cpu64
(01) 2015-12-07 15:14:44 Slp:   FeaturePackageId = sql_engine_core_inst
(01) 2015-12-07 15:14:44 Slp:   FromVersion = 11.2.5058.0
(01) 2015-12-07 15:14:44 Slp:   FromLanguage = 1033
(01) 2015-12-07 15:14:44 Slp:   PreviousInstalledClusterState = CompleteFailoverCluster
(01) 2015-12-07 15:14:44 Slp:   FeatureClusterState = CompleteFailoverCluster
(01) 2015-12-07 15:14:44 Slp:   SlipstreamInstall = 1
(01) 2015-12-07 15:14:44 Slp: Upgrade: Repl Configuration
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to open registry subkey 120\Replication
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\Setup
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value SQLGroup
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed:  D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to set security descriptor D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to normalize security descriptor D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed:  D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to normalize security descriptor D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed:  D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)
(01) 2015-12-07 15:14:44 Slp: SetSecurityDescriptor: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\120\Replication, appending
(01) 2015-12-07 15:14:44 Slp: Repl: Copying individual replication values.
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-12-07 15:14:44 Slp: Repl: Upgrade from unsupported version.
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Replication
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value isinstalled
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value kind for value isinstalled
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-12-07 15:14:44 Slp: Repl: Upgrade from unsupported version.
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Replication
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value workingdirectory
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value kind for value workingdirectory
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2015-12-07 15:14:44 Slp: Repl: Upgrade from unsupported version.
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Replication
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value distributiondb
(01) 2015-12-07 15:14:44 Slp: Sco: Attempting to get registry value kind for value distributiondb
(01) 2015-12-07 15:14:44 Slp: Configuration action failed for feature SQL_Replication_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-12-07 15:14:44 Slp: The system cannot find the file specified.

(01) 2015-12-07 15:14:44 Slp: The configuration failure category of current exception is ConfigurationFailure
(01) 2015-12-07 15:14:44 Slp: Configuration action failed for feature SQL_Replication_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC.
(01) 2015-12-07 15:14:44 Slp: Microsoft.SqlServer.Configuration.Sco.SqlRegistryException: The system cannot find the file specified.
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.ExecuteNative(Int32 result)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.GetValueKind(String name)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.GetValueFromRegistry(ReplValue value, String instanceId, Version version)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.CopyReplicationValues(Version fromVersion)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.UpgradeConfigNonRCImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent, Version fromVersion)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.UpgradeImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent, Version fromVersion)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-12-07 15:14:44 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-12-07 15:14:44 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-12-07 15:14:44 Slp: Inner exceptions are being indented
(01) 2015-12-07 15:14:44 Slp:
(01) 2015-12-07 15:14:44 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.SqlRegistryException
(01) 2015-12-07 15:14:44 Slp:     Message:
(01) 2015-12-07 15:14:44 Slp:         The system cannot find the file specified.
(01) 2015-12-07 15:14:44 Slp:         
(01) 2015-12-07 15:14:44 Slp:     HResult : 0x84d10002
(01) 2015-12-07 15:14:44 Slp:         FacilityCode : 1233 (4d1)
(01) 2015-12-07 15:14:44 Slp:         ErrorCode : 2 (0002)
(01) 2015-12-07 15:14:44 Slp:     Data:
(01) 2015-12-07 15:14:44 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Sco.SqlRegistryException@Win32Error
(01) 2015-12-07 15:14:44 Slp:       SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2015-12-07 15:14:44 Slp:       WatsonConfigActionData = UPGRADE@CONFIGNONRC@SQL_REPLICATION_CORE_INST
(01) 2015-12-07 15:14:44 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2015-12-07 15:14:44 Slp:     Stack:
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.ExecuteNative(Int32 result)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.GetValueKind(String name)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.GetValueFromRegistry(ReplValue value, String instanceId, Version version)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.CopyReplicationValues(Version fromVersion)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.UpgradeConfigNonRCImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent, Version fromVersion)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.Repl.ReplConfigurationPrivate.UpgradeImpl(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent, Version fromVersion)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2015-12-07 15:14:44 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2015-12-07 15:14:44 Slp: Watson Bucket 3
 Original Parameter Values

(01) 2015-12-07 15:14:44 Slp: Parameter 0 : SQL Server 2014@RTM@

(01) 2015-12-07 15:14:44 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.ExecuteNative

(01) 2015-12-07 15:14:44 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.ExecuteNative

(01) 2015-12-07 15:14:44 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.Sco.SqlRegistryException@1233@2

(01) 2015-12-07 15:14:44 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.Sco.SqlRegistryException@1233@2

(01) 2015-12-07 15:14:44 Slp: Parameter 5 : ReplConfigAction_upgrade_ConfigNonRC

(01) 2015-12-07 15:14:44 Slp: Parameter 6 : UPGRADE@CONFIGNONRC@SQL_REPLICATION_CORE_INST

(01) 2015-12-07 15:14:44 Slp: Parameter 7 : Microsoft.SqlServer.Configuration.Sco.SqlRegistryException@Win32Error

(01) 2015-12-07 15:14:44 Slp: Parameter 8 : Microsoft.SqlServer.Configuration.Sco.SqlRegistryException@Win32Error

(01) 2015-12-07 15:14:44 Slp:
 Final Parameter Values

(01) 2015-12-07 15:14:44 Slp: Parameter 0 : SQL Server 2014@RTM@

(01) 2015-12-07 15:14:44 Slp: Parameter 1 : 0x21656841

(01) 2015-12-07 15:14:44 Slp: Parameter 2 : 0x21656841

(01) 2015-12-07 15:14:44 Slp: Parameter 3 : 0xAC7B1A58@1233@2

(01) 2015-12-07 15:14:44 Slp: Parameter 4 : 0xAC7B1A58@1233@2

(01) 2015-12-07 15:14:44 Slp: Parameter 5 : ReplConfigAction_upgrade_ConfigNonRC

(01) 2015-12-07 15:14:44 Slp: Parameter 6 : 0xF32688B2

(01) 2015-12-07 15:14:44 Slp: Parameter 7 : 0xD195CE25

(01) 2015-12-07 15:14:44 Slp: Parameter 8 : 0xD195CE25

(01) 2015-12-07 15:14:46 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151207_150533\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2015-12-07 15:14:46 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151207_150533\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-12-07 15:14:46 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151207_150533\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2015-12-07 15:14:46 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151207_150533\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2015-12-07 15:14:46 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151207_150533\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2015-12-07 15:14:46 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20151207_150533\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2015-12-07 15:14:47 Slp: The system cannot find the file specified.

(01) 2015-12-07 15:14:47 Slp: Watson bucket for exception based failure has been created
(01) 2015-12-07 15:15:11 Slp: Error: Action "ReplConfigAction_upgrade_ConfigNonRC_Cpu64" failed during execution.
(01) 2015-12-07 15:15:11 Slp: Completed Action: ReplConfigAction_upgrade_ConfigNonRC_Cpu64, returned False

SQL Server client tools for Windows 10

$
0
0
My Surface 3 with Win 8.1 crashed and now I have a new Surface with Win 10. Can someone give me a link to download the appropriate version of SQL Server Client tools for Win 10. I only want SQL Server Management Studio on my Surface not the full installation with the DB engine. I am connecting to a 2008 SQL server. 

SQL Server 2008 Installation Hangs on Install_sql_tools_Cpu64_Action: Write_NativeImage64. Generating Native Images

$
0
0
Hi, I have been trying to Install Sql Server 2008 on my 64 bit Vista Ultimate machine.  It gets about 70% through the installation and hangs on the part that says "Install_sql_tools_Cpu64_Action: Write_NativeImage64. Generating Native Images"  I have tried for the last 3 days with no luck.  I have tried un-installing and deleting directories but no luck.  I have scene several posts about the same problem but no solutions except one guy who uninstalled every thing but SQL Server 2008 and re-installed.  I have tried that but it did not help.

Install SQL Server 2012 error 0x858C001B

$
0
0

Hello,

I'm installing SQL Server 2012 enterprise edition with SP3 x64 fr on a Windows 7 Professional SP1 and I get the following error :

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

SQL Server Setup has encountered the following error:

The SQL Server license agreement cannot be located for the selected edition, ENTERPRISE. This could be a result of corrupted media or the edition being unsupported by the media.

Error code 0x858C001B.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0xFDC38F1F%25400xA40CEF17%25401420%254027

------------------------------
BUTTONS:

OK
------------------------------

I've read a lot of threads on the problem on the site and on others but none solved it. So here are the points I tried :
- I downloaded the package from the MSDN site twice,
- I've extracted the archive with WinRar,
- I've moved the extract folder to the localization C:\,
- I switch the language of my computer from "French (France)" to "English (US)" and to "English (United Kingdom)" but I have an error message when I launch the setup with a language other than French,
- I've deleted the folder "Setup Bootstrap" under C:\Program Files\Microsoft SQL Server\110\ between each try,
- The 9 operations from the "Setup Support Rules" are all passed,
- It's a fresh new computer so there were no old SQL Server install before and there are no trace of SQL Server in the programs list,
- I'm admin on my computer,
- I tried to launch the install with the command "Run as administrator".

If anyone can help, that would be so great !!

Cédric

SQL Server 2012 Service Pack 3 constantly fails with Windows Update Code 84B30002

$
0
0

I have MS SQL 2008 R2 Developer, MS SQL 2014 Express, MS SQL 2014 Developer, Visual Studio 3013 Community & Visual Studio 3015 Community

I also installed MSDT & BI templates for Visual Studio 3013

Operation system Windows 8.1 x64 Pro

I have never installed MS SQL 2012 but I found out SQL Server 2012 Service Pack 3 as optional update.  When I tried to install it I got a Code 84B30002. 

When I opened list of installed products I found out following products

Microsoft SQL Server 2012

Microsoft SQL Server 2012 Command Line Utilities

Microsoft SQL Server 2012 Data-Tier Up framework

Microsoft SQL Server 2012 Data-Tier Up framework (x64)

Microsoft SQL Server 2012 Express local DB

Microsoft SQL Server 2012 Management Objects

Microsoft SQL Server 2012 Management Objects (x64)

Microsoft SQL Server 2012 Native Client

Microsoft SQL Server 2012  Setup (English)

Microsoft SQL Server 2012 Transact-SQL Compiler Service

Microsoft SQL Server 2012 Transact-SQL ScriptDom

Microsoft SQL Server 2012 T-SQL Language Service

Microsoft SQL Server 2012 T-SQL Language Service

Microsoft SQL Server data Tools 2012

Microsoft System CLR Types for SQL Server 2012

Microsoft System CLR Types for SQL Server 2012 (x64)

It is possibly that it was installed with Visual Studio 3013 Community

What I would have to install manually or not install at all (hide this update)?

P.S. I checked when this stuff has been installed - it happened partially when I installed VS 2013 community and some stuff came with MS SQL 2014 Developer


P.P.S.  I tried to run this update manually and got following message:

"There are no SQL Server instances or shared features that can be updated on this computer"

Of course I have never installed MS SQL 2012 on my own.  Moreover there were ~8 Gb download @ Windows Updates.  At the same time there are x64 version - 1.0 Gb & x86 version - 732 Mb


Viewing all 7696 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>