Hi all,

I have upgraded some of our SQL2008 enterprise servers from SQL 2014. 

Everything seems to be working reasonably well but I discovered an issue with trying to use debug in SSMS.

Was getting the same error, namely 'failed to start debugger. Data is null. The method or property cannot be coded on Null value'.

One of the servers was my test server, so I played with various things to try and fix it, tried uninstalling/reinstalling the tools, tried the SQL 2016 tools - no joy. 

What finally fixed it was running the 'repair' option from the installation media.

But there seems to be little documentation or advice as to what this does, and I'm wary of running this on a production server without knowing what the risks could be.   Has anyone any experience/info on this option and whether it can cause more harm that good.  Is is advisable to get well backed up before running it ?

Thanks

PD

 Start time:                    2016-10-06 11:11:33
  End time:                      2016-10-06 11:27:27
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
  Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
  Next step for 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 SSMS:            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 Replication:     Use the following information to resolve the error, and then try the setup process again.

Machine Properties:
  Machine name:                  KEVIN
  Machine processor count:       4
  OS version:                    Windows 7
  OS service pack:               Service Pack 1
  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
  Installation location:         C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\x64\setup\
  Installation edition:          Express

  Slipstream:                    True
  SP Level                       1

Product Update Status:
  Success: KB 3058865

Product Updates Selected for Installation:
  Title:                         Microsoft SQL Server 2014  with SP1
  Knowledge Based Article:       KB 3058865
  Version:                       12.1.4100.0
  Architecture:                  x64
  Language:                      1033

  Update Source:                 Slipstream

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:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\ConfigurationFile.ini
  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, SNAC_SDK
  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:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           Kevin\Trogdor
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  Slipstream
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Complete
  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  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 2008 Setup Support Files
  Component error code:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  Feature:                       Management Tools - Basic
  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:             

  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  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:          1308
  Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161006_111132\SqlSupport_KatmaiRTM_Cpu64_1.log
  Error description:             Source file not found: C:\Users\KevinIT\AppData\Local\Temp\Temp1_sql server 2014.zip\sql server 2014\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\AddNode.xml. Verify that the file exists and that you can access it.
  Error help link:              

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Documentation Components
  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

In SQL Server 2008 R2 is there anyway that I can change the delete dialog box to populate the delete existing connections check box. I.e. When I click on delete database I would like the close existing connections box already checked.

Hi There,

We are in the process of setting up new DB server but need some help on whether we should go Virtual hosting route or physical one. Here is the background info:

Database: SQL Server 2016 with SSRS

It will be centrally hosted with around max 200 concurrent users, system will be accessed by users a crossed globe. In future number of concurrent users may rise to 300 users.

Infra team has assured me that they will be setting up dedicated DB server but they want to host virtual server on it cause it is more beneficial from DR point of view.

Development team prefer to have physical server because it makes life easy when things goes wrong and needs investigation

I hope you can either provide me some guidance on it or point me in right direction on this dilemma.

Many thanks in advance.

Regards,

Santosh

Hello,

I have a SQL Server instance which is serving as a DB server for my SharePoint Farm.The SQL Server instance is in a Windows Fail Over Cluster.The Operating system is Windows 2008 R2. The shared Drive for the clustered SQL server instance are running on a SAN. The SAN is running out of its support and life cycle. There is a new SAN which is purchased and ready to be provisioned. What is the best way to move the data from the old san  to the new one.Please note the SAN drives just doesnt hold database and log files, I mean its just not the MDF and LDF files.Its the folder structure and the binaries for the SQL server which is also sitting on the SAN Drives.I had initially thought of detaching the SQL Dbs , copying the MDF and LDF files over to the new volumes from the SAN and then attaching them back.BUt when i had a close look at the drives , i saw the SQL folder structure i.e. MSSQL and other directories on the SAN drives.This could possibly contain some shared files which i am not sure would be required if i just copy mdf,ldf files and use the attach detach method.I researched a lot and found some workarounds.One of them would be to copy the entire contents of the existing SAN drives to the new SAN drives and just change the drive letter.I am not sure if thisi is the best and recommended way of doing this.Any help is much appreciated.

Regards,

Irfan M. Shaikh

IrfanWalid

Anyone know of how I can specifically download CU7 ?

Our software vendor has stated that we need 12.00.4459 SQL Server 2014 SP 1 CU 7 is needed and that they don't recommend CU8 which is what Download the latest cumulative update package for Microsoft SQL Server 2014 Service Pack 1 (SP1) now.

