RICHARDG

upgrading from 2008 r2 eval to 2008 r2 enterprise.

Use the maintenance option from setup. Get pretty far along in the process.  But then the following error. ( an additional note. setup warns that I am running sql server on a domain controller server. )

The link the error message points to has nothing to say. Why would my sql server upgrade fail? If I have to reinstall, will I lose my database data?

thanks,

TITLE: Microsoft SQL Server 2008 R2 Setup
------------------------------

The following error has occurred:

Access to the path 'C:\Program Files\Microsoft SQL Server\100\License Terms\SQLServer2008R2_License_ENT_1033.rtf' is denied.

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+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1&EvtType=0x60797DC7%25400xBB814387
 

DKB

The following error has occurred:  Error reading from file: F:\Software\SqlServer2014Express_with_tools_ctp2_64\x64\setup\sql_engine_core_shared_msi\PFiles32\SqlServr\90\Shared\zdyfqffr.ico.   Verify that the file exists and that you can access it. 

How I can fix it?

I have an Azure Mobile Service Scheduler Job scheduled to run with a frequency of Every 1 days at 11:45 PM.

But on some days its noticed that the scheduler job is running Twice. say if it had run once on 11.45 and it runs again at 11.46. there is no failure on the first run though . very confusing here.

i am not sure if its a known Bug ?. or am i doing something wrong.

Windows Update is offering KB3072779 (MSSQL Server 2012 SP3).

However, we are running MSSQL 2014 SP1 CU4 (12.0.4436.0) which was an in-place upgrade from MSSQL 2012 SP2.

This is on Windows Server 2012 R2 on ESXi 6.

I'm ignoring the update.  Seems strange that it would be offered?

Hi Folks,

I'm looking for advice on if it is possible to have SQL server function with 1 database accessed by 3 subnets when the 3 subnets are connected directly to the server and the Server's NIC  is configured with IP routing to allow access from each subnet to the SQL server to read and update information into the one database.

I have done testing previously with accessing a file share from multiple subnets by connecting those subnets directly to the server and configuring IP routing on the server but I have never done it with SQL.

Regards

Ciaran

I added a new node to a SQL Server failover cluster. When i was trying to update the SQL server 2008  r2 with SP2 on the New node I got an error . All the existing nodes already have  SQL Server service SP2, so the new node also needs to be SP2. I am getting the missing msi file error when applying SP2 to the new node.

SQL Server Setup has encountered the following error:

The cached MSI file 'C:\Windows\Installer\df540d0.msi' is missing.
Its original file is 'sql_engine_core_inst_loc.msi' and it was installed for product 'SQL Server 2008 R2 Database Engine Services'
from 'E:\en_sqlserver2008r2ent_x86_x64\1033_ENU_LP\x64\setup\sql_engine_core_inst_loc_msi\',
 version '10.50.1600.1', language 'ENU'.
To resolve this problem, recover the missing file from the installation media and start setup again.
For more information about how to resolve this problem, see 'Steps to restore the missing Windows Installer cache files' (http://go.microsoft.com/fwlink/?LinkId=144387)  in the Microsoft Knowledge Base.

Error code 0x84B20002.

My questions are:

1) how do the msi files become missing? Are they deleted automatically or do they get deleted manually?

2) I have read articles online about how to resolve the problem. But what i need to know is how and why do the files get missing?

I have a server with 32 cores. I need to purchase SQL Standard 2014 for this server. SQL Standard 2014 supports maximum of 16 cores. Is there any way of utilising all of 32 cores of server.

For eg. If I purchase 16 core license and install 2 instances of SQL Standard on the server. Will both instances use same 16 cores or different 16 cores.

Also 1 question is if I can install multiple instances of SQL on same server machine with single license. So to install I will need to purchase 8*2core packs or 16*2 core packs. Assuming I am using processor affinity to use all 32 cores of the server.

After doing a fresh install to see if another problem could be solved more easily. I have run into the issue of these two processes for SQL express not functioning at all upon completing my installation. The error logs are below.

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893607
  Start time:                    2016-03-01 08:18:01
  End time:                      2016-03-01 08:40:05
  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 Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  NICOCRB
  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\Nicolle\Downloads\SQLEXPRWT_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, CONN, BC, SDK, SSMS, ADV_SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  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:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           NICOCRB\Nicolle
  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\20160301_081656\ConfigurationFile.ini

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

  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Client Tools SDK
  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed

  Feature:                       Management Tools - Basic
  Status:                        Passed

  Feature:                       Database Engine Services
  Status:                        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:                       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:                       SQL Writer
  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\20160301_081656\SystemConfigurationCheck_Report.htm

Hi Expert!

We Installed SQL Server 2005 seven years back (In 2008/2009) but unfortunately  not install any service pack yet.

Following is SQL server information:

My question is that if I installed directly SP4 now, so is there any risk on running business application.....

PS: SQL server 2005 installed on Windows 2003 64 bit

Thanks

SQL Server Setup comes with a feature to generate a report of what SQL Features are installed on that local host.
  See: https://msdn.microsoft.com/en-us/library/bb510455.aspx  orhttp://mssqlfun.com/2013/02/26/sql-server-discovery-report/

I want to capture that data into SCCM Inventory so that in my SCCM Reporting I can tell the difference between a host running the Management Studio and a host running SQL Server (or other services) that require licensing.

