Quantcast
Channel: SQL Server Setup & Upgrade Forum
Viewing all 7701 articles
Browse latest View live

Could not locate the service

$
0
0

hi - I am hoping that someone can help with this.

I have a new server (2008R2SP1) and Installed SQL 2008R2 SP3 Database and Management tools only.

All looks like it has installed correctly, however when I try to stop the SQL service from the SQL Server Management Studio I get the Error "Could not locate the Service".

I can stop the services correctly from both the Services.msc and the SQL Server Configuration Manager.

I can see that the SQL Server Management Studio uses the command

"C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ControlService.exe" -computer <SERVERNAME> -service MSSQLSERVER -stop

So if I run that command from an elevated Command Prompt I get the same result "Could not locate the Service".

I have tried reinstalling but to no avail.

does anyone have experience with this issue?

Many thanks,

Alan


Regards, Alan


SQL instance (default and named) installation on separate partitions

$
0
0

Hi,

Can we install multiple sql named instances on different-2 (separate) partitions ??

Currently we have one default instance of sql installed  and we have to install the multiple named installed on separate partitions on same server box. can we do that , Is any limitation of SQL in this senario ?

also is any SQL ver is limited to this ?


Shailendra Dev

SQL SERVER 2014 Installation error

$
0
0

Hi, I'm having great difficulty in installing SQL server 2014 developer edition 64- bit . When I use to run setup it says sql server boot strapper.dll is missing although it is present inside the folder and when I opened the sql setup bootstrapper.dll it gives the error "This file doesn't have a program associated with it for performing this action".  ? I've attached the snapshot of the error as well.

Needs immediate help.

Windows Installer error message: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more info

$
0
0

I have been receiving this error trying to install SQL Server 2012. Initially I already had SQL Server 2012 on my machine and attempted to install BIDS 2008. My IT guy stated that there was a conflict in the installation and suggested that I uninstall SQL Server 2012 and then attempt to install 2008 BIDs again. Fail. I got a similar error as I pasted below. Giving up on having 2008 BIDS I've been trying to reinstall 2012 SQL Server but am getting this message below.

The links provided by this message are no help at all (For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xDF039760%25401201%25401)

I've attempted to repair my .NET framework, didn't help.

I've followed the steps in these threads (http://support.microsoft.com/kb/2688946), (https://support.microsoft.com/kb/957310?wa=wsignin1.0) and (https://social.msdn.microsoft.com/Forums/en-US/beeceb19-69cc-4044-94f0-591feec04626/an-error-occurred-during-the-installation-of-assembly-microsoftvc80crt-public-key), neither one fixed the error.

Any help? Anyone else run into this error? What should I do?

TITLE: Microsoft SQL Server 2012  Setup
------------------------------

The following error has occurred:

An error occurred during the installation of assembly 'Microsoft.VC80.ATL<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="2d0ab9fa-7943-473c-b5ee-0a6d6b7194b8" id="e03584ff-5e55-4073-ac2e-d3e07379c0ae">,</gs>version="8.0.50727.4053"<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="2d0ab9fa-7943-473c-b5ee-0a6d6b7194b8" id="20b968d8-03a3-4284-bffc-0cc1a90d2aac">,</gs>publicKeyToken="1fc8b3b9a1e18e3b"<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="2d0ab9fa-7943-473c-b5ee-0a6d6b7194b8" id="9b86ea8f-9852-4110-a616-a1e085d740c6">,</gs>processorArchitecture="x86"<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="2d0ab9fa-7943-473c-b5ee-0a6d6b7194b8" id="f52b7568-d5e6-4099-a8ee-ebc11fbf4acc">,</gs>type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80073712. 

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xDF039760%25401201%25401

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

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



TITLE: Microsoft SQL Server 2012  Setup
------------------------------

The following error has occurred:

SQL Server Setup has encountered an error when running a Windows Installer file.