Thanks,

Adam

 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.

Hi all of you, our stores run 2014 Express Edition with CU14 or just 12.0.2000.8

is it recommended to apply SP1? Any caveat or threat known doing that?

Thanks for your time and inputs,

Enric

hi,

i'm using SQL Server 2008 SP3 (not R2) Standard version (10.0.5500) with Windows Server 2008 R2 Standard

i can't find any documents regarding SQL Server 2008 in Microsoft site.

all i can find is SQL 2008 R2

https://msdn.microsoft.com/en-us/library/ms143685(v=sql.105).aspx

i'm planning to upgrade Windows 2008 R2 Standard to Enterprise (which allow more than 32GB RAM)

can SQL Server 2008 SP3 use more than 32GB RAM?

Thank You

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

Hi,

This strange behavior started recently. If I close SSMS, it restarts itself as if it crashed and trying to restore itself. Even if I hit cancel as it's restarting, it will restart itself yet again. This happens twice. Any idea what's causing this?

Thanks, Sam

A while back I tried installing CU6 on my SQL 2014 server and it failed badly.  After working on it for a day I just gave up and restored back to before the update. I have been avoiding the CUs ever since.

Today I tried installing SP2, hoping it would fixe whatever caused the CU to fail.  Well it died too and I can't seem to find any relevant info searching the web, most of the stuff is related to 2012 issues.  In the error log there is a reference to Cannot find the user '##MS_SSISServerCleanupJobUser##' I do not recognize this user and as far I can remember it never existed on the server, I was the one who setup and configured the server so I know I never deleted it.  Master is toast right now so any help would be greatly appreciated. 

Here is what I got from the installer:

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 SQL Server Database Engine Services Instance Features
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error code: 0x851A001A
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.5000.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026 to get help on troubleshooting.

The link goes to an ad for a Service Pro 4 so not very useful.  The log file says:

Overall summary:
  Final result:                  The patch installer has failed to update the following instance: MSSQLSERVER. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2061893606
  Start time:                    2016-10-10 12:20:01
  End time:                      2016-10-10 12:38:58
  Requested action:              Patch

Instance MSSQLSERVER overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2061893606
  Start time:                    2016-10-10 12:37:59
  End time:                      2016-10-10 12:38:56
  Requested action:              Patch

Machine Properties:
  Machine name:                  METSQLBI01
  Machine processor count:       4
  OS version:                    Windows Server 2012
  OS service pack:              
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services                 1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
  SQL Server 2014      MSSQLSERVER          MSAS12.MSSQLSERVER             Analysis Services                        1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
  SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native              1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
  SQL Server 2014                                                          Management Tools - Basic                 1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
  SQL Server 2014                                                          Management Tools - Complete              1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
  SQL Server 2014                                                          Client Tools Connectivity                1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      
  SQL Server 2014                                                          SQL Server Data Tools - Business Intelligence for Visual Studio 2013 1033                                      12.0.2430.0     No         Yes      
  SQL Server 2014                                                          Integration Services                     1033                 Business Intelligence Edition 12.2.5000.0     No         Yes      

Package properties:
  Description:                   Microsoft SQL Server 2014
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       2
  KBArticle:                     KB3171021
  KBArticleHyperlink:           http://support.microsoft.com/?kbid=3171021
  PatchType:                     SP
  AssociatedHotfixBuild:         0
  Platform:                      x64
  PatchLevel:                    12.2.5000.0
  ProductVersion:                12.0.2000.8
  GDRReservedRange:              12.0.2200.0:12.0.2290.0;12.0.4200.0:12.0.4299.0;12.0.4830.0:12.0.4880.0
  Installation location:         f:\fa696b9bbd6496233f0814\x64\setup\

Updated product edition:
  Instance             Edition            
  MSSQLSERVER          Business Intelligence

User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  false
  CLUSTERPASSIVE:                false
  CONFIGURATIONFILE:            
  ENU:                           true
  ERRORREPORTING:                false
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTANCEID:                    <empty>
  INSTANCENAME:                  <empty>
  QUIET:                         false
  QUIETSIMPLE:                   false
  SQMREPORTING:                  false
  UIMODE:                        Normal
  X86:                           false

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161010_122000\SystemConfigurationCheck_Report.htm

