Finding SQL Server licensing information for 2005 and above.

I can use SELECT serverproperty('LicenseType'), serverproperty('NumLicenses') on SQL Server 2000 but these server properties are no longer being returned in SQL Server 2005 and later. This information doesn't seem to be recorded in the registry for
SQL Server 2005 and later.
Is there an easy way to query or report licensing information for SQL Server 2005 onwards?
Thanks.

Hello,
Since SQL Server Version 2005 you have all license Information only on paper; so you have to lookup your papers to get the Information.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Similar Messages

SQL Server Licensing Information

I want to retrieve SQL server licensing information e.g. License type, Count, License Code etc.
Any help?
RK

You can find the license type using serverproperty function as shown in the below link, http://sql-articles.com/index.php?page=Scripts/ServerProperties.php
You may also refer these links where Arnie and Madhu have provided useful information regarding licenses.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2435258&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2713025&SiteID=1
- Deepak

License information for oracle and HTMLDB

Anybody knows which metalink document or where I can found information about getting license for Oracle Database 10g , oracle10gAS Forms&Report server and HTMLDB 2.0 to deploye on the web..?

Hello,
HTML DB v2.0 (Oracle Application Express, by its new name) does not need separate licensing, as it is part of the database license. For all the rest of the items in your post, you can get a "first impression" on the Oracle on-line store, but the best, I believe, is to contact a local Oracle sales person. They can give you the best information with current prices.
Regards,
Arie.

Problems! MS SQL Server 2000 Driver for JDBC.

