SQL Server Express causing log in difficulties....

All-
Well, I'm not out of the woods yet. I've discovered that my issues of logging in to RHS Config Manager (admin/admin, but then nothing happens when I click Sign-In) returns when I select SQL Server Express. This despite the fact that the Config Mgr's Test Connection function shows success (see graphic below). Any ideas what might be going on?
BTW, is there any source which shows screen shots of EXACTLY how SQL Server Express, Tomcat, and RH Server needs to be set up? I see that others in the forum have had similar frustration with this question.

What do you mean by 3rd party libraries? Is the normal oledb provider using
SMO fine to your requirement?
I believe your question would be a better one in a dedicated C++ forum.

Similar Messages

  • SQL Server Express Performance Limitations With OGC Methods on Geometry Instances

    I will front load my question.  Specifically, I am wondering if any of the feature restrictions with SQL Server Express cause performance limitations/reductions with OGC methods on geometry instances, e.g., STIntersects?  I have spent time reading
    various documents about the different editions of SQL Server, including the Features Supported by the Editions of SQL Server 2014, but nothing is jumping out at me.  The
    limited information on spatial features in the aforementioned document implies spatial is the same across all editions.  I am hoping this is wrong.
    The situation....  I have roughly 200,000 tax parcels within 175 taxing districts.  As part of a consistency check between what is stored in tax records for taxing district and what is identified spatially, I set up a basic point-in-polygon query
    to identify the taxing district spatially and then count the number of parcels within in taxing district.  Surprisingly, the query took 66 minutes to run.  As I pointed out, this is being run on a test machine with SQL Server Express.
    Some specifics....  I wrote the query a few different ways and compared the execution plans, and the optimizer always choose the same plan, which is good I guess since it means it is doing its job.  The execution plans show a 'Clustered Index Seek
    (Spatial)' being used and only costing 1%.  Coming in at 75% cost is a Filter, which appears to be connected to the STIntersects predicate.  I brute forced alternate execution plans using HINTS, but they only turned out worse, which I guess is also
    good since it means the optimizer did choose a good plan.  I experimented some with changing the spatial index parameters, but the impact of the options I tried was never that much.  I ended up going with "Geometry Auto Grid" with 16 cells
    per object.
    So, why do I think 66 minutes is excessive?  The reason is that I loaded the same data sets into PostgreSQL/PostGIS, used a default spatial index, and the same query ran in 5 minutes.  Same machine, same data, SQL Server Express is 13x slower than
    PostgreSQL.  That is why I think 66 minutes is excessive.
    Our organization is mostly an Oracle and SQL Server shop.  Since more of my background and experience are with MS databases, I prefer to work with SQL Server.  I really do want to understand what is happening here.  Is there something I can
    do different to get more performance out of SQL Server?  Does spatial run slower on Express versus Standard or Enterprise?  Given I did so little tuning in PostgreSQL, I still can't understand the results I am seeing.
    I may or may not be able to strip the data down enough to be able to send it to someone.

    Tessalating the polygons (tax districts) is the answer!
    Since my use of SQL Server Express was brought up as possibly contributing to the slow runtime, the first thing I did was download an evaluation version of Enterprise Edition.  The runtime on Enterprise Edition dropped from 66 minutes to 57.5 minutes.
     A reduction of 13% isn't anything to scoff at, but total runtime was still 11x longer than in PostgreSQL.  Although Enterprise Edition had 4 cores available to it, it never really spun up more than 1 when executing the query, so it doesn't seem
    to have been parallelizing the query much, if at all.
    You asked about polygon complexity.  Overall, a majority are fairly simple but there are some complex ones with one really complex polygon.  Using the complexity index discussed in the reference thread, the tax districts had an average complexity
    of 4.6 and a median of 2.7.  One polygon had a complexity index of 120, which was skewing the average, as well as increasing the runtime I suspect.  Below is a complexity index breakdown:
    Index
    NUM_TAX_DIST
    1
    6
    <2
    49
    <3
    44
    <4
    23
    <5
    11
    <6
    9
    <7
    9
    <8
    4
    <9
    1
    <10
    4
    >=10
    14
    Before trying tessellation, I tweaked the spatial indexes in several different ways, but the runtimes never changed by more than a minute or two.  I reset the spatial indexes to "geometry auto grid @ 32" and tried out your tessellation functions
    using the default of 5000 vertices.  Total runtime 2.3 minutes, a 96% reduction and twice as fast as PostgresSQL!  Now that is more what I was expecting before i started.
    I tried using different thresholds, 3,000 and 10,000 vertices but the runtimes were slightly slower, 3.5 and 3.3 minutes respectively.  A threshold of 5000 definitely seems to be a sweet spot for the dataset I am using.  As the thread you referenced
    discussed, SQL Server spatial functions like STIntersect appear to be sensitive to the number of vertices of polygons.
    After reading your comment, it reminded me of some discussions with Esri staff about ArcGIS doing the same thing in certain circumstances, but I didn't go as far as thinking to apply it here.  So, thanks for the suggestion and code from another post.
     Once I realized the SRID was hard coded to 0 in tvf_QuarterPolygon, I was able to update the code to set it to the same as the input shape, and then everything came together nicely.

  • 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 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

  • Problem with Datasource for SQL Server Express

    I have set up a development environment to develop some processes for the HCSO client and have a question.  I have a turnkey install on my laptop with MYSQL.  The liveCycle databases are in MYSQL.  I have also installed SQL Server Express on this machine and created a table to query that will control workflow.  I added a datasource configuration in the adobe-ds.xml configuration file.  That configuration is:
    <local-tx-datasource>
                <jndi-name>HCSO</jndi-name>
                <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=DBName</connection-url>
                <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
                <user-name>username</user-name>
                <password>password</password>
                <min-pool-size>1</min-pool-size>
                <max-pool-size>30</max-pool-size>
                <blocking-timeout-millis>60000</blocking-timeout-millis>
                <autoReconnect>true</autoReconnect>
                <idle-timeout-minutes>15</idle-timeout-minutes>
                <prepared-statement-cache-size>100</prepared-statement-cache-size>
                <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
                <new-connection-sql>Select id from HCSOUser.eric</new-connection-sql>
                <check-valid-connection-sql>Select id from HCSOUser.eric</check-valid-connection-sql>
                <metadata>
                      <type-mapping>MS SQLSERVER2000</type-mapping>
                </metadata>
          </local-tx-datasource>
    In SQL Server, I created a user and a schema with the same name in a database.  I created a simple table called "eric" with one column called "id".  The user was given the appropriate default schema and given full permissions on the database and table.
    In workbench, I added a JDBC query single row activity.  I have configured the datasource as java:/HCSO and also tried java:HCSO.  I then entered the query as "Select id from HCSOUser.eric" and hit test.  Nothing appears in the results area.  I see the following in the server.log:
    2009-09-24 14:44:26,437 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterLocal.doBMT(com.ad obe.idp.dsc.transaction.TransactionCallback) throws com.adobe.idp.dsc.DSCException:
    java.lang.RuntimeException: A result set was generated for update.
          at com.adobe.idp.dsc.jdbc.JDBCService.testExecute(JDBCService.java:616)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:592)
          at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
          at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
          at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
          at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
          at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doBMT(EjbTran sactionBMTAdapterBean.java:197)
          at sun.reflect.GeneratedMethodAccessor573.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:592)
          at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
          at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:214)
          at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
          at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor. java:54)
          at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
          at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
          at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 58)
          at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62)
          at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:154)
          at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:153)
          at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
          at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:122)
          at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
          at org.jboss.ejb.Container.invoke(Container.java:873)
          at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:415)
          at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:88)
          at $Proxy270.doBMT(Unknown Source)
          at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:95)
          at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
          at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
          at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
          at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
          at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
          at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
          at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:132)
          at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
          at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
          at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
          at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
          at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
          at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.invoke(AbstractMessageReceiv er.java:315)
          at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invokeCall(SoapSdkEndpoint. java:138)
          at com.adobe.idp.dsc.provider.impl.soap.axis.sdk.SoapSdkEndpoint.invoke(SoapSdkEndpoint.java :81)
          at sun.reflect.GeneratedMethodAccessor710.invoke(Unknown Source)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:592)
          at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
          at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
          at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
          at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
          at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
          at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
          at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
          at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
          at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
          at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:252)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at com.adobe.idp.dsc.provider.impl.soap.axis.InvocationFilter.doFilter(InvocationFilter.java :43)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:202)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
          at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
          at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.ja va:159)
          at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11P rotocol.java:744)
          at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
          at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
          at java.lang.Thread.run(Thread.java:595)
    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: A result set was generated for update.
          at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
          at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
          at com.microsoft.sqlserver.jdbc.SQLServerStatement$StatementExecutionRequest.executeStatemen t(Unknown Source)
          at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)
          at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
          at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(Unknown Source)
          at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:161)
          at com.adobe.idp.dsc.jdbc.helper.SqlHelper.executeTestUpdate(SqlHelper.java:117)
          at com.adobe.idp.dsc.jdbc.JDBCService.testExecute(JDBCService.java:610)
          ... 82 more

    Thanks fot the tip, but now I got a different message in the "Test" results of "Query Single Row":
    Exception: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host  has failed. java.net.ConnectException: Connection refused: connect); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host  has failed. java.net.ConnectException: Connection refused: connect))
    My datasource xml is like this:
    <?xml version="1.0" encoding="UTF-8"?>
            <datasources>
            <local-tx-datasource>
            <jndi-name>MSSQL</jndi-name>
            <connection-url>jdbc:sqlserver://localhost:1433;DatabaseName=ADOBE</connection-url>
              <use-java-context>false</use-java-context>
            <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
            <user-name>sa</user-name>
            <password>adobe</password>
              <min-pool-size>10</min-pool-size>
              <max-pool-size>50</max-pool-size>
              <blocking-timeout-millis>60000</blocking-timeout-millis>
              <idle-timeout-minutes>15</idle-timeout-minutes>
              <prepared-statement-cache-size>100</prepared-statement-cache-size>
              <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
            <check-valid-connection-sql>SELECT 1 FROM sysobjects</check-valid-connection-sql>
            <metadata>
              <type-mapping>MS SQLSERVER2005</type-mapping>
            </metadata>
            </local-tx-datasource>
            </datasources>        
    Where is the problem and how to fix it?
    Thank you.

  • SQL Server Express 2008 instance fails to start

    I've installed SQL Server Express with a named instance 'SQLSERVER2'. I was able to connect to it and reference it in the management studio. There was a problem though with Visual Studio 9 when running an ASP.NET web application that required connecting to the same instance. So, I went into the configuration manager to change the security level of the instance from network to local service. The change went through but could not restart the instance. That is what has created my next round of problems. I can't go in and change it back to network because the instance is permanently stopped. I cannot start it with the services manager. How can I fix this?
    Here is the connection log:
    2009-12-21 11:36:32.20 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
     Jul  9 2008 14:43:34
     Copyright (c) 1988-2008 Microsoft Corporation
     Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
    2009-12-21 11:36:32.50 Server      (c) 2005 Microsoft Corporation.
    2009-12-21 11:36:32.51 Server      All rights reserved.
    2009-12-21 11:36:32.51 Server      Server process ID is 21856.
    2009-12-21 11:36:32.51 Server      Authentication mode is MIXED.
    2009-12-21 11:36:32.53 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG'.
    2009-12-21 11:36:32.89 Server      This instance of SQL Server last reported using a process ID of 3216 at 12/18/2009 6:06:56 PM (local) 12/19/2009 2:06:56 AM (UTC). This is an informational message only; no user action is required.
    2009-12-21 11:36:32.89 Server      Registry startup parameters:
      -d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\master.mdf
      -e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG
      -l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\mastlog.ldf
    2009-12-21 11:36:33.26 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2009-12-21 11:36:33.29 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2009-12-21 11:36:35.15 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.
    2009-12-21 11:36:36.64 Server      Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2009-12-21 11:36:37.42 spid6s      Starting up database 'master'.
    2009-12-21 11:36:38.98 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS2'.
    2009-12-21 11:36:39.40 spid6s      SQL Trace ID 1 was started by login "sa".
    2009-12-21 11:36:39.50 spid6s      Starting up database 'mssqlsystemresource'.
    2009-12-21 11:36:39.59 spid6s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
    2009-12-21 11:36:40.14 spid10s     Starting up database 'model'.
    2009-12-21 11:36:40.17 spid6s      Server name is 'USER-F19E13BA9B\SQLEXPRESS2'. This is an informational message only. No user action is required.
    2009-12-21 11:36:40.56 spid6s      Informational: No full-text supported languages found.
    2009-12-21 11:36:40.57 spid6s      Starting up database 'msdb'.
    2009-12-21 11:36:40.60 Server      Error: 17190, Severity: 16, State: 1.
    2009-12-21 11:36:40.60 Server      FallBack certificate initialization failed with error code: 1.
    2009-12-21 11:36:40.70 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
    2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
    2009-12-21 11:36:40.71 Server      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.
    2009-12-21 11:36:40.71 Server      Error: 17826, Severity: 18, State: 3.
    2009-12-21 11:36:40.71 Server      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.
    2009-12-21 11:36:40.71 Server      Error: 17120, Severity: 16, State: 1.
    2009-12-21 11:36:40.71 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Hi,
    This problem can occur if the new Service Account does not have a profile on the machine. To resolve the issue connect to the SQL Server machine using the New Service account. This will create a profile for the user.
    SQL Server creates a self-generated certificate if a certificate is not explicitly specified and/or is not installed. This information is saved in the profile for the SQL Server service account. If the profile has not been created then SQL cannot register the self-generated certificate.
    If there are any more questions, please let me know.
    Thanks.
    ***Xiao Min Tan***Microsoft Online Community***
    What 'New Service account' are you referring to? SQL Server Express resides on my PC where I'm logged on as administrator. I don't know what you mean by connecting to the server. I only know about connecting to the database instance which is the root of the this problem because it can't be started. Sorry for my confusion...

  • SQL Server Express 2008 no longer accepting remote connections

    Last night our SQL Server Express 2008 (running on Windows 2003 server) stopped accepting remote connections. 
    1. We restarted the SQL Server -- no resolution.
    2. We rebooted the host Windows 2003 server - no resolution.
    3. telnet localhost 1433: says Could not open connection to the host on port 1433... connection failed.
    4. netstat -an indicates that the server is not listening on port 1433
    5. SQL Server Network Configuration -> Protocols for SQLEXPRESS2008A -> (properties) -> TCP-IP (enabled), Listen All (yes)
    6. SQL Native Client 10.0 Configuration -> Client Protocols -> (properties) TCP-IP (enabled), Default port (1433)
    Fragment from the server error log:
    2014-03-26 08:50:41.09 Server      A self-generated certificate was successfully loaded for encryption.
    2014-03-26 08:50:41.11 Server      Server is listening on [ 'any' <ipv4> 1026].
    2014-03-26 08:50:41.11 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS2008A ].
    2014-03-26 08:50:41.11 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS2008A\sql\query ].
    2014-03-26 08:50:41.11 Server      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.
    2014-03-26 08:50:41.11 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-03-26 08:50:41.11 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-03-26 08:50:41.29 spid10s     Clearing tempdb database.
    2014-03-26 08:50:41.89 spid10s     Starting up database 'tempdb'.
    2014-03-26 08:50:42.09 spid13s     The Service Broker protocol transport is disabled or not configured.
    2014-03-26 08:50:42.09 spid13s     The Database Mirroring protocol transport is disabled or not configured.
    2014-03-26 08:50:42.14 spid13s     Service Broker manager has started.
    2014-03-26 08:50:42.14 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-03-26 08:50:53.48 spid51      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2014-03-26 08:50:53.48 spid51      Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_enumerrorlogs'. This is an informational message only; no user action is required.
    2014-03-26 08:51:35.68 spid54      Starting up database 'Web TimeSheet2'.
    2014-03-26 08:51:38.47 spid54      Recovery is writing a checkpoint in database 'Web TimeSheet2' (6). This is an informational message only. No user action is required.
    Note: the lines referring to xpstar.dll is new after this porblem.  Previous logs do not have this,Any help will be appreciated.

    Hi,
    >>Server is listening on [ 'any' <ipv4> 1026].
    Your sql server is not listening on default port 1433 but on 1026.When you connect to instance like hostname\instancename you should specify post no also.
    like hostname\instancename ,1026
    Can you try this.Makes sure TCP/IP and named pipes protocol is enabled
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Can't install sql server express

    HElp!!!
    I'm trying to install any recent free sql server.. to practice with vs2012 and asp.net mvc.. and the install keeps failing.  THis is my personal desktop running 64bit Windows 7.  sql server express "said" it was installing but sql
    server doesn't show up under Start/all programs and SWL server management studio isn't under administrative tools.  I tried sql server express but it said it wouldn't install on 64 bit -- something about WOW.  Several sql server things are listed
    in control panel and I'm trying to uninstall them to start over.   Please point me to place to get sql server express with hopefully instructions to install.  Buying a 32 bit computer is not an option at this time.
    Thanks in advance,
    Kay

    problems: 1. no menu item for "new table" in sql server management studio (Right click on tables)
    2. Can't attach northwind db and won't create it using script.  missing stored procedure 'sp_dboption'
    Hi,
    Based on your description, firstly, we need to verify  if  there is no option of ‘New Table’ when right-clicking ‘Tables’ in the left panel of SQL Server Management Studio (SSMS), or you cannot create new table via the GUI in the right panel as follows.
    They might be caused by incomplete installation, I recommend you to check if you have installed the SQL Server 2012 completely.
    Secondly, are you trying to attach the NORTHWIND sample database with the sp_dboption in SSMS? If so, the sp_dboption has been deprecated in SQL Server 2012, it’s only supported in SQL Server 2008 or prior version, you can use
    ALTER DATABASE NORTHWIND SET RECOVERY SIMPLE to replace the following lines in the
    instnwnd.sql script, then execute it. I have done a test successfully in SQL Server 2012. 
    exec sp_dboption 'Northwind','trunc. log on chkpt.','true'
    exec sp_dboption 'Northwind','select into/bulkcopy','true'
    In addition, according to the message “visual studio 2013 does NOT recognize the server”, it seems that you encounter the connection issue between Visual Studio and SQL Server. If you get some error messages, you can post them for further analysis. Also, you
    need to verify that the connection string (contains server name, login, password and so on) is correct when connecting to the SQL Server from Visual Studio.
    Thanks
    Lydia Zhang

  • Error Installing SQL Server Express 2008: '' is not a valid login or you do not have permission.

    I have tried installing SQL Server 2008 multiple times on my machine, and I always receive this error about 3/4 of the way through: '' is not a valid login or you do not have permission.
    I have tried installing both SQL Server Express 2008 with Tools and SQL Server Express 2008 with Advanced Services, and they both fail the same way. I am trying to do a new stand-alone installation.
    I'm running Windows XP Home Edition SP3.
    Looking into the error, some forums say I have to install it from THE Administrator account, and not an account with administrator permissions; it also cannot be in Safe Mode, because then the Windows Installer won't work. Unfortunately, I haven't been able to login to the Administrator account. I can go to the home login screen, do ctrl+alt+del twice, and attempt to login to the Administrator account, but I receive this error: Unable to Log You on because of an Account Restriction.
    Other forums say that in the Server Configuration section, all you have to do is provide the username and a strong password from an administrative account on the computer, and it doesn't have to be THE Administrator. Well, I did that, but for some reason it doesn't recognize my username and password, it says something like "The credentials you provided for the SQL Server Agent are invalid". BUT THOSE ARE THE CORRECT CREDENTIALS FOR MY ADMINISTRATIVE USER! So I'm forced to use one of the accounts without a password, like NT AUTHORITY\SYSTEM. That's the only way I can get past this step.
    Also, just FYI, on the next step, which is Database Engine Configuration, I am using Mixed Mode for the Security Mode. I AGAIN provide a password, and then add my current user (who IS an administrator on my machine!) to the SQL Server Administrators box.
    But yet, it fails every single time.
    This is pathetic and ridiculous. I must have tried to install this thing 15 times, that is not an exaggeration. I'm posting this on several other forums as well, maybe an MVP or Bill Gates himself can help me.
    I have one of the log files from a failed installation. If someone would like to see it, I will post it.

     Papy Normand wrote:
    Hello,
    Please, could you have a look on the excellent answer of Mike Wachal you will find here :
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=4160294&SiteID=1
    Don't hesitate to post again for more help or explanations
    Have a nice day
    PS : if you are talking about the Sql Server Agent Service, it is disabled for Sql Server Express. It is enabled only for the Workgroup/Standard/Dev and Entreprise Editions
    Sorry, but I've tried the suggestion in that link, and it hasn't helped me.
    For anyone wonder, the link is talking about the problem in Server Configuration where I enter my Windows user account and password (which is in the Administrative group), but it says the credentials are invalid.  The link suggests that you need to either enter your Windows account (which I did, and it wouldn't let me go to the next step), or to use one of the built in accounts (which I also tried, but it gave me the " '' is not a valid login" error during the installation).
    Any other ideas?
    I haven't had any answers from any other forums either, so I'll just post my log file in case anyone wants to look at this:
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068643839
      Exit facility code:            1203
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2008-11-17 11:13:47
      End time:                      2008-11-17 12:17:25
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xBE029E38%400x12C2466D
    Machine Properties:
      Machine name:                  STEVEN
      Machine processor count:       2
      OS version:                    Windows XP
      OS service pack:               Service Pack 3
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         D:\x86\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            STEVEN\Steven
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
      ENABLERANU:                    False
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      MEDIASOURCE:                   D:\
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           STEVEN\Steven
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x12C2466D
      Configuration error description: '' is not a valid login or you do not have permission.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x12C2466D
      Configuration error description: '' is not a valid login or you do not have permission.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x12C2466D
      Configuration error description: '' is not a valid login or you do not have permission.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
      Feature:                       Analysis Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:      0x12C2466D
      Configuration error description: '' is not a valid login or you do not have permission.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\Detail.txt
      Feature:                       Integration Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Books Online
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync Framework
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081117_110917\SystemConfigurationCheck_Report.htm

  • SQL Server Express intermittent installation issue

    Have been seeing this error for several months trying to duplicate and troubleshoot. SQL Server 2008 R2 SP2 Express being installed on Windows 7 (x86 or x64) Professional, various processors, various execution environments (VM and non-VM). Yesterday duplicated
    on x86 Win7 Pro VM clean install (installed Win7 Pro, loaded all updates except .NET 4.5, and installed my application). App installer copies .NET 4, Visual Studio 2010 C++ run-time, and then SQL Server 2008 R2 SP2. Below is portion of detail.txt from
    setup failure log:
    2014-07-12 18:22:17 Slp: ----------------------------------------------------------------------
    2014-07-12 18:22:17 Slp: Running Action: SqlEngineDBStartConfigAction_install_configrc_Cpu32
    2014-07-12 18:22:17 Slp: Action Data:
    2014-07-12 18:22:17 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu32
    2014-07-12 18:22:17 Slp:   Scenario = install
    2014-07-12 18:22:17 Slp:   Timing = ConfigRC
    2014-07-12 18:22:17 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig
    2014-07-12 18:22:17 Slp:   FeatureName = SQL_Engine_Core_Inst
    2014-07-12 18:22:17 Slp:   FeatureCpuType = Cpu32
    2014-07-12 18:22:17 Slp:   FeaturePackageId = sql_engine_core_inst
    2014-07-12 18:22:17 Slp:   SlipstreamInstall = 1
    2014-07-12 18:22:17 SQLEngine: --SqlEngineDBStartConfig: Install: SqlEngineDBStartConfig Configuration
    2014-07-12 18:22:17 SQLEngine: : Action Scenario: Install, Feature Scenario: Install, Resolved Scenario Install
    2014-07-12 18:22:17 Slp: Sco: Attempting to get network service account name
    2014-07-12 18:22:17 Slp: Sco: Attempting to get NT account from sid S-1-5-20
    2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-20
    2014-07-12 18:22:17 Slp: Sco: Attempting to get network service account name
    2014-07-12 18:22:17 Slp: Sco: Attempting to get NT account from sid S-1-5-20
    2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-20
    2014-07-12 18:22:17 Slp: Sco: Attempting to get account sid for user account NT AUTHORITY\NETWORK SERVICE
    2014-07-12 18:22:17 Slp: Sco: Attempting to get sid for user account NT AUTHORITY\NETWORK SERVICE
    2014-07-12 18:22:17 Slp: Sco: GetSidForAccount normalized accountName NT AUTHORITY\NETWORK SERVICE parameter to NT AUTHORITY\NETWORK SERVICE
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.ActiveNode =
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.IsActiveNodeUpgraded = False
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.Version =
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.IsDefaultInstance = False
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.InstanceId = MSSQL10_50.SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.ReferenceInstanceId = MSSQL10_50.SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.InstanceName = SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: container.SqlServerServiceName = MSSQL$SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --ProductProperties: Retrieving product properties from local node.
    2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
    2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value ProductCode
    2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
    2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value Language
    2014-07-12 18:22:17 SQLEngine: --GroupProperties: Loading group properties from local machine.
    2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
    2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value SQLGroup
    2014-07-12 18:22:17 Slp: Sco: Attempting to get account from sid S-1-5-21-3076291671-3154185214-3698330068-1005
    2014-07-12 18:22:17 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    2014-07-12 18:22:17 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
    2014-07-12 18:22:17 Slp: Sco: Attempting to get registry value SQLPath
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties: Dumping Effective Properties for new instance.
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties:  InstanceId = MSSQL10_50.SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties:  InstanceName = SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties:  IsDefaultInstance = False
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties:  SqlServerServiceName = MSSQL$SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties:  IsExpressSku = True
    2014-07-12 18:22:17 SQLEngine: --EffectiveProperties:  IsWorkgroupSku = False
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: Dumping Install Properties
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: EnableRanu = True
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: SecurityMode =
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: LoginMode = 1
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlCollation = SQL_Latin1_General_CP1_CI_AS
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlAdminAcounts =
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlServiceStartupType = Automatic
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlAccount = NT AUTHORITY\NETWORK SERVICE
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: SqlDomainGroup =
    2014-07-12 18:22:17 SQLEngine: --InstallProperties: AddCurrentUserAsSQLAdmin = True
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: Dumping Registry Properties
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: SqlServiceRelativeRegPath = System\CurrentControlSet\Services\MSSQL$SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: CompleteInstanceRegPathByName = SOFTWARE\Microsoft\Microsoft SQL Server\SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: CompleteInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: MSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceMSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQLServer
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: SetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
    2014-07-12 18:22:17 SQLEngine: --RegistryProperties: ReferenceSetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\Setup
    2014-07-12 18:22:17 SQLEngine: --ProductProperties: Dumping Product Properties
    2014-07-12 18:22:17 SQLEngine: --ProductProperties: ProductCode = b5153233-9aee-4cd4-9d2c-4faac870dbe2
    2014-07-12 18:22:17 SQLEngine: --ProductProperties: LCID = 1033
    2014-07-12 18:22:17 SQLEngine: --GroupProperties: Dumping Group Properties
    2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupSid = S-1-5-21-3076291671-3154185214-3698330068-1005
    2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSid = WIN-EAD5VG4PBDE\SQLServerMSSQLUser$WIN-EAD5VG4PBDE$SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSidNoDomain = SQLServerMSSQLUser$WIN-EAD5VG4PBDE$SQLEXPRESS
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: Dumping Directory Propreties
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DataRootDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SystemDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: InstallSqlInstanceDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DefaultDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: DefaultLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: BackupDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Backup
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TempDbDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TempDbLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: ErrorLogDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: TemplateDataDirectory = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SqlInstanceBinnDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: SqlInstanceTemplatesDir = c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Binn\Templates
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: MasterDbPath =
    2014-07-12 18:22:17 SQLEngine: --PublicBasedDirectoryProperties: MasterLogPath =
    2014-07-12 18:22:17 SQLEngine: --SqlEngineDBStartConfig: ConfigRC : SqlEngineDBStartConfig Configuration
    2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
    2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
    2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:18 Slp: Sco: Attempting to set directory full path
    2014-07-12 18:22:18 Slp: Sco: Attempting to normalize directory path c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA
    2014-07-12 18:22:18 SQLEngine: --SqlServerStartup: SQLEngine: Slipstream case: Enable traceflag -T902
    2014-07-12 18:22:18 SQLEngine: : Checking Engine checkpoint 'StartEngineService'
    2014-07-12 18:22:18 SQLEngine: --SqlServerServiceSCM: Starting SQL via SCM (-mSqlSetup -f -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T4010 -T3659 -T3610 -T902 -dc:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data\master.mdf -lc:\Program
    Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf)...
    2014-07-12 18:22:18 Slp: Sco: Attempting to start service MSSQL$SQLEXPRESS
    2014-07-12 18:22:20 Slp: Sco: Service MSSQL$SQLEXPRESS started
    2014-07-12 18:22:20 Slp: Sco: Attempting to get service process id for service MSSQL$SQLEXPRESS
    2014-07-12 18:22:20 Slp: Invoking QueryServiceStatusEx Win32 API
    2014-07-12 18:22:20 Slp: Sco: Returning service process id 3480
    2014-07-12 18:22:20 SQLEngine: : Checking Engine checkpoint 'GetSqlServerProcessHandle'
    2014-07-12 18:22:22 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$SQLEXPRESS' to be created
    2014-07-12 18:22:24 SQLEngine: --SqlServerServiceSCM: Waiting for nt event 'Global\sqlserverRecComplete$SQLEXPRESS' or sql process handle to be signaled
    2014-07-12 18:22:24 SQLEngine: : Checking Engine checkpoint 'WaitSqlServerStartEvents'
    2014-07-12 18:22:59 Slp: Sco: Attempting to initialize script
    2014-07-12 18:23:01 Slp: Sco: Attempting to initialize default connection string
    2014-07-12 18:23:03 Slp: Sco: Attempting to set script connection protocol to NotSpecified
    2014-07-12 18:23:03 Slp: Sco: Attempting to set script connection protocol to NamedPipes
    2014-07-12 18:23:03 SQLEngine: --SqlDatabaseServiceConfig: Connection String: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
    2014-07-12 18:23:03 SQLEngine: : Checking Engine checkpoint 'ServiceConfigConnect'
    2014-07-12 18:23:03 SQLEngine: --SqlDatabaseServiceConfig: Connecting to SQL....
    2014-07-12 18:23:03 Slp: Sco: Attempting to connect script
    2014-07-12 18:23:04 Slp: Connection string: Data Source=\\.\pipe\SQLLocal\SQLEXPRESS;Initial Catalog=master;Integrated Security=True;Pooling=False;Network Library=dbnmpntw;Application Name=SqlSetup
    2014-07-12 18:24:16 Slp: Sco: Connection error code from SqlException is : -2
    2014-07-12 18:24:30 Slp: Watson Bucket 1
     Original Parameter Values
    2014-07-12 18:24:30 Slp: Parameter 0 : SQL Server 2008
    R2@RTM@
    2014-07-12 18:24:30 Slp: Parameter 2 : System.Data.SqlClient.SqlInternalConnection.OnError
    2014-07-12 18:24:30 Slp: Parameter 3 :
    Microsoft.SqlServer.Configuration.Sco.ScoException@1211@1
    2014-07-12 18:24:30 Slp: Parameter 4 :
    System.Data.SqlClient.SqlException@-2146232060
    2014-07-12 18:24:30 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
    2014-07-12 18:24:30 Slp:
     Final Parameter Values
    2014-07-12 18:24:30 Slp: Parameter 0 : SQL Server 2008
    R2@RTM@
    2014-07-12 18:24:30 Slp: Parameter 2 : 0x1BBF2F31
    2014-07-12 18:24:30 Slp: Parameter 3 : 0x0A2FBD17@1211@1
    2014-07-12 18:24:30 Slp: Parameter 4 : 0x3906094D
    2014-07-12 18:24:30 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
    2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-07-12 18:24:36 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2014-07-12 18:25:26 Slp: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    2014-07-12 18:25:32 Slp: Watson bucket for exception based failure has been created
    2014-07-12 18:25:32 SQLEngine: Copying 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt' ...
    2014-07-12 18:25:32 Slp: Sco: Attempting to set file full path to 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
    2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
    2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
    2014-07-12 18:25:32 Slp: Sco: Attempting to copy file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' to file 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
    2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to set file full path to 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to check if directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to check if directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' is equal to path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
    2014-07-12 18:25:32 Slp: Sco: Attempting to normalize directory path 'C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SQLServer_ERRORLOG_2014-07-12T18.25.32.txt'
    2014-07-12 18:25:32 Slp: Sco: Attempting to get security descriptor for file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'
    2014-07-12 18:25:32 Slp: Sco: Attempting to check if file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG' exists
    2014-07-12 18:25:32 Slp: Sco: Returning security descriptor O:NSG:NSD:AI(A;ID;FA;;;NS)(A;ID;FA;;;SY)(A;ID;FA;;;BA)(A;ID;FA;;;S-1-5-21-3076291671-3154185214-3698330068-1005)(A;ID;0x1201ff;;;S-1-5-21-3076291671-3154185214-3698330068-1006)
    2014-07-12 18:25:32 Slp: Sco: Attempting to dispose script
    Please note that this is NOT a question about fixing this one installation. This is an SQL Server Express install as part of my application install and MUST WORK FIRST TIME, EVERY TIME. Please direct me.
    Paul T.

    Here are the parameters used with the SQL Server Express installer EXE (both x86 and x64):
    /q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck /IAcceptSQLServerLicenseTerms
    I presume that TCP/IP is not enabled by default for Express installs. I THINK that named pipe should be enabled.
    Summary.txt is copied below:
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -2068119551
      Exit facility code:            1211
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Start time:                    2014-07-12 18:06:14
      End time:                      2014-07-12 18:25:44
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.4000.0%26EvtType%3d0x1BBF2F31%400x3906094D
    Machine Properties:
      Machine name:                  WIN-EAD5VG4PBDE
      Machine processor count:       1
      OS version:                    Windows 7
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         c:\b610200f3dc88995d16c2effd8b6ac\x86\setup\
      Installation edition:          EXPRESS
      Slipstream:                    True
      SP Level                       2
    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
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\ConfigurationFile.ini
      CUSOURCE:                     
      ENABLERANU:                    True
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    SQLEXPRESS
      INSTANCENAME:                  SQLEXPRESS
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     c:\b610200f3dc88995d16c2effd8b6ac\PCUSOURCE
      PID:                           *****
      QUIET:                         True
      QUIETSIMPLE:                   False
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  NT AUTHORITY\NETWORK SERVICE
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT Authority\Network Service
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           <empty>
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      UIMODE:                        AutoAdvance
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:     
    0x0A2FBD17@1211@1
      Configuration error description: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:     
    0x0A2FBD17@1211@1
      Configuration error description: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\Detail.txt
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140712_180319\SystemConfigurationCheck_Report.htmd
    The entire contents of the installation log can be found in ZIP format here:
    https://onedrive.live.com/redir?resid=8E983C44B610198D!3984&authkey=!AFbuZaCG3Lm38Pw&ithint=folder%2c.zip
    Paul T.

  • SQL Server Express 2012 SP2 installation hangs during extract phase

    Greetings!
    I am having an issue with trying to silent install SQL Server Express 2012 SP2 (x86).
    I have a proprietary installation framework, which is calling the SQL Server Express installer.
    The SQL Server Express installer starts extracting files to c:\{some guid}. The folder reaches about 11 mb in size, and then nothing further happens. No activity on the machine, CPU or disk - I have waited up to 15 minutes to verify this. On the normal installation,
    the size of this folder is ~650 mb.
    Here are the things I've also tested:
    - I'm experiencing these symptoms on both Windows 7 and Windows Server 2012 R2 (haven't tested other platforms)
    - If I launch exactly the same command from the command prompt, the installation goes through as normal
    - If I replace the SQL Server Express 2012 SP2 with SQL Server Express 2012 SP1, and install via our installation framework, the installation goes through as normal
    - I have checked and double-checked that our installation framework is started with administrative privileges.
    - From my previous search attempts, I have seen issues where the installer would hang or fail when launched from inside an msi, which would result in a log in C:\Program Files (x86)\Microsoft SQL Server\<something something>. These are not the symptoms
    I am experiencing. The C:\Program Files (x86)\Microsoft SQL Server\ folder is not even created!
    Any suggestions, or places I can look to figure out why it's not proceeding? For now, I have worked around the issue by including SP1 instead of SP2, but ideally I'd like to base my solution on the most recent service pack.

    Hello Alberto!
    The installation framework does check for this. I'm also certain that these prerequisites are fulfilled. 
    When the SQL Server process hangs, I can kill the process, copy/paste the exact command that was executed from the installation framework's log files, and execute that command in a command prompt - and then the installation runs as expected.
    The installation framework installs SQL Server Express correctly if I use the 2008 R2 SP1 express or the 2012 SP1 Express installer. It's just the SP2 installer that is giving me problems.
    The only difference I can think of is that the installation framework is a 32-bit process, which calls the SQL Server installer, while the command prompt is a 64-bit application. I am installing the SQLEXPR_x86_ENU.exe
    from http://www.microsoft.com/en-us/download/details.aspx?id=43351, so it should be compatible with my 32 bit environment - 
     "SQLEXPR_x86 is the same product but supports installation onto both 32-bit and 64-bit (WoW) operating systems"
    Tomorrow, I will try:
    - Installing on Windows 7 32-bit
    - Trying to launch the SQL Server installer from a powershell (x86) prompt, to emulate a 32-bit environment on a 64-bit machine

  • SQL Server Express is being a real pain

    I've been messing with this SQL Server Express installation
    since Friday and still can't get this application and database to
    work together correctly. The program is written in ColdFusion, but
    the errors seem to be permissions related to me but I just can't
    figure it out.
    I've created a user within SQL Server Management Express
    program and all goes well. I then assign it as database owner for
    the particular database I'm using. I've created the datasource from
    within the ColdFusion administrator and it says the connection is
    being made.
    When trying to access the script, I get the error below.
    In the SQL Management system I have tried everything that I
    know to do - from adding this particular account as a user for the
    "tUsers" table and giving it "Select" permissions to re-creating
    the account and making it owner of the entire database. I tried
    adding the schema to the front and surrounding the table name in
    brackets [ ].
    The database was restored from a backup on another server.
    Would that cause problems at all? I just tried deleting the
    database, creating it again, then restoring it from the file and
    setting the owner as this user during the import process. I'm still
    not having any luck though.
    I've searched Google and almost every result is a forums post
    from people having this same problem who have fixed it by giving
    the account permission to access the database and/or table. For
    some reason that isn't working for me - or I'm an idiot and missing
    something.
    Does anyone have any ideas?

    At first, no, I couldn't perform any queries at all against
    the database.
    I fixed the problem by editing the "server" in the CF admin
    for this datasource and making it:
    localhost/SQLEXPRESS
    CF Admin says it doesn't verify, but if I attach the username
    and password to each CFQUERY statement they work!
    Very strange problem. I'm not sure if this is a 'feature' or
    a known bug, but I don't see any reason why that connection doesn't
    verify. Especially since if it would've I could have saved myself
    countless hours of work.
    Oh well - thanks everyone for your suggestions and
    help!

  • SQL Server Express 2014 Installation Completes with Failures and Repair Does Nothing to Help

    I am attempting to install SQL Server Express 2014 on a development machine and as usual old versions of SQL and the remnants of them are a plague to the installation.
    I have used to Revo Uninstaller to scrub the old installations and with my first attempt after some additional work on the registry I was able to get an instance to install and remarkably I was able to connect to the instance. However, I removed an application
    reference to SQL Server 2008 after the SQL Express 2014 installation (through Control Panel > Programs > Programs and Features) and it stopped working immediately.
    So I removed (uninstalled using Revo Uninstaller) every reference to any SQL Server application as well as removed all of the registry references (using Revo) and I can now install SQL Server Express 2014 with 
    "Feature" failures [Reporting Services, Database Engine Services, Full-Text and Semantic Extractions for Search and SQL
    Server Replication]  and of course it doesn't work.
    Now when I attempt "Repair" the installation the process ends normally (no errors) and reports  "Success" however SQL still has no instance and the services are not running nor are they visible when I open the "SQL Server Configuration
    Manager".
    This is the "Repair" log:
    Overall summary:
    Final result: Passed
    Exit code (Decimal): 0
    Start time: 2014-12-21 17:21:37
    End time: 2014-12-21 17:29:10
    Requested action: Repair
    Machine Properties:
    Machine name: EDWARD-PC2
    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: x86
    Process architecture: 32 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2014 Management Tools - Basic 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Management Tools - Complete 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools Connectivity 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools Backwards Compatibility 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 Client Tools SDK 1033 Express Edition 12.0.2000.8 No Yes
    SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
    Package properties:
    Description: Microsoft SQL Server 2014
    ProductName: SQL Server 2014
    Type: RTM
    Version: 12
    SPLevel: 0
    Installation location: C:\Users\Edward\Downloads\SQLEXPRADV_x86_ENU\x86\setup\
    Installation edition:
    User Input Settings:
    ACTION: Repair
    AGTDOMAINGROUP: <empty>
    AGTSVCACCOUNT: <empty>
    AGTSVCPASSWORD: <empty>
    AGTSVCSTARTUPTYPE: Manual
    ASCONFIGDIR: Config
    ASSVCACCOUNT: <empty>
    ASSVCPASSWORD: <empty>
    CLTSTARTUPTYPE: 0
    CLTSVCACCOUNT: <empty>
    CLTSVCPASSWORD: <empty>
    CONFIGURATIONFILE:
    CTLRSTARTUPTYPE: 0
    CTLRSVCACCOUNT: <empty>
    CTLRSVCPASSWORD: <empty>
    ENU: true
    FAILOVERCLUSTERGROUP: <empty>
    FAILOVERCLUSTERNETWORKNAME: <empty>
    FTSVCACCOUNT: <empty>
    FTSVCPASSWORD: <empty>
    HELP: false
    IACCEPTSQLSERVERLICENSETERMS: false
    INDICATEPROGRESS: false
    INSTANCENAME: <empty>
    ISSVCACCOUNT: NT AUTHORITY\Network Service
    ISSVCPASSWORD: <empty>
    ISSVCSTARTUPTYPE: Automatic
    QUIET: false
    QUIETSIMPLE: false
    SQLSVCACCOUNT: <empty>
    SQLSVCPASSWORD: <empty>
    UIMODE: AutoAdvance
    X86: false
    Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\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 Browser
    Status: Passed
    Feature: Documentation Components
    Status: Passed
    Feature: SQL Writer
    Status: Passed
    Feature: LocalDB
    Status: Passed
    Feature: SQL Client Connectivity
    Status: Passed
    Feature: SQL Client Connectivity SDK
    Status: Passed
    Feature: Setup Support Files
    Status: Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141221_172135\SystemConfigurationCheck_Report.htm
    However this is what the "SQL Sever Configuration Manager" look like:
    Why does this appear to not be working properly? I can not connect the the "local" instance and I would guess that the service either does not exist or is not running.
    Edward Walker

    Hello,
    To my knowledge, Revo is not a supported way to uninstall SQL Server.
    Please try to uninstall all you can using Control Panel -> Programs and Features, then perform a manual uninstall to
    remove remnants. Try the following procedure:
    1. Uninstall all SQL Server 2012 components you can using Control Panel -> Programs and Features
    2. Backup the registry.
    3. Delete the following keys in regedit:
    --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
    --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
    4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing
    SQL Server.
    5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
    6. Rename all the SQL Server folders in the computer like C:\Program Files\Microsoft SQL Server and subfolders.
    After performing above procedure, try to reinstall SQL Server again.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Server Express 2005 to 2014 upgrade and Uninstallation issues

    We have client application running SQL Server Express that connects to a SQL Server 2012 server.  We are attempting to upgrade from Microsoft SQL 2005 express to Microsoft SQL Server 2014
    express – but are having difficulties – especially with uninstall.
    Our understanding is that we needed to follow the following steps:
        First we install Microsoft SQL 2005 express SP4 as required silently
    Start /wait SQLEXPR.exe /qn ACTION=UPGRADE INSTANCENAME="SQLEXPRESS" UPGRADE=SQL_Engine SAPWD=<password>
    SQLACCOUNT="NT AUTHORITY\SYSTEM" SQLPASSWORD= SECURITYMODE="SQL"
        Then try upgrading with Microsoft SQL Server 2014 express, we use following command to do it silently
    SQLEXPR.exe /q /ACTION=upgrade /INSTANCENAME=SQLEXPRESS /ISSVCAccount="NT AUTHORITY\SYSTEM" /IACCEPTSQLSERVERLICENSETERMS
    We see following
        In Control Panel -> Uninstall or change program, we have all the instances listed 2005, 2008, 2012 and 2014.
        How do we uninstall the instance?  , We try uninstalling 2014
    But it is not cleanly uninstalled.
    Questions:
        Is there any way for clean upgrade from Microsoft SQL 2005 express SP3 to Microsoft SQL 2014 express?
        Is there any specific steps suggested to uninstall upgraded SQL 2014 express from system?
        Are we doing anything wrong in commands for silent upgrade?
    Thanks in advance.

    Hello,
    After you perform an in-place upgrade it’s normal to find the binaries and references of the old version of SQL Server on the Start Menu and Control Panel -> Programs and Features. That’s by design. After you have successfully upgraded an instance, you can
    remove the old binaries.
    IfIf you find some remnants after uninstalling SQL Server 2014, please perform the following steps to manually uninstall it:
    1. Uninstall all SQL Server 2014 components you can using Control Panel -> Programs and
    Features
    2. Backup the registry.
    3. Delete the following keys in regedit:
        --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
        --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
    4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete
    all the sub-keys referencing SQL Server.
    5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing
    SQL Server.
    6. Rename all the SQL Server folders in the computer like
    C:\Program Files\Microsoft SQL Server and subfolders.
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Issues using BitLocker in Windows 8 Emedded with 2012 SQL Server Express

    I was told that this forum may be able to help me with my issues (see original thread here:
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8c81fde1-e91b-46eb-8d2f-b79426805ddd/using-sql-server-2012-express-with-bitocker?forum=sqlexpress).
    Background:
    To summarize, I have an OS that is partitioned into two volumes: C and D.
    C drive contains the running software, SQL Server install, and the OS.
    D drive is the encrypted partition via BitLocker. The SQL Server files are stored here (logs, backup, and mdf).
    Problem:
    The software cannot connect to the database stored on the encrypted D volume when BitLocker is turned on. The user account that I use to enable BitLocker is the same SQL Server Service account and has is also part of the Local Admin Group. As soon as I disable
    BitLocker, the software works fine and the database connection succeeds. I am currently using the SQL System Admin account to login (SA) and BitLocker is being used with a TPM.
    The error I am experiencing when connecting through the software is 'login
    failed for user sa'.
    Thank you for the suggestions/help.

    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

Maybe you are looking for