The System Configuration Check report looks like this:

Computer Name(s):METSQLBI01
Report Date/Time: 10/10/2016 12:20 PM
Saved to Directory: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20161010_122000\SystemConfigurationCheck_Report.htm

Rule Name		Rule Description	Result	Message/Corrective Action
PatchGlobalRules: SQL Server 2014 Setup configuration checks for rules group 'PatchGlobalRules'
	Engine_ResourceDLLUpdateRestartCheck	Checks whether shared resource DLLs will be updated, causing restarts for clustered SQL Server instances active on this node.	Not applicable	This rule does not apply to your system configuration.
	AclPermissionsFacet	Checks if the SQL Server registry keys are consistent.	Passed	SQL Server registry keys are consistent and can support SQL Server installation or upgrade.
	Cluster_IsLocalNodeGroupOwner	Checks if the local computer is an owner of an online cluster group for a failover cluster instance that contains the SQL Server service, Analysis Services service or a generic service.	Passed	The local computer is not an owner of an online cluster group for a failover cluster instance that contains the SQL Server service, Analysis Services service or a generic service. The SQL Server instances do not need to be taken offline.
	Cluster_IsOnlineIfClustered	Verifies that the computer is not clustered or that the computer is clustered and the cluster service is online.	Passed	The computer is either not clustered or the cluster is up and online.
	RebootRequiredCheck	Checks if a pending computer restart is required. A pending restart can cause Setup to fail.	Passed	The computer does not require a restart.
	ThreadHasAdminPrivilegeCheck	Checks whether the account running SQL Server Setup has administrator rights on the computer.	Passed	The account running SQL Server Setup has administrator rights on the computer.
	WmiServiceStateCheck	Checks whether the WMI service is started and running on the computer.	Passed	The Windows Management Instrumentation (WMI) service is running.

Rules Documentation:       http://go.microsoft.com/fwlink/?LinkId=296445      
Community:        http://go.microsoft.com/fwlink/?LinkId=296470      
Setup Help File:        http://go.microsoft.com/fwlink/?LinkId=296452

There are 3 error logs and one very big detail.txt file.  The error logs all look similar but are not exactly the same.  The final error that kills the process is the same in all three so I am posting only the last one.

2016-10-10 12:38:49.09 Server      Microsoft SQL Server 2014 (SP2) (KB3171021) - 12.0.5000.0 (X64)
 Jun 17 2016 19:14:09
 Copyright (c) Microsoft Corporation
 Business Intelligence Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)

2016-10-10 12:38:49.09 Server      UTC adjustment: -4:00
2016-10-10 12:38:49.09 Server      (c) Microsoft Corporation.
2016-10-10 12:38:49.09 Server      All rights reserved.
2016-10-10 12:38:49.09 Server      Server process ID is 3128.
2016-10-10 12:38:49.09 Server      System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2016-10-10 12:38:49.09 Server      Authentication mode is WINDOWS-ONLY.
2016-10-10 12:38:49.09 Server      Logging SQL Server messages in file 'D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2016-10-10 12:38:49.09 Server      The service account is 'FRANCO-MFG\SQLBI_sqlsrv$'. This is an informational message; no user action is required.
2016-10-10 12:38:49.09 Server      Registry startup parameters:
  -d D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
  -e D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
  -l D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2016-10-10 12:38:49.09 Server      Command Line Startup Parameters:
  -s "MSSQLSERVER"
  -m "SqlSetup"
  -T 4022
  -T 4010
  -T 1905
  -T 3701
  -T 8015
