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

[Pre-Login] initialization=19286; handshake=16099; SQL 2017 CU14

$
0
0

Hey I got a simple HA/AG SQL 2017 on the latest CU14.

I am trying to copy users from the primary to the secondary and it all works well on port 1433.

I can enable/disable the firewall and the script works as expected.

The problem is that when the 1433 TCP Port is changed to another port, the script fails whenever the firewall is enabled on the intended destination. If I disable the FW, it just works.

So i tried open ports 5022, and 49000-51000, same fail, multiple reboots, applying SQLAgent and ..CEIP.. to the firewall allowed communitaction - all fails. Process monitor does not tell me what is blocked and reports the expected ports and applications are responding as intended and succeded. 

In Powershell I used the same script, zero modifications.

My Script fails when it runs 

Invoke-Sqlcmd -Query $Query -ServerInstance 10.10.15.204

The exact failure message is

 

Invoke-Sqlcmd : Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=19286; handshake=16099; 

At C:\scripts\powershell.ps1:344 char:17
+ ...              Invoke-Sqlcmd -Query $Query -ServerInstance 10.10.15.204
+                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Invoke-Sqlcmd], SqlException
    + FullyQualifiedErrorId : SqlExectionError,Microsoft.SqlServer.Management.PowerShell.GetScriptCommand

Invoke-Sqlcmd : 
At C:\scripts\powershell.ps1:344 char:17
+ ...              Invoke-Sqlcmd -Query $Query -ServerInstance 10.10.15.204
+                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ParserError: (:) [Invoke-Sqlcmd], ParserException
    + FullyQualifiedErrorId : ExecutionFailureException,Microsoft.SqlServer.Management.PowerShell.GetScriptCommand

What Do I Do?



SQL Server 2012 Installation

$
0
0

Can i install SQL Server 2012 +Dynamic Navision 2009 on Windows server 2019?

 

Unqualified Join(s) detected

$
0
0

Hi,

We are going to upgrade SQL Server from 2008 to 2017. We ran DMA tool and found some reports on some topics. Among them one topic they are saying currently database has unqualified join which use old style join rather than using ANSI new join syntax (LEFT/RIGHT OUTER join, FULL OUTER join etc). Below is DMS report output. I want to know does  SQL Server still support old style join or I must use ANSI new join syntax (LEFT/RIGHT OUTER join, FULL OUTER join etc)?

Issue-

Unqualified Join(s) detected



Impacted Object Details

Object [dbo].[abc_procedure] uses the old style join syntax which can have poor performance at database compatibility level 90 and higher.

Return code 84c40032 when installing SQL Server 2017 Express Advanced

$
0
0

I'm writing an InstallShield installation to install SQL Server 2017 Express Advanced with Tools, and it fails.  When looking at the InstallShield log file, the SQL return code shows 84c40032.

I can't find the SQL Server page that lists the return codes and what they mean.  Can someone tell me or point me to a web page where the codes are listed?

Thanks.



SQL 2008 SP3, compatibility with 2008 R2 SP1

$
0
0

I am looking at patching a Server 2008 R2 server with SP1, as it does not accept modern patches without the SP. It has a SQL 2008 SP3 install. I looked at the SQL 2008 SPs, checking for any compatibility for 2008 R2 SP1. None of them mention 2008 R2 SP1, they only mention the non SP1 variant, even though they were released at similar times to Windows SP1.

Are there any compatibility issues when Applying 2008 R2 SP1, to SQL 2008 SP3 installs?

Does 2016 SQL developers edition have the ability to create SQL AG? What about 2014 SQL developers edition?

$
0
0

Does 2016 SQL developers edition have the ability to create SQL AG?   

Can 2014 SQL developers edition create SQL AG?   Can developers edition create SQL failover clusters?

XXXXXXXXXXXXXXXXXXXX

Also below:

2016 SQL standard shows NO for "always-on availability groups" but YES for "always-on failover clusters"?  What is the difference between these two HA technologies?

Is always-on failover clusters just a new term for the traditional single storage cluster used for HA prior to AG which had failover instances??

https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2016?view=sql-server-2017


dsk


SQL Server Management Studio 18 wont load

$
0
0
I recently downloaded and installed SSMS 18. After the install, when I click on the SSMS icon, it shows the splash screen, but does not load. Any help would be appreciated.

error in java


Microsoft SQL Server 2008 version -End of Support

$
0
0

Dear Sir,

As you know Microsoft is going to stop support for SQL server 2008. Due to budget constraint my company don't want to Upgrade SQl server version soon. Is there any problem in using SQL server 2008 after July?

Regards,

Deepak

