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

SSMS July 2016 doesn't connect to my SQL Server after installing SQL Server 2016 for the first time

$
0
0

I just installed SQL Server 2016 today.  And this installation didn't have any failures.  I checked and all of my SQL Server Services are started now (except for SQL Server Agent): Integration Services 11.0, SQL Server, and SQL Server Browser. I let these services logon as the default account.  The name displayed next to SQL Server on this screen is: "MSSQLSERVER01".  Is this the name of the instance?  But when I type in this name into SSMS 2016, it says

"A network-related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or accessible....Error 53.  The network path was not found."

What does this mean?  I checked and all of my Protocols are enabled.  And I ran all of these with the Administrator account.  

I read some other threads that said July 2016 SSMS is a bad release, but where can I download the other SSMS versions from?


Ryan D


SQL DAC Dedicated Admin connection port 1434

$
0
0

Hi There

For SQL server, is there a way to assign a non-default port no for DAC (default 1434) for security? How?

Please shed some light on this.

thanks & regards,

Irene

Change collation from sql_latin1_general_cp1_ci_as to latin1_general_ci_as

$
0
0

Hi All,

We  performed installation of named SQL Server 2008R2 instance. During the setup instead of configuring latin1_general_ci_as, the defualt collation sql_latin1_general_cp1_ci_as was selected . Now i want to modify the server collation to latin1_general_ci_as. Is it possible without a reinstall. 

I see couple of blogs, where rebuild is suggested and in few other blogs trace flag is used T4022,T3659. Will it work in my case . 

can i modify from sql_latin1_general_cp1_ci_as to latin1_general_ci_as.

Thanks

Udhayan



SQL Server 2008 R2 installation set up in Windows 10 OS - XML document error

$
0
0

I am trying to install Microsoft SQL Server 2008R2 in Windows 10 Operating System.

After the initial steps, I see this error, when I get into the main part of the installation:

--------------------------------

TITLE: SQL Server Setup failure

SQL Server Setup has encountered the following error:

There was an error generating the XML document.

Error code 0x84B10001.

--------------------------------

I have installed service pack 3 for SQL Server 2008 R2 already, and have also installed Cumulative Update package 5 for SQL Server 2008 R2.

Is there any quick solution you can provide me ? I need to sort this out ASAP.

sql 2016 enterprise edition Installation Error ( Error KB2919355)

$
0
0

Good evening all,

Im trying to install SQL 2016 enterprise edition on windows 2012 r2 datacenter.

though i followed all the steps and installed all the prerequisites i'm getting below error.

(Error KB2919355)

even after restarting server and trying to install but same error:

steps i followed downloaded and installed belolw.

1. Clearcompressionflag.exe38 KB

2. Windows8.1-KB2919355-x64.msu690.8 MB
3. Windows8.1-KB2932046-x64.msu48.0 MB
4. Windows8.1-KB2959977-x64.msu2.8 MB
5. Windows8.1-KB2937592-x64.msu303 KB
6. Windows8.1-KB2938439-x64.msu19.6 MB
7. Windows8.1-KB2934018-x64.msu126.4 MB

Thanks,

Vijay

Upgrade from Sql Server Entreprise to Evaluation edition, it is possible?

$
0
0

I'm having some trouble upgrading from an Entreprise edition of Sql Server 2008 R2 SP2 to an Evaluation of Sql Server 2014 SP1, and I begin to wonder if it is possible? I didn't found anything about it in the supported version and edition upgrade guide :

https://technet.microsoft.com/en-us/library/ms143393(v=sql.120).aspx

It says that you can't migrate from SQL Server 2014 Entreprise to Evaluation, but it says nothing about previous editions.

Thanks.

Transaction getting aborted on migration to SQL 2008 R2

$
0
0

Hi,

We have recently migrated from SQL 2005 -> SQL 2008 R2 and are facing issue with transactions getting rolled back on its own. When the SQL queries are getting processed from .net code, there are some DataReaders used to perform selects from database. In code [ legacy code], these data readers were kept OPEN and not closed explicitly. [.net 2.0]. This thing was not giving any issue with SQL 2005 and transactions were getting committed without any problem.