2016-10-10 12:38:49.46 Server      SQL Server detected 2 sockets with 2 cores per socket and 2 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2016-10-10 12:38:49.46 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-10-10 12:38:49.46 Server      Detected 32767 MB of RAM. This is an informational message; no user action is required.
2016-10-10 12:38:49.46 Server      Using conventional memory in the memory manager.
2016-10-10 12:38:49.50 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-10-10 12:38:49.53 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2016-10-10 12:38:49.55 Server      The maximum number of dedicated administrator connections for this instance is '1'
2016-10-10 12:38:49.55 Server      This instance of SQL Server last reported using a process ID of 884 at 10/10/2016 12:38:48 PM (local) 10/10/2016 4:38:48 PM (UTC). This is an informational message only; no user action is required.
2016-10-10 12:38:49.55 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-10-10 12:38:49.56 Server      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.
2016-10-10 12:38:49.56 Server      Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2016-10-10 12:38:49.57 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2016-10-10 12:38:49.57 spid8s      Warning ******************
2016-10-10 12:38:49.57 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2016-10-10 12:38:49.57 spid8s      Starting up database 'master'.
2016-10-10 12:38:49.59 spid8s      5 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2016-10-10 12:38:49.60 spid8s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2016-10-10 12:38:49.60 spid8s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-10-10 12:38:49.68 Server      CLR version v4.0.30319 loaded.
2016-10-10 12:38:49.68 spid8s      CHECKDB for database 'master' finished without errors on 2016-10-08 02:00:00.627 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.68 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-10-10 12:38:49.68 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-10-10 12:38:49.70 spid8s      SQL Trace ID 1 was started by login "sa".
2016-10-10 12:38:49.71 spid8s      Server name is 'METSQLBI01'. This is an informational message only. No user action is required.
2016-10-10 12:38:49.72 spid15s     Starting up database 'ReportServer'.
2016-10-10 12:38:49.72 spid16s     Starting up database 'ReportServerTempDB'.
2016-10-10 12:38:49.72 spid9s      Starting up database 'mssqlsystemresource'.
2016-10-10 12:38:49.72 spid17s     Starting up database 'AdminFranco'.
2016-10-10 12:38:49.72 spid18s     Starting up database 'InventoryAudit'.
2016-10-10 12:38:49.73 spid14s     Starting up database 'msdb'.
2016-10-10 12:38:49.73 spid19s     Starting up database 'SSISDB'.
2016-10-10 12:38:49.73 spid9s      The resource database build version is 12.00.5000. This is an informational message only. No user action is required.
2016-10-10 12:38:49.73 spid20s     Starting up database 'ReportingAndUtility'.
2016-10-10 12:38:49.73 spid21s     Starting up database 'RedGate'.
2016-10-10 12:38:49.73 spid22s     Starting up database 'GDSN'.
2016-10-10 12:38:49.73 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-10-10 12:38:49.73 spid12s     A self-generated certificate was successfully loaded for encryption.
2016-10-10 12:38:49.73 spid12s     Server local connection provider is ready to accept connection on [\\.\pipe\SQLLocal\MSSQLSERVER ].
2016-10-10 12:38:49.73 spid12s     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.
2016-10-10 12:38:49.74 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-10-10 12:38:49.78 spid9s      Starting up database 'model'.
2016-10-10 12:38:49.79 spid16s     CHECKDB for database 'ReportServerTempDB' finished without errors on 2016-10-08 05:00:04.180 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.79 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com ] for the SQL Server service.
2016-10-10 12:38:49.79 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com:1433 ] for the SQL Server service.
2016-10-10 12:38:49.80 spid15s     CHECKDB for database 'ReportServer' finished without errors on 2016-10-08 05:00:03.480 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.80 spid17s     CHECKDB for database 'AdminFranco' finished without errors on 2016-10-08 05:00:00.990 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.80 spid21s     CHECKDB for database 'RedGate' finished without errors on 2016-10-08 05:00:02.840 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.81 spid20s     CHECKDB for database 'ReportingAndUtility' finished without errors on 2016-10-08 05:00:03.167 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.81 spid22s     CHECKDB for database 'GDSN' finished without errors on 2016-10-08 05:00:01.510 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.82 spid14s     CHECKDB for database 'msdb' finished without errors on 2016-10-08 02:00:01.913 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.83 spid19s     24 transactions rolled forward in database 'SSISDB' (9:0). This is an informational message only. No user action is required.
2016-10-10 12:38:49.84 spid18s     CHECKDB for database 'InventoryAudit' finished without errors on 2016-10-08 05:00:02.027 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.85 spid9s      CHECKDB for database 'model' finished without errors on 2016-10-08 02:00:01.517 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:49.85 spid9s      Clearing tempdb database.
2016-10-10 12:38:49.85 spid19s     0 transactions rolled back in database 'SSISDB' (9:0). This is an informational message only. No user action is required.
2016-10-10 12:38:49.85 spid19s     Recovery is writing a checkpoint in database 'SSISDB' (9). This is an informational message only. No user action is required.
2016-10-10 12:38:49.88 spid19s     CHECKDB for database 'SSISDB' finished without errors on 2016-10-08 05:00:04.553 (local time). This is an informational message only; no user action is required.
2016-10-10 12:38:50.07 spid9s      Starting up database 'tempdb'.
2016-10-10 12:38:50.43 spid9s      The tempdb database has 4 data file(s).
2016-10-10 12:38:51.50 spid8s      Database 'master' is upgrading script 'SSIS_hotfix_install.sql' from level 201330692 to level 201331592.
2016-10-10 12:38:51.68 spid8s      ------------------------------------------------------
2016-10-10 12:38:51.68 spid8s      Starting execution of SSIS_HOTFIX_INSTALL.SQL        
2016-10-10 12:38:51.68 spid8s      ------------------------------------------------------
2016-10-10 12:38:51.69 spid8s      Start applying SSIS_HOTFIX_INSTALL changes.
2016-10-10 12:38:51.71 spid8s      Stored procedure [catalog].[create_execution] has been dropped.
2016-10-10 12:38:51.71 spid8s      Stored procedure [catalog].[set_execution_parameter_value] has been dropped.
2016-10-10 12:38:51.71 spid8s      Stored procedure [catalog].[configure_catalog] has been dropped.
2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[cleanup_server_retention_window] has been dropped.
2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[cleanup_server_log] has been dropped.
2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[cleanup_server_execution_keys] has been dropped.
2016-10-10 12:38:51.72 spid8s      Stored procedure [internal].[get_execution_values] has been dropped.
2016-10-10 12:38:51.73 spid8s      Stored procedure [internal].[get_execution_property_override_values] has been dropped.
2016-10-10 12:38:51.73 spid8s      Stored procedure [internal].[configure_execution_encryption_algorithm] has been dropped.
2016-10-10 12:38:51.73 spid8s      Stored procedure [catalog].[set_execution_property_override_value] has been dropped.
2016-10-10 12:38:51.87 spid8s      Stored procedure [catalog].[create_execution] has been recreated.
2016-10-10 12:38:51.89 spid8s      Stored procedure [catalog].[set_execution_parameter_value] has been recreated.
2016-10-10 12:38:51.90 spid8s      Stored procedure [internal].[cleanup_server_retention_window] has been recreated.
2016-10-10 12:38:51.91 spid8s      Stored procedure [internal].[cleanup_server_log] has been recreated.
2016-10-10 12:38:51.93 spid8s      Stored procedure [internal].[cleanup_server_execution_keys] has been recreated.
2016-10-10 12:38:51.94 spid8s      Stored procedure [internal].[get_execution_values] has been recreated.
2016-10-10 12:38:51.95 spid8s      Stored procedure [internal].[get_execution_property_override_values] has been recreated.
2016-10-10 12:38:51.97 spid8s      Stored procedure [internal].[configure_execution_encryption_algorithm] has been recreated.
2016-10-10 12:38:51.99 spid8s      Stored procedure [catalog].[configure_catalog] has been recreated.
2016-10-10 12:38:52.01 spid8s      Stored procedure [catalog].[set_execution_property_override_value] has been recreated.
2016-10-10 12:38:52.01 spid8s      Permissions on [catalog].[create_execution] has been granted.
2016-10-10 12:38:52.01 spid8s      Permissions on [catalog].[set_execution_parameter_value] has been granted.
2016-10-10 12:38:52.02 spid8s      Permissions on [catalog].[configure_catalog] has been granted.
2016-10-10 12:38:52.02 spid8s      Error: 15151, Severity: 16, State: 1.
2016-10-10 12:38:52.02 spid8s      Cannot find the user '##MS_SSISServerCleanupJobUser##', because it does not exist or you do not have permission.
2016-10-10 12:38:52.02 spid8s      The failed batch of t-sql statements :
 /*
**  SSIS_hotfix_install.SQL
**  Patch install script for the SSIS server catalog (SSISDB).
*/