INSTALLING sqlcmd for using Node.js problem

$
0
0

hello, im following this instruction from microsoft Create Node.js with sql server

step 1.1 and 1.2 no problems.

step 1.3 installing sqlcmd is making problems

SQLCMD is a command line tool that enables you to connect to SQL Server and run queries.

  1. Installed successfully the OBDC DRIVER.
  2. Installed successfully the SQL Server Command Line Utilities. 
  3. There is a problem: After installing SQLCMD, you should  connect to SQL Server using the following command from a CMD session but i cant... :
  4.  sqlcmd -S localhost -U sa -P your_password
  1. This are errors i got 
C:\>sqlcmd -S localhost -U sa -P your_password
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Named Pipes Provider: Could not open a connection to SQL Server [2]. .
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
  1.  i go to services w-key+R-->services.msc-->SQL Server (SQLEXPRESS) is running. SQL Server VSS Writer restarted. 
  2. sql server configuration manager-->sql server network configuration -->ENABLE named/pipes and tcp/ip protocols.
  3. Still got the problem even if i simply type sqlcmd inside cmd.
  4. CMD is started with administrator privileges all the time.

r

Regards, Mario

Facing issues while installing SQl 2012 in windows 10 64 bits

$
0
0

Hello All,

I'm facing an issue for a long time while installing SQL 2012 in my PC. I'm using windows 10 64 bits.

I've tried everything available to get rid of this issue but unfortunately not finding any solution that can work. Please help me out.

TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------

The following error has occurred:

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 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.3128.0&EvtType=0xDF039760%25401201%25401

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

OK
------------------------------
TITLE: Microsoft SQL Server 2012 Service Pack 1 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,version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80073712. 
Windows Installer file: c:\8be809e40f05ddc2106edb86\1033_ENU_LP\redist\VisualStudioShell\SMO\SharedManagementObjects.msi
Windows Installer log file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190531_210025\VSSMO_Cpu32_1.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.3128.0&EvtType=0xDC80C325

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

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

 

SQL Server 2016 SP2 CUs fail after CU4 applied

$
0
0

I have applied SQL Server 2016 SP2 CU4 (13.0.5233.0), when I try to apply CU5 or CU7 now it fails, the error seems to be it is not seeing the proper install version. If I search the registry I see the proper version and if I run @@version it sees the proper version

select @@version

Microsoft SQL Server 2016 (SP2-CU4) (KB4464106) - 13.0.5233.0 (X64)  

Nov  3 2018 00 :01:54   Copyright (c) Microsoft Corporation  Enterprise

Edition:Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)

The Error from the install is this;

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Common Files
  Component error code:          1642
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190529_130437\MSSQLSERVER\sql_common_core_Cpu64_1.log
  Error description:             The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.

  Feature:                       Integration Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Common Files
  Component error code:          1642
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190529_130437\MSSQLSERVER\sql_common_core_Cpu64_1.log
  Error description:             The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.

Any help would be appreciated

Help with sql express 2017 not installing

$
0
0
TITLE: Microsoft SQL Server 2017 Setup
------------------------------

The following error has occurred:

PerfLib 2.0 counter removal failed with exit code 2. Command line: C:\WINDOWS\system32\unlodctr.exe /m:hkengperfctr.xml from directory C:\Program Files\Microsoft SQL Server\140\Shared\.

For help, click: https://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x590D6427%25400x24BDAA65%25401260%25401

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

OK
------------------------------
Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052377
  Start time:                    2019-05-31 03:24:03
  End time:                      2019-05-31 03:28:55
  Requested action:              Install

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


Machine Properties:
  Machine name:                  JAYSWORKLAPTOP
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Pro (10.0.17763)
  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
  SQL Server 2017                                                          Client Tools Connectivity               1033                                      14.0.1000.169   No         Yes      
  SQL Server 2017                                                          Client Tools Backwards Compatibility    1033                                      14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Client Tools SDK                        1033                                      14.0.1000.169   No        Yes       

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

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 NT Service\MSSQLLaunchpad$SQLEXPRESS
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE, REPLICATION, ADVANCEDANALYTICS, SQL_INST_MR, SQL_INST_MPY, FULLTEXT, CONN, BC
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     true
  IACCEPTROPENLICENSETERMS:      true
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Jaysworklaptop\Administrator
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            1
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\ConfigurationFile.ini

