Finding the guilty SQL

A number of repots run each month on my database. When they run - performance of the database to users slows down dramatically. How can I find the offending SQL?

You can use Enterprise Manager (Top Sessions)
to determine the offending sql statement. You can also for example, when the slow down is occuring, you could check the data dictionary view 'v$session_long_ops' to determine the offending query (You can join it to the view v$session to figure out the offending user).

Similar Messages

  • How to find the current SQL

    Dear All,
    My testing engineers are checking the application from front end, i have to find the current SQL (What SQL queries are used in the application) statements in the back end.
    Please let me know how to find the current executing SQL stements.
    Thanks in advance
    Mahi

    You need to join this query with one more table - v$sqlstats. There are many statistics in particular cpu_time, elapsed_time etc stored in that table for each sql statement.
    You can join v$sqlstats by sql_id until you have multiple child cursors for single statement.
    Or you can just join to v$sql and get statistics from there and in this latter case you include child_number column to distinguish child cursors from each other.
    Best Regards,
    Alex

  • How to find the backend  SQL query of the JSP page in OIC

    Does anybody how the best way to find the backend SQL QUERY of OIV JSP page?

    How To Generate Trace Files in in HTML/JSP (using Profile Option)
    •     • Note: This requires proper responsibility to set SQL Initialization statement using Profile option.      
         Step 1.     Login to the desired Form application.     
         Step 2.     Select +Profile >> System ('Find System Profile Values' screen will pop up)     
         Step 3.     Check 'User' and Type in the Username (in which the account for that user will be trace)     
         Step 4.     Type 'Initialization%' in the Profile box and Hit 'Find' (Click here for preview.)     
         Step 5.     In the User box, type the following statement and Hit 'Save' (Click here for preview)
         BEGIN FND_CTL.FND_SESS_CTL('','','TRUE','TRUE','','ALTER SESSION SET TRACEFILE_IDENTIFIER = TESTING MAX_DUMP_FILE_SIZE = 5000000 EVENTS ='||''''||' 10046 TRACE NAME CONTEXT FOREVER, LEVEL 12'||'''');END;     
         Note:     specify any name you like to identify your trace, in this case, testing is the end name on the trace. You can also specify the amount of data allowable to be in the trace, in this case, 5000000 is the amount set. Make sure you hit 'Save' afterwards.[Quotes in the statement are all 'Single' quotes.]
              specifying TRACEFILE_IDENTIFIER value is mandatory when setting up the trace using the above profile option value
         Step 6.     Login to HTML / JSP page with username/password and start your flow. (Everything you do once login to HTML / JSP will get trace.)     
         Step 7.     Logout of HTML / JSP application once you completed with your flow.      
         Step 8.     Go back to the Profile option in the Form application and delete the Initialization SQL statement, and Hit 'Save'.     
         Step 9.     Log in to the database server or login server and retrieve your trace file.
         Identify and retrieve the trace file using the tracefile_identifier specified in Step 5.
         In this case the tracefile_identifier is “TESTING”. (Click here for Trace file locations) *     
         Note:     If you need to regenerate your trace or tracing a new flow, then repeat Step 1 to Step 8. To avoid self-confusion, choose a different name for your trace identifier everytime you set to trace.     
         Step 10.     See TKPROF section on how to format trace file into readable text.
         Trace Options Definition
         No Trace          Tracing is not activated
         Activities will not get traced.
         Regular Trace
         (Level 1)          Contains SQL, execution statistics, and execution plan.
         Provides execution path, row counts as well as produces smallest flat file.
         Trace with Binds
         (Level 4)          Regular Trace plus value supplied to SQL statement via local variables.
         Trace with Waits
         (Level 8)          Regular Trace plus database operation timings that the SQL waited to have done in order to complete, i.e. disk access.
         Trace with Binds and Waits
         (Level 12)          Regular trace with both waits and binds information.
         Contains the most complete information and will produce the largest trace file.
    ****Send me an email to [email protected],I will share the document with you.

  • Find the full sql text of the currently executing query

    Hi,
    I wish to find the full sql text of currently executing sql.
    Tried through v$sql and v sqltext_with_newlines but it doesn't give the full sql.
    We do not want to enable trace to get sql query.
    How to get this ?
    Thanks.

    Hye,
    I got my answer on the below link,
    Getting data from sql_fulltext
    Thanks.

  • How to find the main sql

    Hi all,
    I'm working on a 11.2 Oracle Enterprise database.
    I need a query to find the top 10 queries of my database. Please could you help me?
    Best regards
    dbajug

    moreajays wrote:
    Hi,
    AWR will give you all historic sql details
    @?/rdbms/admin/awrsqrpt.sql
    To know current top CPU queries you can use below sql
    col sql_text for a80
    set pages 200
    set line 900
    col PROGRAM for a20
    col MACHINE for a20
    col CPU 9999999999
    alter session set nls_date_format='dd-mon-yyyy hh24:mi:ss';
    col event for a40
    select *
    from (select /*+ rule */
    sa.sql_id,
    sa.CPU_TIME "CPU",
    s.sid "SID",
    s.serial# "SERIAL",
    s.program "PROGRAM",
    s.machine "MACHINE",
    sa.SQL_TEXT "SQL_TEXT",
    vp.spid,
    sw.event,
    s.logon_time,
    s.last_call_et / 60,
    s.username,
    s.status
    from v$sqlarea sa, v$session s, v$process vp, v$session_wait sw
    where sa.address = s.sql_address
    and sw.sid = s.sid
    and s.paddr = vp.addr
    order by CPU_TIME desc)
    where rownum < 10;Thanks,
    Ajay More
    http://www.moreajays.com
    Hey? This query is not going to help.
    Your join condition sa.address = s.sql_address will exclude all SQLs that are not the most recently executed by a session.
    And you are listing the same SQL several times if it is executed by multiple sessions, but taking no account of the number of times it was executed.
    You need to run something much simpler. Perhapsselect sql_text,executions,disk_reads,buffer_gets,cpu_time,elapsed time from v$sql order by....;run it several times, sorting it on each of the projected columns.

  • Where do I find the PL/SQL lines referenced in an error report?

    Hi Folks
    I am trying to deploy a mapping and the deploy step has generated several errors referencing an invalid identifier.
    Well, I know what an invalid identifier is but I can't seem to be able to take the line number that's referenced in the error message and find that line in a PL/SQL script somewhere. If I look at the script under the 'View Script' button in the deployment results window, the line numbers don't match the ones in the error message.
    I'm sure I've left out a reconciliation somewhere but as the mappings get larger and larger it becomes impossible to find the missing link without messing up several other items that are correct to begin with.
    Do I try to look in USER_SOURCE at the database level?
    Seems like a lot more work than it should be.
    Many thanks for the guidance.
    Gary

    Nikolai
    That thread did the trick! Thanks very much.
    I had searched on several key words before posting a new thread but either gave up reading threads too early or just didn't use the right key words.
    How about developing a Vulcan Mind Meld that can be used over the Internet!!!
    Thanks again, you're the best.
    Gary

  • Find the current sql which is running against database

    Hi,
    How to find out the current sql which is running against database?

    Hi,
    You can use V$SESSION_LONG_OPS and V$SQL to get the long running(6 seconds or above) queries. You need to join these two views to get the SQL text.
    V$SESSION_LONGOPS : Will give you the long running SQL ID.
    V$SQL : Will give you the text of query against the SQL ID.
    Refere the below link for more details:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2092.htm#REFRN30227
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_2113.htm#REFRN30246
    Cheers,

  • Finding the issued SQL statement

    Hi All,
    A user has issued this:
    DROP USER user CASCADE;
    and after a while it got hung up.
    Since all database users are using the same schema, I can not find the sid/serial # to kill it. There are many users in active and inactive status are found but could not identify the user who issued the above sql.
    I know I can extract sid,serial# through v$session view. How can I join this view with other views to identify the sql statement?
    Do you know how?
    Thanks,

    To get the SID and SERIAL # please execute the SQL below:
    set lin 500
    col username format a15
    col terminal format a15
    col program format a40
    col machine format a25
    select s.paddr, p.spid, s.sid,s.serial#,s.terminal,s.machine,s.username,s.status,s.process,s.program,s.module,s.action, s.server from v$session s, v$process p
    where p.addr=s.paddr
    order by s.sid
    To get the SQL Statement you have to get the SID and SERIAL # from above statement and execute the SQL below:
    select x.sql_text from v$sql x, v$session y
    where x.hash_value = y.sql_hash_value
    and x.address = y.sql_address
    and y.sid = &sid
    /

  • How to find the existing sql server backup plan/schedule is there a script for that?

    Friends,
    Is there a easy way to find out in SQLServer (for All DB's) what is the current backup plan/schedule ? is there a script for that?
    Thanks,
    Karthikeyan Jothi

    To check the database backup 
    Select
    SERVERPROPERTY('ServerName'),
    db.name,
    CONVERT(VARCHAR(10), b.backup_start_date, 103) + + convert(VARCHAR(8), b.backup_start_date, 14) backup_start_date,
    CONVERT(VARCHAR(10), b.backup_finish_date, 103) + + convert(VARCHAR(8), b.backup_finish_date, 14) backup_finish_date,
    case
    when (DATEDIFF(hour, b.backup_start_date, getdate())<24)then 'Success'
    when (DATEDIFF(hour, b.backup_start_date, getdate())>=24)then 'Failed'
    end Status,
    DATEDIFF(hh, b.backup_finish_date, GETDATE())BackupAgeInHours,
    (b.backup_size/1024/1024/1024 )BackupSize,
    case b.[type]
    WHEN 'D' THEN 'Full'
    WHEN 'I' THEN 'Differential'
    WHEN 'L' THEN 'Transaction Log'
    END Type,
    ISNULL(STR(ABS(DATEDIFF(day, GetDate(),(Backup_finish_date)))), 'NEVER')DaysSinceLastBackup
    FROM sys.sysdatabases db
    Left OUTER JOIN (SELECT * , ROW_NUMBER() OVER(PARTITION BY database_name ORDER BY backup_finish_date DESC) AS RNUM
    FROM msdb.dbo.backupset) b ON b.database_name = db.name AND RNUM = 1
    where dbid<>2
    OR
    SELECT
    DISTINCT
    a.Name AS DatabaseName ,
    CONVERT(SYSNAME, DATABASEPROPERTYEX(a.name, 'Recovery')) RecoveryModel ,
    COALESCE(( SELECT CONVERT(VARCHAR(12), MAX(backup_finish_date), 101)
    FROM msdb.dbo.backupset
    WHERE database_name = a.name
    AND type = 'd'
    AND is_copy_only = '0'
    ), 'No Full') AS 'Full' ,
    COALESCE(( SELECT CONVERT(VARCHAR(12), MAX(backup_finish_date), 101)
    FROM msdb.dbo.backupset
    WHERE database_name = a.name
    AND type = 'i'
    AND is_copy_only = '0'
    ), 'No Diff') AS 'Diff' ,
    COALESCE(( SELECT CONVERT(VARCHAR(20), MAX(backup_finish_date), 120)
    FROM msdb.dbo.backupset
    WHERE database_name = a.name
    AND type = 'l'
    ), 'No Log') AS 'LastLog' ,
    COALESCE(( SELECT CONVERT(VARCHAR(20), backup_finish_date, 120)
    FROM ( SELECT ROW_NUMBER() OVER ( ORDER BY backup_finish_date DESC ) AS 'rownum' ,
    backup_finish_date
    FROM msdb.dbo.backupset
    WHERE database_name = a.name
    AND type = 'l'
    ) withrownum
    WHERE rownum = 2
    ), 'No Log') AS 'LastLog2'
    FROM sys.databases a
    LEFT OUTER JOIN msdb.dbo.backupset b ON b.database_name = a.name
    WHERE a.name <> 'tempdb'
    AND a.state_desc = 'online'
    GROUP BY a.Name ,
    a.compatibility_level
    ORDER BY a.name
    To check the schedule you can try the below script
    https://gallery.technet.microsoft.com/SQL-Jobs-Complete-eabe0050
    --Prashanth

  • Line Chart query...having issues with finding the right SQL...tough query

    This initaial entry was much longer and confusing.
    I'm looking to make ar running total based using time periods...see the link in the last post to get to the demo.apex.com area.
    Rob
    Edited by: bostonmacosx on Feb 14, 2013 1:33 PM

    bostonmacosx wrote:
    Hello there. So I hope I can explain this sufficiently:
    OUT OF THE WAY: 11g 4.1.1
    I'm going to simplify my data so that it is clear what I'm looking to do.
    I want to have a line chart grouped by date. Let's say monthly...this is easy to do if you are dealing with one specific date and some value you can build the series against with case statements. I've done that a million times.
    The columns of data I'm dealing with are as follows:
    CREATE_DT(create date)
    RETIRE_DT(retire date)
    MACHINE_TYPE(type of machine)
    So lets say I want to see a line chart where each line(data point) is a MACHINE_TYPE and each bin is a month. That month should be any machine with a CREATE_DT below then end of the month and a RETIRE_DT which is either Greater then the end of the month or is NULL(ala hasn't been retired yet).
    In the query for a chart which is
    SELECT LINK,LABEL,CASE()"",CASE()"",CASE()"" from TABLE GROUP BY ROLLUP(VALUE)I guess I'm not seeing how to be able to put these values together so that it walks month by month and figures out the values and puts them in the correct "bin" of time along the X axis of the chart.
    I hope I'm being semi clear as it is hard to explain this scenario. Nope. Clear as mud.
    If time is plotted against the X axis, what measure is plotted on the Y?
    =============
    on another note I built this table from the data:
    01-JAN-12     01-FEB-12     01-MAR-12     01-APR-12     01-MAY-12     01-JUN-12     01-JUL-12     01-AUG-12     01-SEP-12     01-OCT-12     01-NOV-12     01-DEC-12     01-JAN-13     ENVOS
    59     59     59     59     59     59     59     59     59     59     59     60     60      Alias
    12     26     26     26     26     26     26     26     26     26     26     26     26      Blade
    9     9     9     9     9     9     9     9     9     9     9     9     9      DataMvrUsing the function:
    create or replace FUNCTION ACTIVE_SYSTEMS
    RETURN VARCHAR2
    is
    var1 VARCHAR2(4000):= '';
    start_date DATE:= to_Date('05-JAN-2012','DD-MON-YYYY');
    end_date DATE:= to_Date('08-JAN-2013','DD-MON-YYYY');
    new_start_date DATE;
    BEGIN
    new_start_date:=trunc(start_date,'MONTH');
    var1 := q'!SELECT !';
    while(new_start_date<end_date)
    LOOP
    var1 := var1 || q'! count(case when create_dt<'!'||to_char(new_start_date,'DD-MON-YY')||q'!' and (retire_dt IS NULL or retire_dt>'!'||to_char(new_start_date,'DD-MON-YY')||q'!') then 1 end) "!' ||to_char(new_start_date,'DD-MON-YY')||q'!",!';
    new_start_date:= add_months(new_start_date,1);
    END LOOP;
    var1 := var1 || q'! CMS_NODE_OS.OS_TYPE||' '||node_env as envos from CMS.CMS_NODE LEFT join CMS.CMS_NODE_OS on CMS.CMS_NODE.NODE_NAME=CMS.CMS_NODE_OS.NODE_NAME where retire_dt is NULL group by rollup(CMS_NODE_OS.OS_TYPE||' '||node_env)!';
    RETURN var1;
    END;
    Instead of inadequate attempts to explain this here with fragments of code that we can't do anything with because we don't possess the objects and data they're based on, show us something. Create the objects and some sample data in a workspace on apex.oracle.com and post guest developer credentials. Sketch the required chart or mock it up in a spreadsheet and upload it as an image or PDF so we can see what you're aiming for.

  • How to find where the below sql is used in database

    Hi all,
    I am tring to find the below SQL in our data base where it is used?
    I had done the checking in all reports manually, But have no luck.
    But i am sure that the below sql is in our data base and having some issue on it.
    Can any one please let me know how to find where the below query is used in our database? I mean in packages/ triggers/ procedures or any where in our database
    Please find the query
    select count(sh.shipment_gid) from SHIPMENT sh, SHIPMENT_TYPE stp, LOCATION ld where (sh.shipment_gid in (select sstop.shipment_gid from SHIPMENT_STOP sstop where (sstop.appointment_delivery > trunc(TO_DATE(:1, :2), :3)) and (sstop.appointment_delivery is not null))) and (sh.is_to_be_held=:"SYS_B_0") and (sh.domain_name=:4) and (sh.insurance_policy_number like :"SYS_B_1") and (sh.perspective=:"SYS_B_2") and (sh.shipment_type_gid=stp.shipment_type_gid) and (sh.dest_location_gid=ld.location_gid(+)) and (stp.shipment_type_xid!=:5) order by ld.location_name, sh.start_time
    Regards,
    Dpk

    There is video demonstration how to import from data dictionary.
    After import you can select from the main menu: View->DDL File Editor menu item to open the DDL dialog and then click on "Generate" button on the dialog. When the DDL is generated you can search in it using "Find" button.
    Ivan

  • How can we find the most usage and lowest usage of table in Sql Server by T-SQL

    how can we find the most usage and lowest usage of table in Sql Server by T-SQL
    The table has time stamp column
    StartedOn datetime
    EndedOn datetime

    The Below query has been used , but the textdata column doesnot include the name of the table ServiceLog.
    SELECT
    FROM
    databasename,
    duration
    fn_trace_gettable('F:\Program
    Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\log_148.trc',
    default)
    WHERE
    DATABASENAME='ZTCFUTURE'
    AND TEXTDATA
    IS
    NOT
    NULL
    --AND TEXTDATA LIKE 'SERVICE%'
    order
    by cpu
    desc; 

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      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:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      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\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\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:                       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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       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:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 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.
    2014-04-03 14:14:28.38 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.
    2014-04-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 
    ERRORREPORTING="False"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 
    X86="False"
    ; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
    (RS). 
    INSTANCENAME="MSSQLSERVER"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 
    SQMREPORTING="False"
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process. 
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned. 
    ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; Startup type for the SQL Server service. 
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express. 
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine. 
    SQLCOLLATION="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol. 
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol. 
    NPENABLED="0"
    ; Startup type for Browser Service. 
    BROWSERSVCSTARTUPTYPE="Automatic"
    ; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 
    RSSVCACCOUNT="NT Service\ReportServer"
    ; Specifies how the startup mode of the report server NT service.  When 
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled 
    RSSVCSTARTUPTYPE="Automatic"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • SQL Server Express 2014 on Win8.1: Could not find the Database Engine startup handle

    Hello,
    I tried to follow all the similarly titled posts in this forum, yet no solution seems to work, so I hope I can find some up-to-date suggestion here (most of the older posts refer to versions from 2008 to 2012...).
    I have installed Visual Studio 2013 (with the latest Update 2 RC) on a freshly installed development workstation with Win 8.1 with all its updates. Now I'd want to install SQL Server 2014 Express, but the setup keeps failing with the dreaded "Could
    not find the Database Engine startup handle" error (the log follows below).
    What I tried:
    1) download again and repair. Same error.
    2) completely uninstall by launching setup.exe /Action=uninstall (success), then rebooting the OS, then installing again. Same error. I did this twice, the second time I also manually removed any directory left out in C:\Program Files etc.
    When I launch the setup, I select all the components for installation in the package SQLEXPRADV_x64_ENU.exe (1.12 GB, last downloaded today -Apr 3, 2014-), and accept all the defaults including the proposed services accounts. There is no preexisting
    SQL Server instance, as expected.
    The setup takes its time, and finally fails with the error quoted above. I really do not want to reformat my HD and fully reconfigure my workstation, which took about 3 days... Could anyone suggest a solution to have SQL Server 2014 setup so I can start
    developing instead of wasting time in administering the system?
    Thanks to all! The log follows.
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 18:30:58
      End time:                      2014-04-03 19:04:41
      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 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:                  DIOMEDES
      Machine processor count:       4
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Daniele\Downloads\SQLEXPRADV_x64_ENU\x64\setup\
      Installation edition:          Express
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Disabled
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CLTCTLRNAME:                   <empty>
      CLTRESULTDIR:                  <empty>
      CLTSTARTUPTYPE:                0
      CLTSVCACCOUNT:                 <empty>
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 <empty>
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             
      CTLRSTARTUPTYPE:               0
      CTLRSVCACCOUNT:                <empty>
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     <empty>
      ENABLERANU:                    true
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
      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:                  Latin1_General_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           DIOMEDES\Daniele
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\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:                       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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       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:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       LocalDB
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\SystemConfigurationCheck_Report.htm

    Thank you, it worked! I suppose that it was really your nr.3 which made the difference. I changed NT Service\MSSQL$SQLEXPRESS to NT AUTHORITY\System for the Data service. I'll then change it again as suggested (any suggestion about a "standard"
    account to be used here?), even if this is a development workstation using SQL Server Express only as a local database for debugging, so security is not really a big concern.
    Thanks for the feedback.Ya I know No3 was real step but just added more info so as to rule out any other possibility.
    No not as such, you wont believe,quite few pf my clients I have worked for keep it with local system and they have not complained yet ,they are afraid to change account as few of them faced issue SQL Server not coming online due to logon failure( after changing
    startup account to some domain a and that was happening due to some AD policy.But if you have nay plans to move Critical database in production which would be act as Database to some Internet facing application please follow my suggestion
    of running SQL Server with Least privileged domain account.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • How to find out the failed sql command and its data from DEFERROR

    Hi,
    has anybody a procedure or some other possibilities to read the content of column USER_DATA of the advanced replication view DEFERROR in order to find out the failed sql command and its column values?
    Thanks in advance.

    Hi Vishwa,
                 The control would be something like this for navigation in Get_p_xxx method u mention as link and u mention a event name which gets triggered on the click of this hyperlink. So your GET_P_XXX method would have the following code:
    CASE iv_property.
        WHEN if_bsp_wd_model_setter_getter=>fp_fieldtype.
          rv_value = cl_bsp_dlc_view_descriptor=>field_type_event_link.
        WHEN if_bsp_wd_model_setter_getter=>fp_onclick.
          rv_value = 'EXAMPLE'.
    Now you have to create a method as EH_ONEXAMPLE at your IMPL class and within which you would give an outbound plug method. Within the outbound plug the target data would be filled in the collection and window outbound plug would be triggered.
    This is a huge topic and  i have just mentioned you basic things.
    Regards,
    Bharathy.

Maybe you are looking for

  • TS1382 songs are playing from bottom to top instead of top to bottom in playlist - remedy?

    songs are playing from bottom to top instead of top to bottom in playlists...any remedy?

  • Download full version not downloader

    The automatic updater is not working. Not sure why, maybe my company is blocking it. If I uninstall Firefox so I can download the full program from the Mozilla website, the link only downloads an installer which attempts to download Firefox, but fail

  • Help with Date/Calendar classes

    What is the best way to get the current date/time from the user's system? On my system I use: Date rightnow = new Date(); and this gives the correct time/date/timezone. But it says in the documentation to use Calendar instead, and when i do that ala:

  • Regarding jdk interpretor

    I have installed jdk1.6 recently.it compile the .java file successfully but fail to interpret.whenever i m trying to interpret its giving below error.i had created classpath of it too. Exception in thread "main" java.lang.UnsupportedClassVersionError

  • CRM DataSource Enhancement

    Hi, I need to add a field to one CRM datasource(0CRM_SALES_ACT_1).I have done that using RSA6.Also written a code in 'EXIT_SAPLRSAP_001'. The delta queue for this DataSource is working properly on CRM side but when I pull the same data to BW side it