PRINT '------------------------------------------------------'
PRINT 'Starting execution of SSIS_HOTFIX_INSTALL.SQL         '
PRINT '------------------------------------------------------'

DECLARE @run_script BIT
SET @run_script=1

DECLARE @ssis_database_name SYSNAME
SET @ssis_database_name = N'SSISDB'

-- Check whether SSISDB exists
IF(DB_ID(@ssis_database_name) IS NULL)
BEGIN
    SET @run_script=0
    PRINT 'Database SSISDB does not exist in current SQL Server instance'
END

-- Check whether SSISDB is online
IF @run_script <> 0
BEGIN
 DECLARE @state_online SYSNAME
 SET @state_online = 'ONLINE'
 SELECT @state_online = UPPER(@state_online COLLATE SQL_Latin1_General_CP1_CI_AS)

 IF NOT EXISTS (SELECT state_desc FROM master.sys.databases WHERE name = @ssis_database_name AND
           UPPER(state_desc COLLATE SQL_Latin1_General_CP1_CI_AS) LIKE @state_online)
 BEGIN
  SET @run_script=0   
  PRINT 'WARNING! The database SSISDB is not ONLINE. SSIS_HOTFIX_INSTALL.SQL will not be applied. Please run the script manually after the upgrade.'
 END
END