Detailed results:
  Feature:                       Full-Text and Semantic Extractions for Search
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       Python
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       R
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       Machine Learning Services (In-Database)
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       Database Engine Services
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Server Replication
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Browser
  Status:                        Failed
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Browser
  Component error code:          0x84C6CB27
  Error description:             SQL Server Browser configuration for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' was cancelled by user after a previous installation failure. The last attempted step: Retrieving full path to the SQL Server Browser service executable using Windows Installer API for the SQL Server Browser component with ID '{2E86FD41-C179-456E-8E6A-5157ED427228}'..
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x8510C01B%400x31BA4472%401222%4052007&EvtType=0x8510C01B%400x31BA4472%401222%4052007

  Feature:                       Client Tools Connectivity
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Common Files
  Component error code:          0x84BB0001
  Error description:             The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Common Files
  Component error code:          0x84BB0001
  Error description:             The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190531_032402\SystemConfigurationCheck_Report.htm

Move SQL server 2017 database to another drive

$
0
0

hello

I'm looking to move an SQL 2017 database to another drive. A software company has installed a package that required SQL, we setup the SQL server and then the software company installed the package creating two new databases rather than use the two we prepared for them.

The issue is that they created both databases on the same drive rather than separate the databases on the two drives we had prepared. Looking at moving the database it is recommended to use  ALTER DATABASE and herein lies my issue.

They created a user database files for each database with the same name, database1.mdf / database1.ndf and  database2.mdf / database2.ndf,

How do i use MODIFY FILE when both the mdf and ndf files have the same name 'database2', if we were creating user files we would normally differentiate the file names such as database2.mdf and database2_user.ndf then use

ALTER DATABASE database2   
    MODIFY FILE ( NAME = database2   
                  FILENAME = 'G:\MSSQL\Data\database2.mdf'); 

ALTER DATABASE database2   
    MODIFY FILE ( NAME = database2_user   
                  FILENAME = 'G:\MSSQL\Data\database2_user.ndf'); 

how do you move the database files when both have the same filename?

SQL Server Core Licensing Setup on Virtual Server

$
0
0

Hi Everyone, I have a question on the SQL server licensing (per Core).

What I have at the moment is 4 x SQL Server License (2 Core Pack) , which means a total of 8 core license.

Our environment:
- The SQL server is a VM on VMware ESX 6.5.
- The VM is a part of a cluster resource consists of many ESX hosts.
- Hyperthreading is enabled.

As i understand, the number of SQL cores license = number of vCPU. Please correct me if i'm wrong.  
If above understanding is correct, my next question is; on the Edit Settings on the VM, shall I;

1) Option A. 
- Set the CPU to 8. (I believe we are referring to vCPU here).
- Set the number of cores per socket to 8.

In , above should give us 1 socket and 8 cores to the VM.

2) Option B.
- Set the CPU to 8.
- Set the number of cores per socket to 4.

In summary, above should give us 2 socket and 8 cores to the VM.

3) Option B.
- Set the CPU to 8.
- Set the number of cores per socket to 2.

Above should give us 4 socket and 4 cores to the VM.

4) Option B.
- Set the CPU to 8.
- Set the number of cores per socket to 1.

Above should give us 8 socket and 8 cores to the VM.

Question:
Will all 4 options above satisfy the SQL Server 8 cores licensing that I have?
If yes, what are the advantage and disadvantages of each options.
Which one is the best option?



User Trace disappears on SQl Server 2012 SP4

$
0
0

Hi,

           

I have created an user trace using "SP_TRACE_CREATE" and added some events using "SP_TRACE_SETEVENT" and started the trace using "SP_TRACE_SETSTATUS". I was able to see my trace with Traceid "2" with status "1" when I query "select * from sys.traces"

  I have done this on 3 separate SQL Servers and after some time, I don't see the user trace I've created on two of the servers. I've did this 3 to 4 times and it happens every time, trace appears for some time and then gone, only "system trace" with traceid 1 is visible.

 Is there something I'm doing wrong or any ideas as to why this happens?

Thank you so much in advance.

SG

  

Unable to enable SeBackupPrivilege SeDebugPrivilege SeSecurityPrivilege windows 10 to install an application dependant on SQL 2012 Express

$
0
0

Working for over 4 weeks, Windows 10, to install an application which is dependant on SQL 2012 Express which automates a customized SQL 2012 Express in Windows 10.

If I install SQL 2012 Express directly as administrator, it completes the install.

However, when I install SQL 2012 Express indirectly using the application, the command line driven SQL 2012 Express installation never completes.
SQL 2012 Express always fails with an error log states to complete the installation of SQL 2012 Express before continuing.

I finally found this webpage; https://support.microsoft.com/en-us/help/2000257/sql-server-installation-fail-if-setup-account-not-have-some-user-right, stating that the SeBackupPrivilege, SeDebugPrivilege and SeSecurityPrivilege must all be enabled.