Windows Installer error message: An error occurred during the installation of assembly 'Microsoft.VC80.ATL<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="6682fddf-3b37-48f0-83c9-ec13036b3ec3" id="297b0922-8852-404d-9dc1-a9b38415a2e5">,</gs>version="8.0.50727.4053"<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="6682fddf-3b37-48f0-83c9-ec13036b3ec3" id="785a0f51-5ed5-41ee-97a8-8fc31122e2ae">,</gs>publicKeyToken="1fc8b3b9a1e18e3b"<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="6682fddf-3b37-48f0-83c9-ec13036b3ec3" id="8aa968bd-ff25-4e9d-9109-a219a98ee5e8">,</gs>processorArchitecture="x86"<gs class="GINGER_SOFTWARE_mark" ginger_software_uiphraseguid="6682fddf-3b37-48f0-83c9-ec13036b3ec3" id="aa9e7ba2-4f5a-4d89-bf64-dcff0714afaa">,</gs>type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80073712. 
Windows Installer file: c:\2f4e5903553a88acc6726f538e140c4d\1033_ENU_LP\x64\setup\sqlsupport_msi\SqlSupport.msi
Windows Installer log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150213_150637\SqlSupport_Cpu64_1_ComponentUpdate.log

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xDC80C325

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

&Retry
Cancel
------------------------------

Full list of MS SQL 2000 features that are supported in compatibilty 80 mode but not available in 2008 R2 compatibility 100

$
0
0

Hello Everyone,

Could you possibly suggest where I can find a full list MS SQL 2000 features that are supported in 2008 R2 compatibilty 80 mode but not available in  compatibility 100?

Thanks


SSIS question

Finding SQL Server licensing information for 2005 and above.

$
0
0

I can use SELECT serverproperty('LicenseType'), serverproperty('NumLicenses') on SQL Server 2000 but these server properties are no longer being returned in SQL Server 2005 and later.  This information doesn't seem to be recorded in the registry for SQL Server 2005 and later.

Is there an easy way to query or report licensing information for SQL Server 2005 onwards?

Thanks.




SCCM 2012R2/SQL 2008R2 CU4 problem

$
0
0

Hi All,

our environment: SCCM 2012R2 / SQL 2008R2
Wanted to apply the CU4 for SCCM but when it comes to updating SQL i'm getting following errors:
Could someone please advise re solving the problem?

Thanks a lot in advance.

Msg 2812, Level 16, State 62, Line 1
Could not find stored procedure 'k'.
Msg 207, Level 16, State 1, Procedure spAddRecoveryTrackingRecord, Line 41
Invalid column name 'TransportType'.
Msg 207, Level 16, State 1, Procedure spAddRecoveryTrackingRecord, Line 46
Invalid column name 'TransportType'.
Msg 207, Level 16, State 1, Procedure spAddRecoveryTrackingRecord, Line 49
Invalid column name 'TransportType'.

(0 row(s) affected)
Msg 208, Level 16, State 6, Procedure v_ContentDistributionReport_G, Line 2
Invalid object name 'v_ContentDistributionReport_G'.

(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)