-- Check whether SSISDB is corrupted
IF @run_script <> 0
BEGIN
 IF OBJECT_ID (N'SSISDB.internal.catalog_properties', N'U') IS NULL
 BEGIN
  SET @run_script=0
  PRINT 'Database SSISDB is missing the catalog properties table. The database may be corrupted, or it is not an SSIS Catalog.'
 END
END

IF  @run_script = 0
BEGIN
 PRINT 'Database SSISDB was not patched.'
END
ELSE
BEGIN
 PRINT 'Start applying SSIS_HOTFIX_INSTALL changes.'

 DECLARE @rawCmd NVARCHAR(MAX), @cmd NVARCHAR(MAX)

 DECLARE @targetVersion NVARCHAR(256)
 SELECT @targetVersion = CONVERT(NVARCHAR,SERVERPROPERTY(N'ProductVersion'))

    --Version handler for PCU2
 --1. drop the old SP
 IF OBJECT_ID (N'SSISDB.[catalog].[create_execution]', N'P') IS NOT NULL
 BEGIN
  SET @rawCmd = N'DROP PROCEDURE [catalog].[cre...
2016-10-10 12:38:52.02 spid8s      Error: 912, Severity: 21, State: 2.
2016-10-10 12:38:52.02 spid8s      Script level upgrade for database 'master' failed because upgrade step 'SSIS_hotfix_install.sql' encountered error 15151, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2016-10-10 12:38:52.02 spid8s      Error: 3417, Severity: 21, State: 3.
2016-10-10 12:38:52.02 spid8s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2016-10-10 12:38:52.02 spid8s      SQL Server shutdown has been initiated
2016-10-10 12:38:52.02 spid8s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2016-10-10 12:38:53.03 spid8s      Error: 25725, Severity: 16, State: 1.
2016-10-10 12:38:53.03 spid8s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.
2016-10-10 12:38:53.07 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com ] for the SQL Server service.
2016-10-10 12:38:53.07 spid12s     The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MetSQLBI01.franco-mfg.com:1433 ] for the SQL Server service.

Hello ,

We are evaluating options to consolidate our existing infrastructure to SQL Server cluster solution.

We couldn't find good reference materials on impact of placing TempDB on local SSD vs Shared SAN?.

How does it affect the fail-over scenario recovery timelines?. Does having TempDB locally increase the fail over time because inflight transactions needs to be committed or rolled back.

Your help is much appreciated.

I90Runner

I have a new laptop with windows 10 and wanted to install a SQL Server version. But every single version I try to install is failing when it is checking the setup rules. I tried a lot of things, also cleaning up the registry. But maybe I missed something.

Part of the Detailed logfile:

If more information is needed, please let me know.

Hopefully someone can help me out.

Shane

Hi all, I would like to know what the warning with linkid 94001 is all about and how to solve this?

i've  created an exception for the tcp 1433 and udp 1434 and also an exception for the database engine service but still didnt solved.

can anybody please help me?

I have SQL Server Server licenses (not the core version) available from way back and software assurance.  I need to do an install of SQL 2014 using one of those licenses.  The only way I see to run with that license (which has CPU limitations) is this:

1. install SQL 2008r2 Enterprise
2. Upgrade to SQL2012, specifying the server license during setup
3. Upgrade to 2014.

Is there a way to do this directly without all the steps?

Thanks

ZzZz

I'm a developer who has bought a reconditioned Samsung NC110 x64 netbook to mess around on during otherwise dull train journeys. I upgraded it from Win7 Starter edition to Win10 Home. I have installed VS2016 Community edition without any problems (other than speed!). Why can't SQL Server 2016 Express edition install?Win 10 Home is one of the supported OSes.

Thanks in advance.