Yet, though I am the ONLY user for windows 10 (either an upgraded version of Windows 7 Pro 64-bit or a clean Windows 10 install), the default administrator (S-1-5-21-1640373479-2815045965-3870623452-500)
a whoami.exe /priv inquiry reports that the SeBackupPrivilege, SeDebugPrivilege and SeSecurityPrivilege are all disabled; 
presumably the reason for the consistent failure.

For two days of searching many potential options, I have been unable to find a method the enable these 3 privileges to see if the SQL 2012 Express dependant application will install.

Suggestions?

(BUG found) Command Line Install Fails using /SQLTEMPDBFILESIZE and /SQLTEMPDBDIR paramaters

$
0
0

It appears that there is a bug on the new parameter /SQLTEMPDBFILESIZE introduced in SQL 2016. I am using the /SQLTEMPDBDIR parameter to specify a mount point setup just for TempDB (128GB) which is much larger than the system databases default directory volume (30GB). The issue that I'm seeing is that when I specify a size for my TempDB files that is larger than the volume that the "system databases directory" resides on the installation fails stating there is not enough space on the path of where the tempdb files default to in the "system databases directory" despite that I'm specifying them to go to a completely different path on a larger volume. I have confirmed this behavior by choosing a smaller combined file size less than 30GB that allows the tempdb data files  and the installation completes successfully and the tempdb data files go to the correct tempdb mount point.

What I believe is happening is the sql installation is putting the default tempdb data file in the system database folder where it goes by default and it is growing the file before moving it to the correct directory specified in the install config parameters.

I have not tested to see if this behavior is an issue with 2017 or 2019, but I will test soon and follow up.

##Details from the summary bootstrap log file which shows the wrong behavior.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2146232060
  Start time:                    2019-06-03 16:30:14
  End time:                      2019-06-03 16:33:42
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  vm-sqlserver1
  Machine processor count:       2
  OS version:                    Microsoft Windows Server 2016 Datacenter (10.0.14393)
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered  Configured

Package properties:
  Description:                   Microsoft SQL Server 2016 
  ProductName:                   SQL Server 2016
  Type:                          RTM
  Version:                       13
  Installation location:         C:\temp\SQLBuild\Media\SQL2016\x64\setup\
  Installation edition:          Developer

  Slipstream:                    True
  SP Level                       2
  Patch Level:                   13.2.5337.0

Product Update Status:
  Success: KB 4052908, KB 4495256

Product Updates Selected for Installation:
  Title:                         Microsoft SQL Server 2016  with SP2
  Knowledge Based Article:       KB 4052908
  Version:                       13.2.5026.0
  Architecture:                  x64
  Language:                      1033

  Title:                         SQL Server update
  Knowledge Based Article:       KB 4495256
  Version:                       13.2.5337.0
  Architecture:                  x64
  Language:                      All

  Update Source:                 Slipstream

......

##Config options in same summary log file showing correct path and size option passed to the install.

  SQLTEMPDBDIR:                  S:\TempDb\D1\DATA
  SQLTEMPDBFILECOUNT:            2
  SQLTEMPDBFILEGROWTH:           0
  SQLTEMPDBFILESIZE:             32996
  SQLTEMPDBLOGDIR:               S:\Data\L1\DATA
  SQLTEMPDBLOGFILEGROWTH:        512
  SQLTEMPDBLOGFILESIZE:          512

##See the error below which specifies the wrong path for the tempdb data file.

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x80131904
  Error description:             MODIFY FILE encountered operating system error 112(There is not enough space on the disk.) while attempting to expand the physical file 'S:\MSSQL\MSSQL13.SQLSERVER2016\MSSQL\DATA\tempdb.mdf'.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.5337.0&EvtType=0x7590AFD6%400x9A41B222&EvtType=0x7590AFD6%400x9A41B222


Can I use SQL Server developer edition for backup testing?

$
0
0

I have some scripts that tests database backups by restoring them and then running integrity checks against them.

Will I be able to use developer edition without violating the license terms, or should opt for a paid license?

SQL Server 2017 and supported memory

$
0
0

Hi,

I have several questions regarding memory usage/configuration for the SQL Server Standard 2017

1. Editions and supported features of SQL Server 2017 article mentions 128 GB as one of the limit

Is it possible to install SQL Server 2017 with Standard server license on the machine that has more than 128 GB of memory?

2. If  "Yes" for q1, and we install two instances of SQL server 2017 Standard on the machine with 256 GB of memory will each of them have memory usage 128GB limit ?

Thank you

Viewing all 5760 articles
Browse latest View live


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