In Dos-promt ill got only this message: com.microsoft.jdbc.sqlserver.SQLServerDriver
What is wrong and is there someone that can help me out?
I have installed Microsoft SQL Server 2000 Driver for JDBC and set the path like this in the system, advance, environment variable:
.;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar
This is the source code i use to test the connection:
import java.sql.*;
public class Exercise2_1 {
static String driver = ("com.microsoft.jdbc.sqlserver.SQLServerDriver");
static String url= "jdbc:microsoft:MinTest;ah;modeerf";//sqlserver://H:1433;user=ah;password=modeerf";
public static void main(String[] args) {
try {
     Class.forName(driver).newInstance();
     System.out.println("Loaded driver");
     Connection conn = DriverManager.getConnection(url);
     System.out.println("Connected to database");
     conn.close();
     System.out.println("Closed connection");
catch (Throwable e) { System.err.println(e.getMessage()); }

You printed the error message associated with the exception but didn't print the type of the exception. com.microsoft.jdbc.sqlserver.SQLServerDriver was probably a ClassNotFoundException meaning that the VM couldn't find the jars.
You say you put the jars in the path. They should actually be in the class path. Either set the CLASSPATH environment variable or pass it in to the Java VM via the -cp option.
One more thing. Seeing as the paths that you installed the JDBC driver into contain spaces you may need to put quotes around the path names or use the MSDOS short names for those directories.
Col

SQL ENTERPRISE: The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database

The error below makes absolutely no sense! I'm using Enterprise Core...yet I'm being told I can't use remote data sources:
w3wp!library!8!03/05/2015-19:08:48:: i INFO: Catalog SQL Server Edition = EnterpriseCore
w3wp!library!8!03/05/2015-19:08:48:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: , Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "The edition of Reporting
Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services.;
Really? This totally contradicts the documentation found here:
https://msdn.microsoft.com/en-us/library/ms157285(v=sql.110).aspx
That article says remote connections are completely supported.
ARGH! Why does this have to be so difficult to setup?!?

Hi jeffoliver1000,
According to your description, you are using Enterprise Core edition and you are prompted that you can’t use remote data sources.
In your scenario, we neither ignore your point nor be doubt with what you say. But actually we have met the case before that even though the SQL Server engine is Enterprise but the reporting services is still standard. So I would recommend you to find the
actual edition of reporting services you are using. You can find Reporting Services starting SKU in the Reporting Service logs ( default location: C:\Program Files\Microsoft SQL Server\<instance name>\Reporting Services\LogFiles). For more information,
please refer to the similar thread below:
https://social.technet.microsoft.com/Forums/en-US/f98c2f3e-1a30-4993-ab41-acbc5014f92e/data-driven-subscription-button-not-displayed?forum=sqlreportingservices
By the way, have you installed the other SQL Server edition before?
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Reporting Services Add-in for Sharepoint- does it need an SQL Server license?

In a new project we will be creating an SSRS in Sharepoint integrated mode. For this we'll need SQL Server and Sharepoint on that box.
We'll also have one or more SharePoint Web Front End (WFE) servers. To allow them to connect to the SSRS-in-sharepoint-mode box, and to present the user with the right user interface for doing so, I believe we can install the Reporting Services Add-In for
Sharepoint on the WFE servers.
The question is, do we need to have SQL Server license for each WFE server where we use the Reporting Services Add-In, or is it free to use?
We've had advice that we need to buy a SQL Server license everywhere we use the add-in, but I am not sure this is correct.
Thanks in advance,
Rich

Hello there,
The Reporting service Add-in for SharePoint can be downloaded free on Microsoft Download site. That means it does not need any license on the add-in.
Regards,
Edward
Edward Zhu
TechNet Community Support

Having issues with getting SQL Server Express to start services and run.

Good afternoon everyone,
I have been working on a 2012 R2 server getting ready to move databases to new hardware. I had SQL Server Express 2008 R2 running on this server with no issues. I was handed another software package that ran SQL Express 2012 and had to for compatibility
reasons. I have had multiple versions run on Server 2012 before with no issues. This time, not so lucky. When the installer from the updated package put on SQL Express 2012 it completed with errors ( error log posted at the end of post) and
would not allow me to run software. I then tried the db that I had installed on 2008 R2 and it also gave the same error as the 2012 version. IN basic terms the required services attempted to start and shut back down again. I have received
Error 1068 about database handles and error %%945. I know this db has plenty of space and the permissions were added for the Admin account to access both db's. I then uninstalled both versions and tried again, with the same errors listed when
I tried to start the services. I am thinking that a clean install would fix the issue however I am not certain what files/folders/reg entries need to be deleted or modified. I have researched all the errors I can find, however I am very
new with SQL anything so I know I am missing something. I also do not have an "E:" drive on this server (not sure why it is going there). Input would be very welcome as I am not certain where to go from here.
Thanks,
Matt
Error Log follows, server and domain names have been blacked out with ****.
2015-04-15 11:57:55.16 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-04-15 11:57:55.16 Server (c) Microsoft Corporation.
2015-04-15 11:57:55.16 Server All rights reserved.
2015-04-15 11:57:55.16 Server Server process ID is 4104.
2015-04-15 11:57:55.16 Server System Manufacturer: 'HP', System Model: 'ProLiant ML350p Gen8'.
2015-04-15 11:57:55.16 Server Authentication mode is WINDOWS-ONLY.
2015-04-15 11:57:55.16 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-04-15 11:57:55.17 Server The service account is 'NT AUTHORITY\LOCAL SERVICE'. This is an informational message; no user action is required.
2015-04-15 11:57:55.17 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-04-15 11:57:55.17 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-04-15 11:57:55.48 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-04-15 11:57:55.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-04-15 11:57:55.48 Server Detected 8157 MB of RAM. This is an informational message; no user action is required.
2015-04-15 11:57:55.48 Server Using conventional memory in the memory manager.
2015-04-15 11:57:55.68 Server This instance of SQL Server last reported using a process ID of 7840 at 4/15/2015 11:57:47 AM (local) 4/15/2015 3:57:47 PM (UTC). This is an informational message only; no user action is required.
2015-04-15 11:57:55.68 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-04-15 11:57:55.69 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.
2015-04-15 11:57:55.72 Server Software Usage Metrics is disabled.
2015-04-15 11:57:55.73 spid5s Starting up database 'master'.
2015-04-15 11:57:55.79 spid5s 20 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.79 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.80 Server CLR version v4.0.30319 loaded.
2015-04-15 11:57:55.86 spid5s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-04-15 11:57:55.89 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-04-15 11:57:55.91 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.91 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.94 spid5s SQL Trace ID 1 was started by login "sa".
2015-04-15 11:57:55.94 spid5s Server name is '********\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-04-15 11:57:55.96 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2015-04-15 11:57:55.96 spid5s Starting up database 'msdb'.
2015-04-15 11:57:55.96 spid9s Starting up database 'mssqlsystemresource'.
2015-04-15 11:57:55.96 spid5s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:55.96 spid5s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:55.96 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:55.96 spid5s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:55.96 spid5s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-04-15 11:57:55.99 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-04-15 11:57:56.02 spid12s A self-generated certificate was successfully loaded for encryption.
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv6> 53345].
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv4> 53345].
2015-04-15 11:57:56.03 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2015-04-15 11:57:56.03 spid12s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2015-04-15 11:57:56.04 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.
2015-04-15 11:57:56.04 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.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 53.
Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been
manually registered.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:53345 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure
to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually
registered.
2015-04-15 11:57:56.09 spid9s Starting up database 'model'.
2015-04-15 11:57:56.10 spid9s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:56.10 spid9s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:56.10 spid9s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:56.10 spid9s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:56.10 spid9s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-04-15 11:57:56.10 spid9s Error: 945, Severity: 14, State: 2.
2015-04-15 11:57:56.10 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-04-15 11:57:56.10 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

SQL Server License from SAP to use the Business Intelligence Stack

Hi Sean,
SQL Server license is a very complicated issue. If the tool is given to you in the package, it should be ok to use it. There is no update for the info provided in the blog although it is over 3 years.
Thanks,
Gordon

Hi delaynomore,
According to your description, you fail to execute the function with timeout error after migration to SQL Server 2012. Based on my research, the issue could be due to the long running tasks or uncommitted transactions.
To troubleshoot the issue, besides Olaf's suggestion to check the connection to SQL Server 2012 instance and the stored procedure using SQL Server Management Studio(SSMS) manually, you could also follow the methods below.
1. Execute that procedure manually using SSMS and check if it takes a very long time to execute and return. For example, there could be millions of rows being updated. If it takes a long time, you can adjust the CommandTimeout accordingly.
2. Execute the following statement in SSMS to check if there are any uncommitted transactions: dbcc opentran ('yourDatabaseName'). If there are any uncommitted transactions, please change the stored procedure accordingly to commit the transactions.
For more information about the process, please refer to the article:
http://blogs.msdn.com/b/spike/archive/2008/07/31/timeout-expired-the-timeout-period-elapsed-prior-to-completion-of-the-operation-or-the-server-is-not-responding.aspx
Regards,
Michelle Li

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
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
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\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: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality 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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
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
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Why SCCM 20012 Install fails with remote 64 bit SQL Server but proceeds for remote 32 bit SQL Server

I have the following setup:
AD User accounts
- SQLAdmin (used to run SQL Services i.e. Database Engine)
- SCCMADmin (used to install SCCM 2012)
SPN registered for user account SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1432 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1432 Domain_Name\SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1433 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1433 Domain_Name\SQLAdmin
and checked with setspn -L TESTING\SQLAdmin
1 SERVER called SQL
32bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dynamic ports)
User accounts that have been given public and sysadmin SQL server roles
on both instances are: SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned on with access allowed on Ports 1432, 1433, 4022,445, and WMI - WMI-in, DCOM-in and ASync-iN builtin rules allowed\enabled.
1 SERVER called SQL3
64bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dymanic ports)
User accounts that have been given public and sysafmin SQL server roles on both instances are:
SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned off
1 SERVER called SCCM
64bit Server that is to be the Primary Site Server\MP for SCCM 2012
ODBC link to SQL\SCCM2012,1432
ODBC link to SQL3\SCCM2012,1432
ODBC uses SQL Native Client 10.0 (64 bit)
Both ODBC connections when TESTed pass and suggest connectivity to SQL Servers
Install process doe SCCM2012
Tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account
SCCMAdmin, and when utilising the SCCM2012 SQL instance on
32 bit server of SQL install proceeds barring warning about 8GB rec, for SQL Server. Then fails on PKI certificate issue. Installation (chose HTTP for MP). I beleive the PKI failure as install starts is
due to the fact that SCCM 2012 needs its database server to b 64 bit ?
Thus i then tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account SCCMAdmin, and
when using the SCCM2012 SQL instance on
64 bit server of SQL install proceeds but fails at checking stage and says:
SQL Server sysadmin rights FAILED SQL3.Domain_Name
Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup
cannot continue.
and
Site System to SQL Server communication WARNING SCCM.Domain_Name
A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL
Server instance hosting the site database. Setup cannot continue.
Why does the install of SCCM 2012 with 32 bit SQL proceed further than the install with 64 bit SQL, with the latter process failing as above error meesages show and yet both servers are set identically (apart from temporary turning off Firewall on the 64
bit server) and during the install the Databse Server specified is accepted ?

