Dear Team,

I can't find SQL key from VLSC site.. what could be the reason? noting I have purchased a licensed edition

Thanks

For over a year I have not been able to install sqlserver on my system. I spent months and 70+ hours trying to fix this to no avail. It started with SCCM; after uninstalling it improperly I was left with junk in the system, and no longer able to install subsequent installations of sql. Even after dist-upgrades, given there are over 11,000 registry keys buried in the system, its hard to clean up. I just fixed my problem and managed to install it for the first time in a year. Simple process... you will need two things. 1. Windows Installer Clean up, (I just found out after the fact a new one was released last month, but I used the ancient one which worked successfully) and you will need 2. "Revo Uninstaller 4.0." There are multiple approaches. My version Microsoft SQL 2008 Server Express Edition

Here is how I did it!

1. I tried to install it, it failed.

2. Before closing/rolling back installation, I opened "Windows Installer Clean up" to confirm installation entries had been reported. They were there. Seeing that SQL uninstaller doesn't do its job right, Iopen task manager and kill the setup-installer rather than letting it roll itself back. 

3. I opened revo-uninstaller, highlighted SQL entries and prepared to do an advanced uninstall/removal. This searches for leftovers the native uninstaller conveniently misses.

4. I initiated "Windows installer clean up" on all SQL entries at about the same time as I initiated an advanced uninstall with revo, so one wouldn't plausibly gut whatever the other one needs to do its job before its too late; ok kind of nutty, but you can combine this in various ways until it works for you, if it doesn't the first time. It worked for me first go. 

It may be wise to Install SQL with Revo Uninstaller first, crash the failed setup, then run "Windows installer clean up", and THEN do the Revo Log based clean up.

5. Windows installer clean up won the race and left behind much if not all of the files on the hard drive, but probably worked most of its magic in the registry. 

6. Revo-Uninstaller completed and cleaned up whatever junk was left on the hard-drive, there were next to no registry entries reported left behind.

7. I tried installing sql-sever again, this time with Revo, VIA "Install ProgramWith Revo-Uninstaller", think of this as "Process Monitor" for installations. I could have done that the first time, but none the less, this worked.  This time SQL installed without a hitch for the first time in a year after dozens and dozens of previous attempts. PLUS Revo has detected over 12,125 registry keys and logged everything necessary to clean it up absolutely 100%; user rights and all...

You can copy and repeat with whatever versions you believe you have installed previously to ensure you get every last bit of junk out of there. This basically overrides what was already on there before but gives you a convenient log that automates the process of removal for a later time.  I recommend, then, using SQL's built in uninstaller, to remove itself PROPERLY this time, this way post installation changes may be reverted as well. THEN run the Revo-Uninstaller's Advanced Uninstall, THEN the LOG based removal system after.... Then, and or at the same time, run "Windows Install Clean Up" to be sure its dead.

PS. I just did a dist-upgrade to windows 10 from 7, this may be very helpful, as I noted it, or possibly DISM, over time, cleaned up and defaulted some user rights permissions I had changed in GPO in windows 7 that may have caused some issues as well.

I hope this saves you a whole lot of troubles!

Ok, have a brand new clean Windows 10 Pro VM deployed in Azure. I turned on IIS, and then attempted to install SQL server. Nothing else has run on this system. Installation fails with:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I attempted to start the SQL service, but it was unable to. I did a restart and tried to start it again, no luck.

Summary File:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068119551
  Start time:                    2019-02-06 03:04:51
  End time:                      2019-02-06 03:14:49
  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.


Machine Properties:
  Machine name:                  Bates
  Machine processor count:       2
  OS version:                    Microsoft Windows 10 Pro (10.0.17134)
  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:\SQLServer2016Media\Express_ENU\x64\setup\
  Installation edition:          Express

  Slipstream:                    True
  SP Level                       2

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

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>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190206_030443\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              true
  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
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  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:                         true
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Bates\818bates
  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:                 false
  UpdateSource:                  Slipstream
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20190206_030443\ConfigurationFile.ini

Detailed results:
  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:          0x84BB0001
  Error description:             A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.5026.0&EvtType=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

  Feature:                       SQL Browser
  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\130\Setup Bootstrap\Log\20190206_030443\SystemConfigurationCheck_Report.htm

Thanks all for taking a look.

I have a 2 Node Cluster with 4 instances. 

2 of the instances were created on Server A, which was installed incorrectly. 

The shared features were installed on drive c instead of drive d. 

The instances that were installed on it are now having issues because they cannot failover to Server B because of the shared features.

Would it be possible to fix the issue by remove Server A from the cluster, add a back with a good instance created on Server B, and repair the 2 instances that were created on Server A?

i got error while installing ms sql server 2008 r2 .

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

SQL Server Setup has encountered the following error:

The collation Indic_General_90_CI_AS was not found.

Error code 0x84B40000.

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

OK

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

how i can resolve this error

Hi!

I have been trying to set up a SQL Server DB locally, mainly for practice dealing with Windows Server, however I have been stuck for the past day. Every time I try and run the setup from Powershell I am met with an error regarding Invalid URI, I don't understand what triggers such an error.

Image of error: https://i.imgur.com/JefvvJ2.png

The setup command I am trying to use, the hostname is Server1, but I am not confident that Server1\Administrator is accurate here.

