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

Trying to install SQL Server 2016 Express on Windows 10

$
0
0

I'm trying to install SQL Server 2016 Express 2016 on a new Windows 10 Laptop. I have made sure I have the latest Windows updates installed and the machine is not on any Network but the install process keeps failing. The install error log file is below.

Can anybody please provide any assistance?

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052081
  Start time:                    2016-10-13 19:58:20
  End time:                      2016-10-13 20:00:49
  Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
  Next step for SDK:             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.
  Next step for RS:              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 FullText:        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 Replication:     Use the following information to resolve the error, and then try the setup process again.

Machine Properties:
  Machine name:                  DESKTOP-NNQQPQJ
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Home (10.0.10586)
  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
  SPLevel:                       0
  Installation location:         C:\Users\paul\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>
  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:            
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 NT Service\MSSQLLaunchpad$SQLEXPRESS
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE, REPLICATION, ADVANCEDANALYTICS, FULLTEXT, RS, CONN, BC, SDK
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  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
  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:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  NT Service\ReportServer$SQLEXPRESS
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DESKTOP-NNQQPQJ\paul
  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\130\Setup Bootstrap\Log\20161013_195820\ConfigurationFile.ini
Detailed results:
  Feature:                       Client Tools Connectivity
  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 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
  Feature:                       Client Tools SDK
  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 Batch Parser
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\sql_batchparser_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=sql_batchparser.msi%40PublishProduct%401935%3a0x800736B3
  Feature:                       Client Tools Backwards Compatibility
  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 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
  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, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
  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 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
  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, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
  Feature:                       R Services (In-Database)
  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 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
  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, and then try the setup process again.
  Component name:                SQL Server 2008 Setup Support Files
  Component error code:          1935
  Component log file:            C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x800736B3.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.1711.0&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x800736B3
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161013_195820\SystemConfigurationCheck_Report.htm


TDE ( Encryption ) in SQL Server 2016

$
0
0

Hi ,

i am using sql server 2016 enterprise edition ( evaluation ) , in which i am supposed to use TDE on DB level,

Can you please help me to understand the steps to perform the same on 10 Different User DB's in that instance. 

It would be great if you can share me the informative URLs to understand the concepts 

Thank you 


hemadri

Please help me with the installation of SQL Server 2016

$
0
0
I had a problem while installing sql server 2016 and the error message is " Setup Account Privileges", searched it for solutions and still the same, in my laptop there isn't Local Security Policy in administrator tools but i already run as administrator, please help me fix this problem. my windows is 8.1 Single Language in 64-bit, Thank You

SQL 2016

$
0
0
I am trying to download SQL 2016  from virtual studio and I am unable to do so. I first download the information on a disk but I am not sure where go go from there. Can anyone provide some guidance?

SQL VSS Writer not in list

$
0
0

Hello,

running vssadmin list writers does not show the SQL Server Writer.

SYSTEM is sysadmin (even put in local admin group to test).  under services, the service is running.

SQL Server VSS Writer Service is added to the sysadmin role

ran select ‘#’ + name +’#’ from sys.databases  - no spaces appear

tried to use the administrator account - no luck.

uninstalled sql vss rebooted and then reinstalled sqlwriter.msi  - no luck

running server 2012 R2 in a vmware vm.   SQL 2012 SP3 Std 64bit.    We do have SSL enabled for SQL.

any thoughts?

Thanks in advance.

How to remove Windows server core from PC with command line

$
0
0

Hello ,

I installed the 2016 Windows Server Technical Preview 4 (which is Server Core without GUI), I have access only to command line.

How do I remove the core server installation from my PC with command line?


SQL Server 2016 Developer edition throws "evaluation period has expired" error

$
0
0

Hello,

I have installed an SQL Server 2016 RC 2Developer Edition, but now I get the following error when trying to start the service:

2016-10-14 01:34:31.84 Server      SQL Server evaluation period has expired.