However, when we migrated to 2008 R2, the transactions are getting aborted abruptly. So, we figured it's because of the open datareaders. When we closed these, the problem got solved. However, there are few instances where transactions are still getting aborted.

Are there any fixes / patches rolled out for this? Please note that this issue was not happening with 2005 SQL. We have also checked MSDTC settings on both APP and SQL server and these look good.

Please help!

Unable to install Sql Server 2012 on Windows Server 2012 for SharePoint Reports

$
0
0

Hi all,

I have been trying to install Reporting components from SQL Server 2012 in SharePoint Server 2013 runs on Windows Server 2012 as we have separate database server for SharePoint Server. I have been unsuccessful to install the Reporting components, I get this below error message,

Your help is much appreciated.

Thanks.


SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified

$
0
0

Hi, Here is the brief outline of my problem.
SQLDC is a SQL server  R2 dommain controller.
SQLA and SQLB are SQL server 2008 R2 members on which I installed SQL server 2012.
SQLA has a default database TESTDbA and an instance SQLA\INSTANCEDbA
SQLB has a default database TESTDbB and an instance SQLB\INSTANCEDbB
From Explorer Object of SQL Server Management Studio of SQLA, I can access to TESTDbA,
SQLA\INSTANCEDbA and TESTDbB but not to SQLB\INSTANCEDbB.
I tried many variations.  Even when - I prefixed the server/instance name with tcp
(tcp:SQLB\INSTANCEDbB): and when I specified TCP/IP 
for the network protocol in the connection properties dialog (tcp:SQLB,49226) - yielded the same error.
What else to do in order to troubleshoot this issue?




Upgrade fails: "SQL Server 2008 R2 Feature Upgrade"

$
0
0

Shouldn't I be able to upgrade to 2008 R2?

Current version:

Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64)   Mar 29 2009 10:11:52   Copyright (c) 1988-2008 Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

SQL Server Express 2014 on Win8.1: Could not find the Database Engine startup handle

$
0
0

Hello,

I tried to follow all the similarly titled posts in this forum, yet no solution seems to work, so I hope I can find some up-to-date suggestion here (most of the older posts refer to versions from 2008 to 2012...).

I have installed Visual Studio 2013 (with the latest Update 2 RC) on a freshly installed development workstation with Win 8.1 with all its updates. Now I'd want to install SQL Server 2014 Express, but the setup keeps failing with the dreaded "Could not find the Database Engine startup handle" error (the log follows below).

What I tried:

1) download again and repair. Same error.

2) completely uninstall by launching setup.exe /Action=uninstall (success), then rebooting the OS, then installing again. Same error. I did this twice, the second time I also manually removed any directory left out in C:\Program Files etc.

When I launch the setup, I select all the components for installation in the package SQLEXPRADV_x64_ENU.exe (1.12 GB, last downloaded today -Apr 3, 2014-), and accept all the defaults including the proposed services accounts. There is no preexisting SQL Server instance, as expected.

The setup takes its time, and finally fails with the error quoted above. I really do not want to reformat my HD and fully reconfigure my workstation, which took about 3 days... Could anyone suggest a solution to have SQL Server 2014 setup so I can start developing instead of wasting time in administering the system?

Thanks to all! The log follows.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893607
  Start time:                    2014-04-03 18:30:58
  End time:                      2014-04-03 19:04:41
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  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 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:                  DIOMEDES
  Machine processor count:       4
  OS version:                    Windows 8
  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:\Users\Daniele\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:                  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:                    true
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
  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:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DIOMEDES\Daniele
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\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:                       Reporting Services - Native
  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  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:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       Full-Text and Semantic Extractions for Search
  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Server Replication
  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, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0019
  Error description:             Could not find the Database Engine startup handle.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Documentation Components
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       LocalDB
  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\20140403_183057\SystemConfigurationCheck_Report.htm

LocalDB - Create & Connect To Database >> Programmatically

$
0
0
I need to be able to create & connect to temporary databases programmatically, and NOT using the command-line, within a C# program. How would one go about doing this?

Co-Worker Sysprepped a SQL 2014 Box, is this safe for Production

$
0
0