Thanks for the reply.
I can connect via ODBC to the the 32 bit SQL Server and the 64 bit SQL Server from the SCCM Server
The SQL Server Unit called SQL3 unit is a 64 bit SQL.
The SQL Server Unit called SQL is only 32 bit, but at least gets past the final checking stage and the error messages about sysadmin rights and Site System to SQL Server communication problem, and then fails with PKI certificate error message.
When trying to install SCCM specifying the 64 bit SQL Server as the Database Server it gives the 2 error messages at the final checking stage of the installation as listed.
So as I said what is confusing is the fact that if the SCCM install uses the remote 32 bit SQL Server it passes the final checking (although fails with PKI certificate message) but the 64 bit SQL Server set up exactly the same apart from the Firewall being
left off for the time being, fails at the final check stage with the 2 listed errors.
If I use a local 64 bit SQL Server the installation is fine.
Still would like to find out what cause the 2 issues for the remote 64 bit SQL Server, when ODBC seems fine, sysadmin rights have been given for the installer account and the SCCM computer account and SPNs have been set for the user account running the SQL
Services.

Suppress Powershell Warning in agent job "WARNING: Could not obtain SQL Server Service information"

Hi
I get this warning running through powershell_ise but through sql agent it just errors out.
The code does everything it is supposed to and I tried everything to completely resolve the warning to no avail.
How do I supress it so sql agent wont error out running powershell code?
Thanks!
WARNING: Could not obtain SQL Server Service information. An attempt to connect to WMI on 'server_name' failed with the following error: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Warning only present when it connects to remote servers, it doesn't produce it for local server. And it does get all info from the remote servers.
Paula