.\SQLSetup.exe /qs /ACTION=Install /FEATURES=SQLEngine /INSTANCENAME=MSSQLSERVER /SQLSVACCOUNT="Server1\Administrator" /INSTANCENAME="SQLEXPRESS" /SQLSYSADMINACCOUNTS="Server1\Administrator" /AGTSVACCOUNT="Server1\Administrator" /SECURITYMODE=SQL /SAPWD="MySecretPassword" /TCPENABLED=1 /IACCEPTSQLSERVERLICENSETERM

I made a thread here initially: https://social.technet.microsoft.com/Forums/en-US/a6fe9327-ed06-44cc-94f2-8ae94b71d15b/need-help-installing-sql-server?forum=winservercore

Thanks in advance!

In LINUX, this command correctly sets memory, but i do not see it reflected when running SSMS  sp_configure even after a SQL restart.  Is there an additional step to flush something so SSMS sp_configure shows the correct max memory value?  I am running SQL Server 2019 CTP 2.2 on LINUX RHEL 7.6.

sudo /opt/mssql/bin/mssql-confset memory.memorylimitmb 12288

We are in need to do an in-place upgrade of our current sql server from windows server 2008r2 std and sql 2008r2 std to windows server 2016 and sql 2016.

I know this will be a multi process upgrade however I am getting conflicting information on the upgrade steps. Can someone tell me the proper upgrade path in order to keep the system working during all steps?

Hi,

when I try to run the Setup for SQL Server 2017 under Windows 10 1809 from commandline with the following command a exception appears.

.\SQLServer2017-SSEI-Expr.exe /?

The exception is:

Unhandled Exception: System.ArgumentNullException: String reference not set to an instance of a String.
   at System.Reflection.RuntimeAssembly.GetResource(RuntimeAssembly assembly, String resourceName, UInt64& length, StackCrawlMarkHandle stackMark, Boolean skipSecurityCheck)
   at System.Reflection.RuntimeAssembly.GetManifestResourceStream(String name, StackCrawlMark& stackMark, Boolean skipSecurityCheck)
   at System.Reflection.RuntimeAssembly.GetManifestResourceStream(String name)
   at Microsoft.Sql.Installer.Engine.ManifestCache.GetManifestFromResource(String resourceName)
   at Microsoft.Sql.Installer.Engine.ManifestCache.InitializeDownloadManifest(String edition)
   at Microsoft.Sql.Installer.Engine.ManifestCache.Initialize(String edition, Boolean skipBootstrapInitialization)
   at Microsoft.Sql.Installer.UI.SSEIBusinessLogic.Initialize(String edition)
   at Microsoft.Sql.Installer.UI.App.AppInitialize(String[] args, String edition)
   at Microsoft.Sql.Installer.UI.App.App_OnStartup(Object sender, StartupEventArgs e)
   at System.Windows.Application.OnStartup(StartupEventArgs e)
   at System.Windows.Application.<.ctor>b__1_0(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at Microsoft.Sql.Installer.UI.App.Main()

The error does not occur under Windows 10 1803 with an older .NET Framework installed.

Please help, I need a silent and unattended installation with automated download and extraction from the 5MB Online-Installer.

Thanks.

1. Is there any mandatory hotfixes exists for SQL Server 2000 running on SP4?
2. How do we know and where can we find if any mandatory patch or hotfixe exists for SQL Server 2000, 2005 and 2008?
3. I have collected the detail across the web, is that below details correct?

Has anybody every seen missing 'Startup Parameters' property of SQL Service in SSCM (Windows Server 2008 R2)?

It should look like this:

Why would 'Startup Parameters' property be missing and how do I resolve ?

Thanks in advance,

Phil Streiff, MCDBA, MCITP, MCSA

Is it possible to remigrate a DB to an older version if the original DB existed on an even older version?

We have a DB that was migrated from 2008r2 to SQL17, and it turns out that the product is unsupported on SQL that new, and we were told host it on SQL14. 

Is it possible to go from 2008r2 > SQL`17 > SQL 14?

Even easier if we could restore it on the same box after i uninstalled SQL 17 and reinstalled SQL 14. 

Dear All,

I am looking for the SQL Server 2012 Developer edition. I have searched lot of portals and websites but couldn't able to get. Can some one help me in finding the setup files or share the setup if any one of you have.

Thanks in advance.

Sathish.K

Hi,

I discovered that SQL 2017 standard not have a product key. The key is into the ISO installer.

So I installed an SQL trial version in a production host waiting to receive the product key.

Now I must change to licensed version in an production host  that can't be stopped for more of 10 minutes.

How can solve this problem? Remove and Install it is a long time.

If I install the licensed version over the trial with a setup as "repair" can I solve? There is a repair setup? And the repair change to license version the SQL?

Or what can I do?

Thank you

Giuseppe

If i buy SQL Server standard Core 2017 today, will i get downgrade rights? If so, then will i get the downgrade rights till SQL Server 2014?

Hello, i want to install SQL Server 2017 on Windows 10 Pro, can i do this with right with Windows 10 License? I found information on License FAQ -> http://download.microsoft.com/download/A/5/9/A599711B-6807-4757-B38D-1EE269F2F19B/FAQs-Product-Licensing.pdf

it says, that i can't use Windows 10 Pro like as server, but here 

https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-2017

for SQL Standard version, Windows 10 Pro is allowed, and they nothing says about licensing

Hi everyone!

  May someone help me to point the difference between those two SQL Server collation?

Latin1_General_CI_AS x SQL_Latin1_General_CP1_CI_AS

Thanks.

Doria

TENGO UN PROBLEMA CON ACTUALIZACIÓN DE WINDOWS AL ACTUALIZAR, ME APARECE EL ERROR D59 

error : -