Now I have checked in the installer that I definately chose the Developer edition, so basically this should not happen. Is this a known issue and is there a way of fixing that? I tried running an "Upgrade edition" to Developer again, but this didn't work.

I also have a 2008 Express installation running which I need for a specific program, but that shouldn't really matter.

For those who wish to see the whole error log, here it is:

2016-10-14 01:34:31.84 Server      Microsoft SQL Server 2016 (RC2) - 13.0.1300.275 (X64) 
Mar 26 2016 03:43:12 
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows 10 Pro 6.3 <X64> (Build 14393: )

2016-10-14 01:34:31.84 Server      UTC adjustment: 2:00
2016-10-14 01:34:31.84 Server      (c) Microsoft Corporation.
2016-10-14 01:34:31.84 Server      All rights reserved.
2016-10-14 01:34:31.84 Server      Server process ID is 8784.
2016-10-14 01:34:31.84 Server      System Manufacturer: 'System manufacturer', System Model: 'System Product Name'.
2016-10-14 01:34:31.84 Server      Authentication mode is WINDOWS-ONLY.
2016-10-14 01:34:31.84 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\Log\ERRORLOG'.
2016-10-14 01:34:31.84 Server      The service account is 'NT Service\MSSQL$DEV_TABULAR'. This is an informational message; no user action is required.
2016-10-14 01:34:31.84 Server      Registry startup parameters: 
-d C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL13.DEV_TABULAR\MSSQL\DATA\mastlog.ldf
2016-10-14 01:34:31.84 Server      Command Line Startup Parameters:
-s "DEV_TABULAR"
2016-10-14 01:34:31.84 Server      Error: 17051, Severity: 16, State: 1.
2016-10-14 01:34:31.84 Server      SQL Server evaluation period has expired.
2016-10-14 01:34:31.84 Server      SQL Server shutdown has been initiated


Newbie: I have installed SQL Server 2016 and Management Studio but there is no SQL Server name to choose from

$
0
0

Hi,

I have installed SQL Server 2016 and Management Studio with success but when I try to connect to a Server on SSMS, the combo is empty.
Do I need to start a service manually?  I could only found the SQL Writer service running.

Thanks/Brgds
joao


Windows Internal Database Service Pack 4 (2463332) & Windows SBS 2003 R2

$
0
0

 

RE: Windows SBS 2003 R2 with Windows Internal Database Service Pack 4.

I tried to install Windows Internal Database Service Pack 4 (2463332) as it had been offered by Windows for several months. Seemed to install too quick, but said successfully installed. However, Windows then immediately offers to reinstall it again, i.e., reappears in system tray. Windows update history shows no indication that said service pack was installed.

In doing some research, I thought perhaps that I need to:

1.     Download/run standalone version. Although standalone version appears to be almost 10 times the size of the update offered by Windows; or

 

2.     Stop SQL Server before running Windows update.

 

Any help guidance would be appreciated as my knowledge is somewhat limited and next course of action is to contact our firm’s network consultant.

Thanks

Kristopher

 


kristopherk09

Failed to install WIndows update KB3045313

$
0
0

Environment

Our machine is running Windows Server 2012 R2 Standard and SQL Server 2008 R2 (SP2) - 10.50.4000.0 (Intel X86).

Problem encountered

When installing the update for KB3045313 in Windows Update, the following error was prompted (error screen attached):

Error(s) found:

Code 80246013 Windows Update ran into a problem.

Then I tried to download the update from Microsoft and install the update manually, the following error was prompted (error screen attached):

The following feature couldn't be installed:

.NET Framework 3.5 (includes .NET 2.0 and 3.0)

As .NET framework is not compulsory for SQL Server 2008 R2, how can we install the update for KB3045313 when SQL Server development using NET Framework 3.5 is not required for us.

Some updates of SQL Server 2008 and SQL Server 2014 were not recommended in Microsoft Update

$
0
0

Problem summary

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

We are running SQL Server 2008 R2 (SP2) and SQL Server 2014 in a Windows Server 2012 R2 server.  .NET framework 4.5 was enabled and .NET framework 3.5 was not enabled.  Some updates on SQL Server was not shown after checking for updates in Windows Update.