Hey Guys. Have a quick question. I have a fellow engineer here who wanted to set up a SQL server for me for a Skype for Business installation. he did not specifically use the SQL sysprep tool, he just sysprepped the box and renamed the default instance and indicated that it will work fine. After doing some googling, I have found a decent few opinions indicating that this is frowned upon and could cause issues. I am not even remotely a SQL guy but I have experience elsewhere so I'm a bit hesitant to proceed this way.

I wanted to get the opinions of the folks on the SQL board here. Is this safe for production, or is this risking immediate or future issues? Thanks all and please let me know if you need any further info. 

KB3171021 Fails with Code 851A0042

$
0
0

I am trying to install KB3171021 (SQL Server 2014 SP2) on my production SQL box.  It fails with Code 851A0042.

This is the only information in the Event Log: Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft SQL Server 2014 Service Pack 2 (KB3171021).

I have verified the system and SQL server program disk have space on them.

Regards,

Ray

install SSDT for SQL server 2016 to avoid localDB installation

$
0
0
I am trying to download and install SQL 2016 Data tools on a development server which we have already installed SQL server 2016 database engine.

The SSDT download page is here.

https://msdn.microsoft.com/en-us/mt186501

I am not sure how to do the option of Set up an Administrative Install Point
I downloaded on a network share, by remote log in to the server, open the UNC path, and double click the setup file, it gives an error.

Then I tried next option of Download SSDT as an ISO image file.

After mount the ISO, it started to install, and it installs a localdb first without prompt, which I don't want to install, since we already have  a full version of database engine .
Is there a way to choose not to install localDB?
Thanks,
                

SQLFriend


[SOLVED] KB3171021 Fails with Code 851A0042

$
0
0

I am trying to install KB3171021 (SQL Server 2014 SP2) on my production SQL box.  It fails with Code 851A0042.

This is the only information in the Event Log: Installation Failure: Windows failed to install the following update with error 0x80070643: Microsoft SQL Server 2014 Service Pack 2 (KB3171021).

I have verified the system and SQL server program disk have space on them.

Regards,

Ray


Have installed SQL Server Management Studio (Missing Microsoft Analysis Services Client Tools)

$
0
0

We have installed the SQL Server 2008r2

When we go in to Microsoft SQL Server Management Studio

It lists that we have everything installed but Microsoft Analysis Services Client Tools 10.50.1617.0 is missing

Here is what I have installed

Microsoft SQL Server Management Studio 10.50.1617.0

Microsoft Data Access Components (MDAC) 6.1.7601.17514

Microsoft Internet Explorer 9.0.8112.16421

Microsoft .NET Framework 2.0.50727.5456

Operating System 6.1.76.01

where can I find Microsoft Analysis Services Client Tools 10.50.1617.0 to add since it is needed for some projects.

Thanks for the help

      Corey

Installing SQL Server 2014 on Windows server 2016

$
0
0
We are planning to setup an environment installing SQL Server 2014 on Windows server 2016 RTM. It will have Windows clustering with AG. Looking for any known issues to be considered before setting up the enviroment.

Converting SQL 2012 Eval to Developer Edition

$
0
0

I have an expired eval installation of SQL Server 2012 that I am trying to upgrade to SQL 2014 Developer Edition. The SQL service will not start because the evaluation has expired so the update fails. I found the following article which looks like it will address the issue but when I run the command I get an error.

https://support.microsoft.com/en-us/kb/2020443

The error message says "The system cannot find the file specified" I did follow the instructions to run the command from the folder that the setup file is located in. I copied and pasted the command but I'm not sure if I needed to provide a value for <AppropriatePID>. If I need to add the AppropriatePID to the command where can I find the value to insert?

Installation Error SQL SERVER 2016

$
0
0

 Microsoft SQL Server 2016 Setup

The following error has occurred:

Unable to open Windows Installer file 'D:\en_sql_server_2016_enterprise_x64_dvd_8701793\redist\VisualStudioShell\VC10SP1\x64\vc_red.msi'.

Windows Installer error message: 1: 2203 2: D:\en_sql_server_2016_enterprise_x64_dvd_8701793\redist\VisualStudioShell\VC10SP1\x64\vc_red.msi 3: -2147286960 .

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

Viewing all 7724 articles
Browse latest View live


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