Granted, the setup command to generate the report will have to be run periodically to get the current state and each run of that report generates a new folder uniquely named at the time it ran.  That part I can probably script and execute with an SCCM package.  More so, once that data is generated, how to get it into SCCM via Inventory is the bigger challenge.

I'm sure I am not the first to have this desire so I am hoping there is a solution out there has gone through some cycles and proven reliable?

Hello!

I am trying to run some experiments using a VM and I choose an A6 instance (4 cores, 28GB, Intel Xeon processor) which shows that there are only 4 physical cores and no hyperthreading (therefore 4 logical processors).

I have also built a HDInsight cluster with an A6 instance datanode and namenodes. I connected through the remote desktop and checked for the processors available through commandline and got 4 cores and 4 Logical processors. Yet when I run my application on the cluster and check the Hadoop Yarn Status web UI for the nodes that are up and running, there is a section under cluster metrics that says "VCores Available: 8". 

Can anyone clarify why there is a discrepancy seen in the cluster?

Thank you! 

We have a multi instance install of SQL Server 2008 R2 on Windows Server 2008 R2. We would like to upgrade both of these. The SQL upgrade seems fairly straightforward but I was wondering if anyone had any guidance regarding upgrading the Server OS itself when running SQL Server? I did some searching but did not find any solid guidance on whether this is a bad idea (I know technically this OS upgrade path is supported).

In case of MSSQL Server 2008, SQL server has created some SQL Server users like

SQLServerMSSQLUser$hostname$MSSQLSERVER

SQLServerMSSQLAgentUser$hostname$MSSQLSERVER

...

However, MSSQL Server 2012 seems not creating such users.

Our software product is using SQL Server, we need to make sure of the validity of these user settings.

May I know whether there is no problem without these users in SQL server 2012 ?

Does SQL Server (2003, 2008, 2012) support TLS 1.2? Is so, how to configure it?

I have installed SQL Server 2008 R2 on a Windows 2008 R2 machine, and following instruction to set TLS 1.2 for IIS, while IIS works with TLS 1.2 (verified with a remote browser restricted to TLS 1.2), the SQL Server to a restricted client would fail and the server had chosen TLS 1.0 - anyone knows if there is a solution for this - many thanks.

Does anyone know if running SQL 2008 R2 on Windows Server 2008 R2 if you can enable TLS 1.2 for connections between the SQL server and the SQL 2008 R2 ODBC client? I successfully enabled TLS 1.2 in IIS 7.5. But a network trace with the same system tweaks showed that the SQL connection was only being negotiated at TLS 1.0.

Enabling TLS 1.2 for IIS 7.5 can be found here:

http://derek858.blogspot.com/2010/06/enable-tls-12-aes-256-and-sha-256-in.html

The big difference between TLS 1.0 and 1.2 is the use of SHA-256 hashing instead of SHA1. NIST has recommended the phasing out of SHA1 in favor of SHA-256.

Could really use some help.

Am running XP Pro SP3.  Had 2005 Express running fine previously.  Installed 2008 Express but cannot get the SQL Server service to start.  SQL Server Agent does start though.  In log (below) it seems to be trying to access an E:\ drive that doesn't exist (did default install to C:\Program Files) - plus other issues.  Have 5gig+ free, so not sure why it's saying not enough space.  Have RTFMd the problem for a whole day with no luck.  Any advice much appreciated.

Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86) 

Apr  2 2010 15:53:02 

Copyright (c) Microsoft Corporation

Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3) (Hypervisor)

Error: 17054, Severity: 16, State: 1.

The current event was not reported to the Windows Events log. Operating system error = 1502(The event log file is full.). You may need to clear the Windows Events log if it is full.

(c) Microsoft Corporation.

All rights reserved.

Server process ID is 4988.

Authentication mode is WINDOWS-ONLY.

Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.

This instance of SQL Server last reported using a process ID of 3232 at 9/4/2010 9:36:12 AM (local) 9/4/2010 1:36:12 PM (UTC). This is an informational message only; no user action is required.

Registry startup parameters: 

-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf

-e c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG

-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf

SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

Detected 1 CPUs. This is an informational message; no user action is required.

Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.

Node configuration: node 0: CPU mask: 0x00000001:0 Active CPU mask: 0x00000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

Starting up database 'master'.

FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.

SQL Trace ID 1 was started by login "sa".

Starting up database 'mssqlsystemresource'.

The resource database build version is 10.50.1600. This is an informational message only. No user action is required.

Server name is 'FOO\SQLEXPRESS'. This is an informational message only. No user action is required.

Informational: No full-text supported languages found.

Starting up database 'model'.

Starting up database 'msdb'.

Error: 17204, Severity: 16, State: 1.

FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).

Error: 5120, Severity: 16, State: 101.

Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".

Error: 17204, Severity: 16, State: 1.

FCB::Open failed: Could not open file e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1.  OS error: 3(The system cannot find the path specified.).

Error: 5120, Severity: 16, State: 101.

Unable to open the physical file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".

Error: 17207, Severity: 16, State: 1.

FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.

File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.

Error: 945, Severity: 14, State: 2.

Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.

Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.

SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

A self-generated certificate was successfully loaded for encryption.

Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].

Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].

Error: 17207, Severity: 16, State: 1.

FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.

File activation failure. The physical file name "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.

Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.

The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

SQL Server is now ready for client connections. This is an informational message; no user action is required.