Versions of SQL Server installed

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

In Program and Features, the following installed versions were shown:

- Service Pack 2 for SQL Server 2008 R2 (KB2630458)  (Version 10.52.4000.0)

- Microsoft SQL Server 2014 Setup (English)

Updates not shown after checking for updates in Windows Update

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

- GDR 4042 for SQL Server 2008 R2 (KB3045313)    (Version 10.52.4042.0)

- Microsoft SQL Server 2014 Service Pack 2 (KB3171021)

Anyone can share experience.  Thank you.

SQL Installation Problems

$
0
0

I have had SQL Server 2012 intsalled and running fine on my Windows 10 laptop.

However, following a failed windows update, which also wiped out my restore points!, I had to 'reset' windows 10 and since then I have not been able to succesfully install SQL Server.

I believe that the following is the problem:-

(01) 2016-09-30 17:54:49 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2016-09-30 17:54:49 Slp: Inner exceptions are being indented
(01) 2016-09-30 17:54:49 Slp:
(01) 2016-09-30 17:54:49 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
(01) 2016-09-30 17:54:49 Slp:     Message:
(01) 2016-09-30 17:54:49 Slp:         Attempted to perform an unauthorized operation.
(01) 2016-09-30 17:54:49 Slp:     HResult : 0x84bb0001
(01) 2016-09-30 17:54:49 Slp:         FacilityCode : 1211 (4bb)
(01) 2016-09-30 17:54:49 Slp:         ErrorCode : 1 (0001)
(01) 2016-09-30 17:54:49 Slp:     Data:
(01) 2016-09-30 17:54:49 Slp:       WatsonData = HKEY_LOCAL_MACHINE@SYSTEM\CurrentControlSet\Services\FltMgr
(01) 2016-09-30 17:54:49 Slp:       DisableRetry = true
(01) 2016-09-30 17:54:49 Slp:     Inner exception type: System.UnauthorizedAccessException
(01) 2016-09-30 17:54:49 Slp:         Message:
(01) 2016-09-30 17:54:49 Slp:                 Attempted to perform an unauthorized operation.
(01) 2016-09-30 17:54:49 Slp:         HResult : 0x80070005
(01) 2016-09-30 17:54:49 Slp:         Stack:
(01) 2016-09-30 17:54:49 Slp:                 at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.OpenSubKey(String subkey, RegistryAccess requestedAccess)

I have looked at the registry and HKEY_LOCAL_MACHINE@SYSTEM\CurrentControlSet\Services\FltMgr is owned by system and I cannot change that ownership.

Any help or advice will be greatfully recieved.

Adding new node to existing SQL Server AlwaysOn

$
0
0

Hi,

Our AlwaysOn SQL Server 2012 already running with 2 Nodes on Windows Server 2012 R2 from past 1 year.

Now we are planning to add  NEW 3rd node. Does it requires any downtime for adding 3 Node to existing cluster? ]

Please suggest.

ENVIRONMENT: (VM Virtual Machines)

Node1      PrimaryManual                   --> Main Data Center

Node2     SecondaryManual     --> DR Location

Node 3     Primary          Automatic            --> Main Data Center     


Sql server encountered an error on installing or unistalling it.

$
0
0

When i am installing the sql server 2008 r2 it was showing an error : "The given was not present in the dictionary." Same problem is coming when i am uninstalling it. I am facing so much problem due to this. Please help me.


 

SQL Server 2016 Installation ERROR

$
0
0

While installing the SQL Server 2016  every time we are getting following Error.

Error "The Service did not respond to the start or control request in timely fashion." 


DB Mail not working in sql server 2012

$
0
0

Hi,

I am using sql server 2012 std edition 64 Bit version . 

I am trying to configure DB mail, where i am ending up with the error shown in the attached screen shot . 

This is the first time i try after installing sql server  in that environment, 

I have as well checked sp_configure , the value of dbmail where it shows as 1. 