(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(2 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(2 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(2 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)
(0 row(s) affected)

Installed SQL Server 2008 R2 with all features and can't find SQL Server Business Intelligence Development Studio

$
0
0

I went to install additional items and found that the installation process has that product greyed out meaning it has been already installed. Where can I find it?

Thank you,

 

Oscar Osorio


Upgrade from SQL 2012 RTM version

$
0
0

Hello,

I found a SQL 2012 instance with a version 11.0.2100.60 meaning a that is a RTM version.

So my question is, can this version by upgraded simple by installing the SPs or first i have to upgrade the licence too?

Thanks,

Rui Bandarra

How to SQL Server icons in start menu (Win Server 2012 R2)

$
0
0

Hi Folk's,

I have an installation of SQL Server 2012 Developer Edition on Windows Server 2012 R2.  The installation was successful with the exception I have no SQL icons in the start menu - so I can't run the SQL Server Management Studio without going and looking for the executable.

Does anyone know how I can re-generate the icons. I have tried doing a repair but this did not work.

Regards

Andy

SQL Server Management Studio has stopped working when changing fonts and colors

$
0
0

I installed sql server management studio 2012 about 3 months ago to test drive and from time to time I'll attempt to change my background color of the TSql editor "In the fonts and colors option under tools"; however, the entire studio crashes and restarts.

This has been ongoing since I first installed it 3 or 4 months ago, and have waited on posting to a fourm for help, assuming I am not the only one this is happening to I've waited for an update that might fix the issue.

I've got to start on some heavy scripting and that god awful white background kills my eyes. I've got to have a black background or my work day is cut off by about 3 hours becuase of strain.

What can I provide to someone that would help me with this?

Thank you,

Erik



Specialize in software for the construction industry.


Powershell DSC - xSQLServer -- xSQLServerSetup error.

$
0
0

Hi All,

I've been trying to automate the installation of SQL Server using the experiment DSC Module for SQL Server.  This issue occurs in my vagrant environments and vCenter environments.

This is the entirety of the script that does the meat and potatoes of the install.

#use xSQLServerSetup of xSQLServer
#sql install error log can be found at C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\log
param (
    [string]$SetupCredA = $(throw "error -SetupCredA is required.  Need installer username."),
    [string]$SetupCredPW = $(throw "error -SetupCredPW is required.  Need installer password."),
	[string]$SvcAccountCredA = $(throw "error -SvcAccountCred is required.  Need to know service account."),
    [string]$SvcAccountPW = $(throw "error -SvcAccountCred is required.  Need to know service account pw."),
    [string]$Features = $(throw "error -Features is required."),
    [string]$SAArray = $(throw "error -SAArray is required.  Need to know sysadmins.")
 )
$SetupCred=New-Object System.Management.Automation.PSCredential ($SetupCredA, $(ConvertTo-SecureString $SetupCredPW -AsPlainText -Force))
$SvcAccountCred=New-Object System.Management.Automation.PSCredential ($SvcAccountCredA, $(ConvertTo-SecureString $SvcAccountPW -AsPlainText -Force))
$Extract="C:\InstallSQL"
$ServerCoreFeatures="SQLENGINE,REPLICATION,FULLTEXT,AS,CONN,IS,SNAC_SDK"
$ServerGUIFeatures="SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,MDS,DREPLAY_CTLR,DREPLAY_CLT"
$ServerGUIFeaturesWithReporting="$ServerGUIFeatures,RS"
$ReportServerFeatures="RS"

switch ($Features) {
    "ServerCoreFeatures" { $Features = $ServerCoreFeatures }"ServerGUIFeatures" { $Features = $ServerGUIFeatures }"ServerGUIFeaturesWithReporting" { $Features = $ServerGUIFeaturesWithReporting }"ReportServerFeatures" { $Features = $ReportServerFeatures }
}


$configData = @{
    AllNodes = @(
          @{
                NodeName = "$($env:computername)"
                PSDscAllowPlainTextPassword = $true
           }
         )
}

Configuration SetupSQL
{
    Import-DSCResource -ModuleName xSQLServer
    Node "$($env:computername)"
    {
        xSQLServerSetup Install-SQL
        {
            SourcePath = $Extract
            SourceFolder = "SQL2014"
            SetupCredential = $SetupCred
            #-------------
            SQLSvcAccount = $SvcAccountCred
            AgtSvcAccount = $SvcAccountCred
            SQLSysAdminAccounts = $SAArray
            #--------------------
            UpdateEnabled = "False"
            UpdateSource = "$Extract\SQL2014\Updates"
            #-----------------
            ErrorReporting = "True"
            #-----------------
            SQLUserDBDir = "M:\Data"
            SQLUserDBLogDir = "L:\Log"
            SQLTempDBDir = "T:\TempDB"
            SQLTempDBLogDir = "T:\TempLog"
            SQLBackupDir = "M:\Backup"
            #-----------------
            InstanceName= "MSSQLSERVER"
            Features = $Features
        }

    }

}
SetupSQL -ConfigurationData $configData
Start-DscConfiguration .\SetupSQL -force -wait -verbose

The environment is prestaged with

$Modules="C:\Program Files\WindowsPowerShell\Modules"
$Extract="C:\InstallSQL"
$ResourceKit="$Extract\DSCRK9.zip"
$WinSXSFiles="$Extract\sxsfiles.zip"
$SQLInstall="$Extract\SQL2014.zip"
mkdir $Extract -force
write-host "$(get-date) Downloading install resources"
start-bitstransfer "http://downloads.yosemite.local/files/application/microsoft/sqlinstall/dscrk9.zip" $ResourceKit
start-bitstransfer "http://downloads.yosemite.local/files/application/microsoft/sqlinstall/sxsfiles.zip" $WinSXSFiles
start-bitstransfer "http://downloads.yosemite.local/files/application/microsoft/sqlinstall/sql2014.zip" $SQLInstall
write-host "$(get-date) Download completed"
Configuration PreStageSQL
{

    Archive Extract-Resource-Kits
    {
        Ensure = "Present"
        Path = $ResourceKit
        Destination = $Extract
    }

    Archive Extract-WinSXS-Files
    {
        Ensure = "Present"
        Path = $WinSXSFiles
        Destination = $Extract
        DependsOn = "[Archive]Extract-Resource-Kits"
    }

	Archive Extract-SQL-Files
    {
        Ensure = "Present"
        Path = $SQLInstall
        Destination = $Extract
        DependsOn = "[Archive]Extract-WinSXS-Files"
    }

	File Move-Resource-Files
    {
       SourcePath = "$Extract\All Resources"
       DestinationPath = $Modules
       Ensure = "Present"
       Type = "Directory"
       Recurse = $True
       MatchSource = $True
       DependsOn = "[Archive]Extract-SQL-Files"
    }

	WindowsFeature Install-NET35
    {
        Name = "NET-Framework-Core"
        Source = "$Extract\sxs"
        Ensure = "Present"
        DependsOn = "[File]Move-Resource-Files"
    }

}
PreStageSQL
Start-DscConfiguration .\PreStageSQL -force -wait -verbose
write-host "$(get-date) completed"

The setup errors out at the end with the following messages in the console/event log.  The SQL Install itself appears to be complete.  I've tried this with UpdateEnabled = "true" as well and it errors at the same location.

So the install appears to complete successfully but powershell reports an error

'C:\InstallSQL\SQL2014\setup.exe' started in process ID 192
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function 'NetUse'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function 'ResolvePath'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function
'StartWin32Process'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Importing function
'WaitForWin32ProcessEnd'.
VERBOSE: [WINDOWS2012R2]:                            [[xSQLServerSetup]Install-SQL] Path:
C:\InstallSQL\SQL2014\setup.exe
VERBOSE: [WINDOWS2012R2]: LCM:  [ End    Set      ]  [[xSQLServerSetup]Install-SQL]  in 500.8120 seconds.
PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message:
Set-TargetResouce failed+ CategoryInfo          : InvalidOperation: (:) [], CimException+ FullyQualifiedErrorId : ProviderOperationExecutionFailure+ PSComputerName        : WINDOWS2012R2

The SendConfigurationApply function did not succeed.
    + CategoryInfo          : NotSpecified: (root/Microsoft/...gurationManager:String) [], CimException+ FullyQualifiedErrorId : MI RESULT 1+ PSComputerName        : WINDOWS2012R2

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 501.455 seconds

With the following errors in event viewer.  

Job {5E0C5C09-B7B2-11E4-80B6-000C29F93310} :
Message Set-TargetResouce failed
HResult -2146233087
StackTrack    at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
   at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Job {5E0C5C09-B7B2-11E4-80B6-000C29F93310} :
This event indicates that failure happens when LCM is processing the configuration. ErrorId is 0x1. ErrorDetail is The SendConfigurationApply function did not succeed.. ResourceId is [xSQLServerSetup]Install-SQL and SourceInfo is C:\InstallSQL\InstallSQL.ps1::41::9::xSQLServerSetup. ErrorMessage is PowerShell DSC resource MSFT_xSQLServerSetup  failed to execute Set-TargetResource functionality with error message: Set-TargetResouce failed .

Job {5E0C5C09-B7B2-11E4-80B6-000C29F93310} :
DSC Engine Error :
	 Error Message The SendConfigurationApply function did not succeed.
	Error Code : 1 
However everything from the SQL install summary appears to have been created.

Overall summary:
  Final result:                  Passed
  Exit code (Decimal):           0
  Start time:                    2015-02-18 21:09:08
  End time:                      2015-02-18 21:17:01
  Requested action:              Install

Machine Properties:
  Machine name:                  WINDOWS2012R2
  Machine processor count:       2
  OS version:                    Windows Server 2012
  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 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\InstallSQL\SQL2014\x64\setup\
  Installation edition:          Enterprise Edition: Core-based Licensing

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 Administrator
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Automatic
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            Administrator
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:
  CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
  CLTSTARTUPTYPE:                Manual
  CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150218_210907\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               Manual
  CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                true
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
  FTSVCPASSWORD:                 <empty>
  HELP:                          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:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT Service\MsDtsServer120
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  C:\Backup
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 Administrator
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Administrator, Administrator
  SQLTEMPDBDIR:                  C:\TempDB
  SQLTEMPDBLOGDIR:               C:\TempLog
  SQLUSERDBDIR:                  C:\Data
  SQLUSERDBLOGDIR:               C:\Log
  SQMREPORTING:                  false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  C:\InstallSQL\SQL2014\Updates
  USEMICROSOFTUPDATE:            false
  X86:                           false

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

Detailed results:
  Feature:                       Management Tools - Complete
  Status:                        Passed

  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Client Tools SDK
  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed

  Feature:                       Database Engine Services
  Status:                        Passed

  Feature:                       Data Quality Services
  Status:                        Passed

  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Passed

  Feature:                       SQL Server Replication
  Status:                        Passed

  Feature:                       Master Data Services
  Status:                        Passed

  Feature:                       Distributed Replay Client
  Status:                        Passed

  Feature:                       Distributed Replay Controller
  Status:                        Passed

  Feature:                       Integration Services
  Status:                        Passed

  Feature:                       Data Quality Client
  Status:                        Passed

  Feature:                       Analysis Services
  Status:                        Passed

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Documentation Components
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150218_210907\SystemConfigurationCheck_Report.htm

The problem I run into is when I attempt to invoke this particular script from CI tools, the error triggers a false exit of the provision.  Additionally the error seems to happen before I can install updates.  

I am using SQL2014.  Does anybody have any ideas?

Uninstall "SQL 2008 R2 Express" (Common Files & Database Engine Shared)??

$
0
0

I've been trying to uninstall SQL 2008 R2 Express but no luck.

I think I didn't remove the components in right order in Control Panel..

Now, I have left with a component calll "Microsoft SQL Server 2008 R2 Setup (English)" which I can't get rid of..

When I try to uninstall it, it gives me an error "Warning 26003. MS Server 2008 R2 Setup Support Files cannot be uninstalled because the following products are installed:

SQL Server 2008 R2 Common Files

SQL Server 2008 R2 Database Engine Shared"

If I click OK,

it says something like "Try the installation again using a valid copy of the installation package"sqlsupport.msi"

at this point, it wouldn't let me uninstall nor reinstall..

Any comments would be appreciated. Thank you!

SQL Server installation paths best practices

$
0
0

In my company we're planning to setup a new (consolidated) SQL Server 2012 server (on Windows 2012 R2, VMWare). Current situation is there is a SQL Server 2000, a few SQL Server 2008 Express and a lot of Access databases. For the installation I'm wondering what the best selections for the various installation paths are. Our infra colleagues (offshore) have the following standard partition setup for SQL Server servers:

C:\ OS
E:\ Application
L:\ Logs
S:\ DB
T:\ TEMPDB

And during the installation I have to make a choice for the following

Shared feature directory: x:\Program Files\Microsoft SQL Server\
Shared feature directory (x86): x:\Program Files\Microsoft SQL Server\

Instance root directory (SQL Server, Analysis Services, Reporting Services): x:\Program Files\Microsoft SQL Server\

Database Engine Configuration Data Directories:
Data root directory: x:\Program Files\Microsoft SQL Server\
User database directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
User database log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Backup directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...

Analysis Services Configuration Data Directories:
User database directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
User database log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Temp DB log directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...
Backup directory: x:\Program Files\Microsoft SQL Server\MSSQL11.x\MSSQL\...

Distributed Replay Client:
Working Directory: x:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
Result Directory: x:\Program Files (86)\Microsoft SQL Server\DReplayClient\ResultDir\

So I'd like some on assistance on the filling in the x drive letters. I understand it's best practice to seperate the data files and the logs files. But should that also be the case for TempDB? And should both the database and tempdb log files go to the same log paritition then? What about the backup directories? Any input is very much appreciated!

Btw, I followed the http://www.sqlservercentral.com/blogs/basits-sql-server-tips/2012/06/23/sql-server-2012-installation-guide/ guide for the installation (Test server now).

TempDB autogrowth is full

$
0
0

Hi,

I am running a SQL Server job which is failing now with the error message

"Could not allocate a new page for database 'TEMPDB' because of insufficient disk space in filegroup 'DEFAULT'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. [SQLSTATE 42000] (Error 1101).  The step failed."

Could you please let me know what can be done to resolve this issue, This needs to be resolved as soon as possible because its a Produciton issue. Thanks in advance!

Regards,
Fazlu


Management Studio won't open after evaluation

$
0
0

I installed SQL Server 2012 on my own computer as an evaluation copy to test.  Now we have purchased SQL Server 2012 and have installed it on our network.  I now want to connect to the network server, but when I try to open 2012 Management Studio to connect to it, it just keeps saying my evaluation is expired and directs me to the Microsoft website to purchase.  I didn't think I needed to purchase a license for my PC to connect to the instance on the server.  Do I?  Is there a way to reset this?  Do I have to reinstall Management Studio?

Link to download Sql Server 2012 “Standard Edition”

$
0
0

We have purchased Sql Server 2012 “Standard” edition license. Looking for the link to download of installation software for 2012 “Standard” edition. Have tried a lot but could only found - the “enterprise” evaluation copy.

Looking for urgent help on this. Thanks.

just 4 threads

$
0
0

I have installed SQL Server 2014 BI Edition in a Server that has 16 processors. I have taken a picture of the task manager.

The fact is that if I allow more than 4 as Maximum threads, I'm going to have an error when I process a cube. If I put 4 it works all right. And I think it should be possible to run more threads at the same time. What could I do to Change it?

Upgrade Advisor - Shared report path

$
0
0

I have multiple instances my team of 5 DBAs need to run SQL 2014 Upgrade Advisor on and we would like to all be working off the same set of reports.  We have looked into copying report files to a common directory and exporting to .csv but this adds additional time that would be more productive spent on assessing the reports.

Does anyone know if there is a way to override the default report directory Upgrade Advisor stores reports in? 


Mike

SQL 2008 R2 SP3 unable to discover and patch running SQL instances.

$
0
0

I have a computer running SQL 2008 R2 Developer Edition(Sp2). I am trying to patch with Sp3. However even though the SQL instances are currently running fine and when I run select @@version from an active instance I get the following:

Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
 Jun 28 2012 08:36:30
 Copyright (c) Microsoft Corporation
 Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

However when I attempt to apply SP3 to the server I get the following:

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

SQL Server Setup has encountered the following error:


There are no applicable SQL Server instances to patch. Setup cannot continue.

Error code 0x84B20001.

I run the SQL discovery report from setup and it discovers all the shared components but none of the SQL Engine installs. I need to patch the server. Anyone ever run into this issue. Does anyone know what the discovery report looks at to discover what is installed on the machine?

Thanks in advance....

Viewing all 7701 articles
Browse latest View live




Latest Images