Hi paulata,
According to your description, when you run powershell scripts about the remote machine
in SQL Server Agent job, the warning error will occur. “The common error message is Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).” This suggests that your credentials aren't sufficient for accessing the
remote system. If you have an account that has sufficient permissions for the query, there's a simple workaround for this problem in the form of PowerShell's Get-Credential command and the script's Credential parameter. I recommend you check if your account
has permission on remote machine and it can execute the powershell scripts.
In addition, if you want to run query statement on the remote machine , I recommend you create Linked Server, then do some related operations. There is a similar issue about access denied, you can review the following article.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/157f536d-6716-4547-bdb4-9e3c8451cb95/sql-agent-service-account-permissions-sql-server-2008?forum=sqlgetstarted
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL Server Data Tools - for visual studio 2013

Hi
I have recently installed Visual Studio 2013 and need to install the SQL Server Data Tools too, as I have done in Visual Studio 2012, but I can not find the software, where can I get it?
thanks
MsdnMezzo

Hi,
I hope you serve.Regards
SQL Server Data Tools for Visual Studio 2013 - 12.0.40403.0
Portuguese (Brazil)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/BR/SSDTSetup.exe
Chinese (PRC)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/CN/SSDTSetup.exe
German
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/DE/SSDTSetup.exe
English (United States)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/EN/SSDTSetup.exe
Spanish
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/ES/SSDTSetup.exe
French
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/FR/SSDTSetup.exe
Italian
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/IT/SSDTSetup.exe
Japanese
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/JA/SSDTSetup.exe
Korean
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/KO/SSDTSetup.exe
Russian
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/RU/SSDTSetup.exe
Chinese (Taiwan)
http://download.microsoft.com/download/2/A/4/2A4211D0-AA9B-4496-A9D4-48CDBED5C25C/TW/SSDTSetup.exe

How to edit "license information for multiple logon" screen

hey gurus
i need to know how to edit or modify the 'license information for multiple logon" screen. this screen usually pops up when a user tries for a multiple logon to sap. We have activated the parameter 'login/disable_multi_gui_login' but we would like to modify the screen in such a way that only one radio button which says 'terminate this logon' should exist. we would prefer to remove the option of 'continue with this option and end any other logon'. Now i searched but i could not find anything to implement this so i am here and i need your advice and suggestions.
thanks in advance.
cheers.
nate

hey bernhard
many thanks for your reply..i appreciate your help. its just that its not explicitly mentioned we cant modify the screen in the note.
Is there any other note that specifically say so?
thanks for your time buddy.
regards

SQL Server Dev Environment for Windows 8 Tab

I recently received a Windows 8 Asus tablet running Windows 8 and wanted to know if there was a light weight version of SQL Server that I can use for development when traveling. I am writing alot of stored procedures and am tired of taking my laptop
on trips.

Hi sawyerdad,
According to your description, we need to verify the type of your Asus tablet, windows 8 Surface RT or Surface Pro.
If it is Surface Pro, you can install SQL Server in the tablet base on window 8, Personally, I recommend you install the version of SQL Server according to the hardware and software of the device. Such as the developer version, the developers
can build any kind of application on top of SQL Server. It includes all the functionality of Enterprise edition, but is licensed for use as a development and test system, not as a production server. SQL Server Developer is an ideal choice
for people who build and test applications. If it is Surface RT, it could not install the traditional desktop apps.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Is there any way to find out the dependency information for column of view?

Does Oracle provide some view / table / pl/sql pkgs to find out the dependency information for column of view ?
For example, there are two table mytable1 (col1 varchar2(10), col2 date) & mytable2 (col1 varchar2(10), qty int), and there is one view myView as
select mytable1.col1, col2, qty from mytable1 inner join mytable2 on mytable1.col1 = mytable2.col
Can I get some information such as myView.col1 is come from mytable1.col, myView.col2 is come from mytable1.col2, myView.qty is come from mytable2.qty
?

I can get the information about the columns list in table/view from ALL_TAB_COLUMNS table, but I wish to know the column in the view is come from which original table's column.
Is there any way to find it out from Oracle meta data / through any PL/SQL packages ?

Finding SQL Server licensing information for 2005 and above.

Similar Messages

Maybe you are looking for