Can some how help me to resolve this problem . 

Or is ther any way , where we can install DB mail alone with out disturbing the entire server.


hemadri


SQL R Installation Error - Tried multiple times!

$
0
0

I can not get SQL R successfully installed.  I have tried both offline and onne installation attempts.  I have patched to CU2 but that has not helped.

Message is: 

Action required:

Use the following information to resolve the error, and then try the setup process again.

Feature failure reason:

An error occurred during the setup process of the feature.

Error details:

§ Error installing Unknown

R Patch failed. Check /logfile "C:\Program Files\Microsoft SQL Server\130\Setup Bootstrap\Log\20161018_135807\RSetup.log" for details.

Error code: 0x80131500

Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=13.0.2164.0&EvtType=0x25C2E45A%400xC68B78F0&EvtType=0x25C2E45A%400xC68B78F0 to get help on troubleshooting.

Latest error is:

Running command: E:\MSSQL\MSSQL13.MSSQLSERVER\R_SERVICES\\library\RevoScaleR\rxLibs\x64\registerRext.exe /install /sqlbinnpath:"E:\MSSQL\MSSQL13.MSSQLSERVER\R_SERVICES\\..\MSSQL\Binn" /userpoolsize:0 /instance:"MSSQLSERVER"

2016-10-18T13:10:00          WARN    E:\MSSQL\MSSQL13.MSSQLSERVER\R_SERVICES\\library\RevoScaleR\rxLibs\x64\registerRext.exe:Command returned exit code -1

Any ideas?! Please :-)

Regards

Rob Firth

SQL Server Database Encryption mechanism

$
0
0

HI Team,

I have two instances / Servers 

1. SQL Server 2012 - Ent. Edt

2. SQL Server 2016 - Ent. Edt

I have got an requirement that i would need to implement the sql database level encryption technique. where by the Database sizes varies from 10 GB to 300 GB , around 10 DB's i have in total to be encrypted, but where as in total each instance has got 50 DB's . 

Can you please help me to adopt that , it would be great if some one of you can share your expert advise to configure the same. 

as well few questions i have is 

1. IF the DB is encrypted, though i am a DBA , i might not be allowed to view the data in the DB unless i have that encrypted key ? am i true or if i am wrong , can you please guide me . 

2. as well, if the application which has got read access or write access , which is talking to that encrypted DB , can able to se the data or pull the values from the DB as it was before encryption . 

3. If the DB is encrypted and the key is with my friend and i dont know the same, but i have SA privilage , where in can i have full privilage to view the Data , though the DB is encrypted. 

Please share me if you have any URLs to understand the basics 

thank you 

hemadribabu


hemadri


Database in recovery mode

$
0
0

Hi ,

Can some one help me to identify , the reason why the SQL DB is ( user DB) is going to Recovery mode daily in the morning hours in between 7 AM to 11 AM , any time in between . 

I dont have exact clue on the reason behind , but request your help to point out why & the action point to be taken to prevent it.

few points 

1. sql server is an 2008 std 64 Bit

2. have enough disk space on the user DB where their mdf, ldf files are stored.

3. perform full backup daily in the midnight around 12 AM  and perform tlog backups every 30 mins . 

Thanks


hemadri

Unable to apply SP2 CU2 or SP1 CU9 patch to SQL 2014 RTM Enterprise Edition

$
0
0

Hi all,

I am trying to apply patch upgrade to SQL 2014 Enterprise edition(12.0.2000.8). But check boxes are disabled where we select SQL Instance to upgrade. Error states:

When tried to apply SQL 2014 SP1 CU9 patch, Error is-
The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update.
The installed SQL Server product version is 12.0.2000.8, and the expected SQL Server version is 12.1.4100.1.

When tried to apply SQL 2014 SP2 CU2 patch, Error is-
The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update.
The installed SQL Server product version is 12.0.2000.8, and the expected SQL Server version is 12.2.5000.0.

Please help. Thank you.

Viewing all 7701 articles
Browse latest View live


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