SQL Server 2014 reseting isolation level

Hi,
Working with C# application accessing SQL Server 2012 and 2014 using ADO.NET.
There seem to be a change regarding isolation level reset when returning connection to pool.
Previous versions of SQL Server does not reset the isolation level on the connection (unfortunately) as claimed here (http://support.microsoft.com/?id=972915).
However it seems this has changed with SQL Server 2014.
If running the attached code it shows that the isolation level in fact is reset when running against a SQL Server 2014 instance but not 2012.
Can anyone on the SQL Server team confirm that this is an intended change that is here to stay? I have not seen any documentation on this so far in the behavior changes documented here: http://msdn.microsoft.com/en-us/library/ms143359.aspx
class Program
static void Main(string[] args)
TestIsolationLevelReset();
Console.ReadLine();
public static void TestIsolationLevelReset()
var connectionString = @"Data Source=(local); Integrated Security=true; Initial Catalog=master;";
var commandText = @"select cast (transaction_isolation_level as nvarchar) + ' - ' + CAST(@@spid as nvarchar) from sys.dm_exec_sessions where (session_id = @@SPID)";
using (var conn = new SqlConnection(connectionString))
conn.Open();
var cmd = new SqlCommand(commandText, conn);
Console.WriteLine(cmd.ExecuteScalar());
using (var tran = new TransactionScope(TransactionScopeOption.Required, new TransactionOptions() { IsolationLevel = IsolationLevel.Serializable }))
using (var conn = new SqlConnection(connectionString))
conn.Open();
var cmd = new SqlCommand(commandText, conn);
Console.WriteLine(cmd.ExecuteScalar());
tran.Complete();
using (var conn = new SqlConnection(connectionString))
conn.Open();
var cmd = new SqlCommand(commandText, conn);
Console.WriteLine(cmd.ExecuteScalar());

Is that possible to know, or must I always ask SQL Server what has been negotiated?
The negotiated version is the highest version supported by both client and server.  According to
http://msdn.microsoft.com/en-us/library/dd304523.aspx, the Server versions are:
SQL Server 7.0 7.0
SQL Server 2000 7.1
SQL Server 2000 SP1 7.1 Revision 1
SQL Server 2005 7.2
SQL Server 2008 7.3.A
SQL Server 2008 R2 7.3.B
SQL Server 2012 7.4
SQL Server 2014 7.4
I can't speak to the exact TDS versions supported by SqlClient.  On my PC, .NET 4.0 and above against a SQL 2014 box used TDS 7.4 where as 3.5 and earlier used TDS 7.3. 
Based on this, I wouldn't expect the isolation level behavior change if SQL Server 2012 and 2014 is the only difference.  What version of .NET are you using?
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Similar Messages

  • Moving sql server 2000 to sql server 2014

    Moving sql server 2000 to sql server 2014. Could someone please give me steps to move everything from sql 2000 one server to sql 2014. I have 2 instance on sql 2000. 8 databases on each of them. On both instances we have store procedure and jobs.

    i think your SQL Server 2000 is hosted on old Windows server version so based on that you should prepare new environment for SQL Server 2014 from Win Server 2012 Sp1 and SQL Server 2014 and build your clusters then start your Migration from Old Servers to
    new servers and here below is 10 configurations outlines that you should look after carefully for any DB consolidation or migration from a server to  a server and indeed they represent unique potentials for your DB Consolidation /migration service that
    can leverage distinctly your service quality and shape you very well in front of your customers:
    1-      Backup DBs and restore DBs with ZERO down time and ZERO data loss in the same time …Awesome …!
    2-      Cloning all DB special features that are not covered by backups and restores such as :
    RCSI (Read committed snapshot isolation level using row versioning)
    Service brokers
    Encryption keys and certificates
    3-      Cloning identically all SQL logins with their mapped DB users including their passwords (if SQL authenticated logins ) and privileges on both server and DB levels .
    4-      Copying .rdl and .rds files between different versions of reporting services where backup and restore reportserver and reportservertemp DBs is not an option
    5-      Cloning all special Jobs like certain business jobs configured to perform some business stuff .
    6-      Cloning all mail profiles with their mail accounts
    7-      Cloning all Linked server + Aliases might be used inside old DB servers
    8-      Cloning some server configurations like CLR ,CPU parallelism, Replication size , Network packet size , optimize for ad hoc workloads
    9-      Cloning all Replications configurations for publishers and subscribers
    10-   Cloning all DTC configurations for both local and clustered DTC services
    Follow the below links to know the steps by the scripts:
    http://sqlserver-performance-tuning.net/?p=5262
    http://sqlserver-performance-tuning.net/?p=5359
    http://sqlserver-performance-tuning.net/?p=5398
    http://sqlserver-performance-tuning.net/?p=5415
    http://sqlserver-performance-tuning.net/?p=5458
    Mustafa EL-Masry
    Principle Database Administrator & DB Analyst
    SQL Server MCTS-MCITP
    M| +966 54 399 0968
    MostafaElmasry.Wordpress.com

  • SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

    We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.)  Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
    anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
    specifically listed as a SQL DB user tries to use the front end they get an error of:
    Microsoft SQL Server Login
    Connection failed:
    SQL State: '28000'
    SQL Server Error: 18456
    [Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
    After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
    to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
    Thanks a billion in advance ----

    Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
    all other roles, as well as allowing select only, and still have no access for the guest account.
    The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
    and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
    thru MS Access ACCDB, using a (by default) read only OCDB connection.
    This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
    levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
    since the result set would involve hundreds of thousands if not millions of records.
    So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
    as well as running our network on Microsoft's network software.

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

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

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

  • Overlapped I/O error 997 installing SQL Server 2014 Express on Windows Server 2012 R2

    I'm attempting to install SQL Server 2014 Express on a Windows Server 2012 R2 system. When I do the install, it fails (several times) with an "Error: 997. Overlapped I/O operation is in progress.". From searching the web, I can see many people
    have had this problem with this installer and other non-SQL server installers.
    I've tried every solution I can find discussed, but none help with my problems The system is fully updated, with the exception of the KB2538243 (VC 2008 SP1 redist), which is probably failing for the same reason.
    I've tried removing several updates mentioned in other articles (KB2918614). I've confirmed that I'm not using a temporary profile.
    Does anyone have an idea of how I can solve this issue?
    Thanks,
    Zack
    Partial detail from install log file:
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      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=vc_red.msi%40ProcessComponents%40997
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                Microsoft Visual Studio 2010 Redistributables
      Component error code:          997
      Component log file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150205_151618\VC10Redist_Cpu64_1.log
      Error description:             Error 997.Overlapped I/O operation is in progress.
      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=vc_red.msi%40ProcessComponents%40997
    Partial detail from component log file:
    MSI (s) (D8:3C) [15:18:29:173]: Resolving source.
    MSI (s) (D8:3C) [15:18:29:173]: Resolving source to launched-from source.
    MSI (s) (D8:3C) [15:18:29:173]: Setting launched-from source as last-used.
    MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
    MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\'.
    MSI (s) (D8:3C) [15:18:29:188]: PROPERTY CHANGE: Adding SourcedirProduct property. Its value is '{1D8E6291-B0D5-35EC-8441-6616F567A0F7}'.
    MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR ==> C:\Users\zerhart\Downloads\SQLEXPRWT_x64_ENU\redist\VisualStudioShell\VC10SP1\x64\
    MSI (s) (D8:3C) [15:18:29:188]: SOURCEDIR product ==> {1D8E6291-B0D5-35EC-8441-6616F567A0F7}
    MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: A general error running CryptAcquireContext
    MSI (s) (D8:3C) [15:18:29:188]: Determining source type
    MSI (s) (D8:3C) [15:18:29:188]: Source type from package 'VC_RED.MSI': 2
    MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: Hash Database: C:\Windows\Installer\SourceHash{1D8E6291-B0D5-35EC-8441-6616F567A0F7}
    MSI (s) (D8:3C) [15:18:29:188]: SECREPAIR: SourceHash database file already exists. Deleting it.
    MSI (s) (D8:3C) [15:18:29:204]: Note: 1: 2262 2: SourceHash 3: -2147287038 
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: New Hash Database creation complete.
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:0
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Crypt Provider not initialized. Error:997
    MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: Failed to CreateContentHash of the file: install.res.1040.dll: for computing its hash. Error: 997
    MSI (s) (D8:3C) [15:18:29:235]: SECREPAIR: Failed to create hash for the install source files
    MSI (s) (D8:3C) [15:18:29:235]: SECUREREPAIR: SecureRepair Failed. Error code: 3e561F257D8
    Action start 15:18:29: ProcessComponents.
    MSI (s) (D8:3C) [15:19:28:843]: 
    Error 997.Overlapped I/O operation is in progress.

    Alberto,
    Thanks for your help. Unfortunately, I've already tried that. I did try it again and I get an "This update is not applicable to your computer."
    I tried to post the Windows Update log, but it was too large. I've posted some of it below.
    Here is the WU log:
    2015-02-06 11:24:25:793
    5048 50
    Misc ===========  Logging initialized (build: 7.9.9600.17489, tz: -0500)  ===========
    2015-02-06 11:24:25:793
    5048 50
    Misc  = Process: C:\Windows\system32\wusa.exe
    2015-02-06 11:24:25:793
    5048 50
    Misc  = Module: C:\Windows\System32\wuapi.dll
    2015-02-06 11:24:25:793
    5048 50
    COMAPI -----------  COMAPI: IUpdateServiceManager::AddScanPackageService  -----------
    2015-02-06 11:24:25:793
    5048 50
    COMAPI  - ServiceName = Windows Update Standalone Installer
    2015-02-06 11:24:25:793
    5048 50
    COMAPI  - ScanFileLocation = C:\c5f288db3c43a7e4613232ca1a3c\wsusscan.cab
    2015-02-06 11:24:25:808
    920 111c
    Misc ===========  Logging initialized (build: 7.9.9600.17489, tz: -0500)  ===========
    2015-02-06 11:24:25:808
    920 111c
    Misc  = Process: C:\Windows\system32\svchost.exe
    2015-02-06 11:24:25:808
    920 111c
    Misc  = Module: c:\windows\system32\wuaueng.dll
    2015-02-06 11:24:25:808
    920 111c
    Service *************
    2015-02-06 11:24:25:808
    920 111c
    Service ** START **  Service: Service startup
    2015-02-06 11:24:25:808
    920 111c
    Service *********
    2015-02-06 11:24:25:824
    920 111c
    IdleTmr Non-AoAc machine.  Aoac operations will be ignored.
    2015-02-06 11:24:25:824
    920 111c
    Agent  * WU client version 7.9.9600.17489
    2015-02-06 11:24:25:824
    920 111c
    Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
    2015-02-06 11:24:25:824
    920 111c
    Agent  * Base directory: C:\Windows\SoftwareDistribution
    2015-02-06 11:24:25:824
    920 111c
    Agent  * Access type: No proxy
    2015-02-06 11:24:25:824
    920 111c
    Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
    2015-02-06 11:24:25:824
    920 111c
    Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
    2015-02-06 11:24:25:824
    920 111c
    Agent  * Network state: Connected
    2015-02-06 11:24:25:824
    920 111c
    Service UpdateNetworkState Ipv6, cNetworkInterfaces = 12.
    2015-02-06 11:24:25:824
    920 111c
    Service UpdateNetworkState Ipv4, cNetworkInterfaces = 4.
    2015-02-06 11:24:25:855
    920 b64
    Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2015-02-06 11:24:25:855
    920 111c
    Agent ***********  Agent: Initializing global settings cache  ***********
    2015-02-06 11:24:25:887
    920 111c
    Agent  * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2015-02-06 11:24:25:887
    920 111c
    Agent  * WSUS server: <NULL>
    2015-02-06 11:24:25:887
    920 111c
    Agent  * WSUS status server: <NULL>
    2015-02-06 11:24:25:887
    920 111c
    Agent  * Target group: (Unassigned Computers)
    2015-02-06 11:24:25:887
    920 111c
    Agent  * Windows Update access disabled: No
    2015-02-06 11:24:25:902
    920 b64
    WuTask WuTaskManager delay initialize completed successfully..
    2015-02-06 11:24:25:902
    920 b64
    AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
    2015-02-06 11:24:25:902
    920 b64
    AU    Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2015-02-06 19:30:54, not idle-only, not network-only
    2015-02-06 11:24:25:902
    920 b64
    AU    Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2015-02-06 19:30:54, not idle-only, not network-only
    2015-02-06 11:24:25:902
    920 b64
    Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
    2015-02-06 11:24:25:902
    920 b64
    Report CWERReporter::Init succeeded
    2015-02-06 11:24:25:902
    920 b64
    Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2015-02-06 11:24:25:902
    920 b64
    DnldMgr Download manager restoring 0 downloads
    2015-02-06 11:24:25:902
    920 111c
    AU ###########  AU: Initializing Automatic Updates  ###########
    2015-02-06 11:24:25:902
    920 111c
    AU AIR Mode is disabled
    2015-02-06 11:24:25:902
    920 111c
    AU  # Approval type: Scheduled (User preference)
    2015-02-06 11:24:25:902
    920 111c
    AU  # Auto-install minor updates: Yes (User preference)
    2015-02-06 11:24:25:902
    920 111c
    AU  # Will interact with non-admins (Non-admins are elevated (User preference))
    2015-02-06 11:24:25:902
    920 111c
    Misc WARNING:     IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 2, GetLastError=2250
    2015-02-06 11:24:25:918
    920 111c
    AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2015-02-06 11:24:25:918
    920 111c
    AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2015-02-06 11:24:25:918
    920 111c
    AU AU finished delayed initialization
    2015-02-06 11:24:25:933
    920 111c
    AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2015-02-06 11:24:25:933
    920 111c
    AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2015-02-06 11:24:25:933
    920 b64
    Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\a487aa0f-3e53-4fee-a784-6171b00254e4\Source.cab with dwProvFlags 0x00000080:
    2015-02-06 11:24:25:933
    920 111c
    AU Adding timer: 
    2015-02-06 11:24:25:933
    920 111c
    AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2015-02-07 08:14:01, not idle-only, not network-only
    2015-02-06 11:24:25:949
    920 af0
    DnldMgr Asking handlers to reconcile their sandboxes
    2015-02-06 11:24:25:949
    920 b64
    Misc Microsoft signed: Yes
    2015-02-06 11:24:26:154
    920 b64
    DtaStor Default service for AU is {7971F918-A847-4430-9279-4A52D1EFE18D}
    2015-02-06 11:24:26:154
    920 b64
    IdleTmr Incremented idle timer priority operation counter to 1
    2015-02-06 11:24:26:154
    5048 50
    COMAPI  - Added scan package service, ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
    2015-02-06 11:24:26:154
    5048 50
    COMAPI -------------
    2015-02-06 11:24:26:154
    5048 50
    COMAPI -- START --  COMAPI: Init Search [ClientId = wusa]
    2015-02-06 11:24:26:154
    5048 50
    COMAPI ---------
    2015-02-06 11:24:26:154
    5048 50
    COMAPI -------------
    2015-02-06 11:24:26:154
    5048 50
    COMAPI -- START --  COMAPI: Search [ClientId = wusa]
    2015-02-06 11:24:26:154
    5048 50
    COMAPI ---------
    2015-02-06 11:24:26:169
    920 b64
    IdleTmr WU operation (CSearchCall::Init ID 1) started; operation # 17; does use network; is not at background priority
    2015-02-06 11:24:26:169
    920 b64
    IdleTmr Incremented idle timer priority operation counter to 2
    2015-02-06 11:24:26:341
    920 b64
    Report ***********  Report: Initializing static reporting data  ***********
    2015-02-06 11:24:26:341
    920 b64
    Report  * OS Version = 6.3.9600.0.0.131344
    2015-02-06 11:24:26:341
    920 b64
    Report  * OS Product Type = 0x00000021
    2015-02-06 11:24:26:357
    920 b64
    Report  * Computer Brand = PowerSpec
    2015-02-06 11:24:26:357
    920 b64
    Report  * Computer Model = S Series
    2015-02-06 11:24:26:357
    920 b64
    Report  * Platform Role = 1
    2015-02-06 11:24:26:357
    920 b64
    Report  * AlwaysOn/AlwaysConnected (AOAC) = 0
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Revision = 1.1a
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Name = 1.1a
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Release Date = 2013-08-20T00:00:00
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Sku Number = S Series
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Vendor = American Megatrends Inc.
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Family = Server
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Major Release = 4
    2015-02-06 11:24:26:357
    920 b64
    Report  * Bios Minor Release = 6
    2015-02-06 11:24:26:357
    920 b64
    Report  * Locale ID = 1033
    2015-02-06 11:24:26:357
    920 b64
    Handler Calculating current update level for this session
    [ Omitted data ]
    http://support.microsoft.com/?kbid=3000850, timestamp 01d039c57a22c0be
    2015-02-06 11:24:28:388
    920 b64
    Handler Done calculating current update level for this session
    2015-02-06 11:24:28:982
    920 b64
    Agent *** START ***  Queueing Finding updates [CallerId = wusa  Id = 1]
    2015-02-06 11:24:28:982
    5048 50
    COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = wusa]
    2015-02-06 11:24:28:982
    920 11f4
    Agent ***  END  ***  Queueing Finding updates [CallerId = wusa  Id = 1]
    2015-02-06 11:24:28:982
    920 11f4
    Agent *************
    2015-02-06 11:24:28:982
    920 11f4
    Agent ** START **  Agent: Finding updates [CallerId = wusa  Id = 1]
    2015-02-06 11:24:28:982
    920 11f4
    Agent *********
    2015-02-06 11:24:28:982
    920 11f4
    Agent  * Online = Yes; Ignore download priority = No
    2015-02-06 11:24:28:982
    920 11f4
    Agent  * Criteria = "DeploymentAction='Installation'"
    2015-02-06 11:24:28:982
    920 11f4
    Agent  * ServiceID = {A487AA0F-3E53-4FEE-A784-6171B00254E4} Third party service
    2015-02-06 11:24:28:982
    920 11f4
    Agent  * Search Scope = {Machine}
    2015-02-06 11:24:28:982
    920 11f4
    Agent  * Caller SID for Applicability: S-1-5-21-3157695610-3447843402-2534478823-500
    2015-02-06 11:24:28:982
    920 11f4
    Agent  * RegisterService is set
    2015-02-06 11:24:29:185
    920 11f4
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2015-02-06 11:24:29:185
    920 11f4
    PT  + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
    2015-02-06 11:24:29:185
    920 11f4
    PT WARNING: Cached cookie has expired or new PID is available
    2015-02-06 11:24:29:185
    920 11f4
    Agent Reading cached app categories using lifetime 604800 seconds
    2015-02-06 11:24:29:185
    920 11f4
    Agent Read 0 cached app categories
    2015-02-06 11:24:29:185
    920 11f4
    Agent SyncUpdates adding 0 visited app categories
    2015-02-06 11:24:29:294
    920 11f4
    Agent Reading cached app categories using lifetime 604800 seconds
    2015-02-06 11:24:29:294
    920 11f4
    Agent Read 0 cached app categories
    2015-02-06 11:24:29:294
    920 11f4
    Agent SyncUpdates adding 0 visited app categories
    2015-02-06 11:24:29:357
    920 11f4
    Agent Reading cached app categories using lifetime 604800 seconds
    2015-02-06 11:24:29:357
    920 11f4
    Agent Read 0 cached app categories
    2015-02-06 11:24:29:357
    920 11f4
    Agent SyncUpdates adding 0 visited app categories
    2015-02-06 11:24:29:638
    920 11f4
    Agent Reading cached app categories using lifetime 604800 seconds
    2015-02-06 11:24:29:638
    920 11f4
    Agent Read 0 cached app categories
    2015-02-06 11:24:29:638
    920 11f4
    Agent SyncUpdates adding 0 visited app categories
    2015-02-06 11:24:30:013
    920 11f4
    Agent Reading cached app categories using lifetime 604800 seconds
    2015-02-06 11:24:30:013
    920 11f4
    Agent Read 0 cached app categories
    2015-02-06 11:24:30:013
    920 11f4
    Agent SyncUpdates adding 0 visited app categories
    2015-02-06 11:24:30:044
    920 11f4
    Agent Reading cached app categories using lifetime 604800 seconds
    2015-02-06 11:24:30:044
    920 11f4
    Agent Read 0 cached app categories
    2015-02-06 11:24:30:044
    920 11f4
    Agent SyncUpdates adding 0 visited app categories
    2015-02-06 11:24:30:044
    920 11f4
    PT  + SyncUpdates round trips: 5
    2015-02-06 11:24:30:076
    920 11f4
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2015-02-06 11:24:30:076
    920 11f4
    PT  + Offline serviceId = {A487AA0F-3E53-4FEE-A784-6171B00254E4}
    2015-02-06 11:24:30:138
    920 11f4
    Agent  * Found 0 updates and 54 categories in search; evaluated appl. rules of 126 out of 284 deployed entities
    2015-02-06 11:24:30:138
    920 11f4
    Agent *********
    2015-02-06 11:24:30:138
    920 11f4
    Agent **  END  **  Agent: Finding updates [CallerId = wusa  Id = 1]
    2015-02-06 11:24:30:138
    920 11f4
    Agent *************
    2015-02-06 11:24:30:138
    920 11f4
    IdleTmr WU operation (CSearchCall::Init ID 1, operation # 17) stopped; does use network; is not at background priority
    2015-02-06 11:24:30:138
    920 11f4
    IdleTmr Decremented idle timer priority operation counter to 1
    2015-02-06 11:24:30:154
    5048 1428
    COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = wusa]
    2015-02-06 11:24:30:154
    5048 1428
    COMAPI  - Updates found = 0
    2015-02-06 11:24:30:154
    5048 1428
    COMAPI ---------
    2015-02-06 11:24:30:154
    5048 1428
    COMAPI --  END  --  COMAPI: Search [ClientId = wusa]
    2015-02-06 11:24:30:154
    5048 1428
    COMAPI -------------

  • Installing SQL Server 2014 Express package as ClickOnce prerequisite

    I'm using clickOnce and deploying an installer with it.
    I have tried various settings. Using SQL Server 2008 Express and SQL Server 2012 Express as prerequisite is all ok (I've dowloaded them and set the option of clickonce "download prerequisites from the same path of app").
    Now I'm trying to do the same thing with SQL Server 2014 Express.
    Since the SQL Server 2014 Express package isn't alredy done line 2008 and 2012 versiones, I'm trying to create it.
    I have done and it seems to work, but while installing it gives error number **-2054422506**. It is a very generic error and I don't understand it.
    It appears a pop up saying the installation is stopped because it is an error installing SQL Server Express 2014 and to look the log for more infos.
    The log only says:
        Installing using command     
        'C:\Users\VIRTUA~1\AppData\Local\Temp\VSD24F4.tmp\SqlExpress2014\
        SQLEXPR32_x86_ITA.EXE' and parameters '/q /action=Install /features=SQL
        /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is  
        /sqlsvcaccount="NT Authority\Network Service'
        Process exited with code -2054422506
        Status of package 'SQL Server 2014 Express' after install is 'InstallFailed'
    So, I've tried to install SQL Server 2014 Express manually, without ClickOnce, and it works. So I think I've made some mess in the xml file of the package.
    My package is so build (in C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\Bootstrapper\Packages\):
        \SqlExpress2014
             \it
                 SQLEXPR32_x86_ITA.exe
                 SQLEXPR_x64_ITA.exe
                 eula.rtf
                 package.xml
             product.xml
             SqlExpressChk.exe
    This is my package.xml file:
    <?xml version="1.0" encoding="UTF-8"?>
    <Package
    xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper"
    Name="DisplayName"
    Culture="Culture"
    LicenseAgreement="eula.rtf">
    <PackageFiles CopyAllPackageFiles="false">
    <PackageFile Name="SQLEXPR32_x86_ITA.EXE"/>
    <PackageFile Name="SQLEXPR_x64_ITA.EXE" />
    <PackageFile Name="eula.rtf"/>
    </PackageFiles>
    <InstallChecks>
    <ExternalCheck Property="SQLExpressChk" PackageFile="SqlExpressChk.exe" Arguments="11.0.2100 1040"/>
    </InstallChecks>
    <Commands Reboot="Defer">
    <!-- Defines a new installation (x86)
    /skiprules=RebootRequiredCheck /enableranu=1 /AddCurrentUserAsSqlAdmin /hideconsole
    -->
    <Command PackageFile="SQLEXPR32_x86_ITA.EXE"
    Arguments='/q /action=Install /features=SQL /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /sqlsvcaccount="NT Authority\Network Service"
    /IAcceptSqlServerLicenseTerms /SQLSVCPASSWORD="234692Is" /SQLSYSADMINACCOUNTS="NT Authority\Network Service" /AGTSVCACCOUNT="NT AUTHORITY\Network Service"'
    EstimatedInstalledBytes="225000000"
    EstimatedInstallSeconds="420">
    <InstallConditions>
    <FailIf Property="VersionNT" Compare="ValueNotExists" String="InvalidPlatformOS"/>
    <FailIf Property="VersionNT" Compare="VersionLessThan" Value="6.0.0" String="InvalidPlatformOS"/>
    <FailIf Property="VersionNT" Compare="VersionLessThan" Value="6.0.2" String="InvalidPlatformOSServicePack"/>
    <FailIf Property="VersionNT" Compare="VersionEqualTo" Value="6.1.0" String="InvalidPlatformOSServicePack"/>
    <FailIf Property="AdminUser" Compare="ValueEqualTo" Value="false" String="AdminRequired"/>
    <FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-1" String="InvalidUpgradeNotExpress"/>
    <FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-2" String="InvalidUpgradeNotExpressCore"/>
    <FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-3" String="InvalidUpgradeLanguage"/>
    <FailIf Property="SQLExpressChk" Compare="ValueEqualTo" Value="-4" String="InvalidUpgradeWoW"/>
    <FailIf Property="SQLExpressChk" Compare="ValueLessThan" Value="-4" String="GeneralFailure"/>
    <BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="Intel"/>
    <BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="1"/>
    </InstallConditions>
    <ExitCodes>
    <ExitCode Value="0" Result="Success"/>
    <ExitCode Value="1641" Result="SuccessReboot"/>
    <ExitCode Value="3010" Result="SuccessReboot"/>
    <!-- 0x84BE0BC2 (1214,3010) -->
    <ExitCode Value="-2067919934" Result="FailReboot"/>
    <!-- 0x84C10BC2 (1217,3010) -->
    <ExitCode Value="-2067723326" Result="FailReboot"/>
    <!-- 0x84BE0007 (1214,7) -->
    <ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>
    <!-- 0x84C4001F (1220,31) -->
    <ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>
    <!-- 0x84BE0001 (1214,1)-->
    <ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>
    <!-- 0x84C4000E (1220,14) -->
    <ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>
    <!-- 0x84C4000B (1220,11) -->
    <ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>
    <!-- 0x84BE01F8 (1214,504) -->
    <ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE01FA (1214,506) -->
    <ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE0202 (1214,514) -->
    <ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>
    <!-- 0x84BE0203 (1214,515) -->
    <ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
    <ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
    <DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
    </ExitCodes>
    </Command>
    <!-- Defines an upgrade installation (x86) -->
    <Command PackageFile="SQLEXPR32_x86_ITA.EXE"
    Arguments="/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck"
    EstimatedInstalledBytes="225000000"
    EstimatedInstallSeconds="420">
    <InstallConditions>
    <BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="Intel"/>
    <BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="2"/>
    </InstallConditions>
    <ExitCodes>
    <ExitCode Value="0" Result="Success"/>
    <ExitCode Value="1641" Result="SuccessReboot"/>
    <ExitCode Value="3010" Result="SuccessReboot"/>
    <!-- 0x84BE0BC2 (1214,3010) -->
    <ExitCode Value="-2067919934" Result="FailReboot"/>
    <!-- 0x84C10BC2 (1217,3010) -->
    <ExitCode Value="-2067723326" Result="FailReboot"/>
    <!-- 0x84BE0007 (1214,7) -->
    <ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>
    <!-- 0x84C4001F (1220,31) -->
    <ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>
    <!-- 0x84BE0001 (1214,1)-->
    <ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>
    <!-- 0x84C4000E (1220,14) -->
    <ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>
    <!-- 0x84C4000B (1220,11) -->
    <ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>
    <!-- 0x84BE01F8 (1214,504) -->
    <ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE01FA (1214,506) -->
    <ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE0202 (1214,514) -->
    <ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>
    <!-- 0x84BE0203 (1214,515) -->
    <ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
    <ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
    <DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
    </ExitCodes>
    </Command>
    <!-- Defines a new installation (amd64) -->
    <Command PackageFile="SQLEXPR_x64_ITA.EXE"
    Arguments='/q /hideconsole /action=Install /features=SQL /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck'
    EstimatedInstalledBytes="225000000"
    EstimatedInstallSeconds="420">
    <InstallConditions>
    <BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="amd64"/>
    <BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="1"/>
    </InstallConditions>
    <ExitCodes>
    <ExitCode Value="0" Result="Success"/>
    <ExitCode Value="1641" Result="SuccessReboot"/>
    <ExitCode Value="3010" Result="SuccessReboot"/>
    <!-- 0x84BE0BC2 (1214,3010) -->
    <ExitCode Value="-2067919934" Result="FailReboot"/>
    <!-- 0x84C10BC2 (1217,3010) -->
    <ExitCode Value="-2067723326" Result="FailReboot"/>
    <!-- 0x84BE0007 (1214,7) -->
    <ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>
    <!-- 0x84C4001F (1220,31) -->
    <ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>
    <!-- 0x84BE0001 (1214,1)-->
    <ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>
    <!-- 0x84C4000E (1220,14) -->
    <ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>
    <!-- 0x84C4000B (1220,11) -->
    <ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>
    <!-- 0x84BE01F8 (1214,504) -->
    <ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE01FA (1214,506) -->
    <ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE0202 (1214,514) -->
    <ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>
    <!-- 0x84BE0203 (1214,515) -->
    <ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
    <ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
    <DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
    </ExitCodes>
    </Command>
    <!-- Defines an upgrade installation (amd64) -->
    <Command PackageFile="SQLEXPR_x64_ITA.EXE"
    Arguments="/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS /securitymode=SQL /sapwd=234692Is /IAcceptSqlServerLicenseTerms /skiprules=RebootRequiredCheck"
    EstimatedInstalledBytes="225000000"
    EstimatedInstallSeconds="420">
    <InstallConditions>
    <BypassIf Property="ProcessorArchitecture" Compare="ValueNotEqualTo" Value="amd64"/>
    <BypassIf Property="SQLExpressChk" Compare="ValueNotEqualTo" Value="2"/>
    </InstallConditions>
    <ExitCodes>
    <ExitCode Value="0" Result="Success"/>
    <ExitCode Value="1641" Result="SuccessReboot"/>
    <ExitCode Value="3010" Result="SuccessReboot"/>
    <!-- 0x84BE0BC2 (1214,3010) -->
    <ExitCode Value="-2067919934" Result="FailReboot"/>
    <!-- 0x84C10BC2 (1217,3010) -->
    <ExitCode Value="-2067723326" Result="FailReboot"/>
    <!-- 0x84BE0007 (1214,7) -->
    <ExitCode Value="-2067922937" Result="Fail" String="AdminRequired"/>
    <!-- 0x84C4001F (1220,31) -->
    <ExitCode Value="-2067529697" Result="Fail" String="AdminRequired"/>
    <!-- 0x84BE0001 (1214,1)-->
    <ExitCode Value="-2067922943" Result="Fail" String="InvalidPlatformOSServicePack"/>
    <!-- 0x84C4000E (1220,14) -->
    <ExitCode Value="-2067529714" Result="Fail" String="InvalidPlatformOSLanguage"/>
    <!-- 0x84C4000B (1220,11) -->
    <ExitCode Value="-2067529717" Result="Fail" String="AnotherInstanceRunning"/>
    <!-- 0x84BE01F8 (1214,504) -->
    <ExitCode Value="-2067922440" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE01FA (1214,506) -->
    <ExitCode Value="-2067922438" Result="Fail" String="BetaComponentsFailure"/>
    <!-- 0x84BE0202 (1214,514) -->
    <ExitCode Value="-2067922430" Result="Fail" String="InvalidPlatformArchitecture"/>
    <!-- 0x84BE0203 (1214,515) -->
    <ExitCode Value="-2067922429" Result="Fail" String="InvalidPlatformArchitecture"/>
    <ExitCode Value="216" Result="Fail" String="InvalidPlatformArchitecture"/>
    <DefaultExitCode Result="Fail" FormatMessageFromSystem="true" String="GeneralFailure" />
    </ExitCodes>
    </Command>
    </Commands>
    <Strings>
    <String Name="DisplayName">SQL Server 2014 Express</String>
    <String Name="Culture">it</String>
    <String Name="SqlExpr32Exe">http://download.microsoft.com/download/1/6/E/16E343FB-7961-457C-A9C9-E6919F2B7188/Express%2032BIT/SQLEXPR_x86_ITA.exe</String>
    <String Name="SqlExpr64Exe">http://download.microsoft.com/download/1/6/E/16E343FB-7961-457C-A9C9-E6919F2B7188/Express%2064BIT/SQLEXPR_x64_ITA.exe</String>
    <String Name="AdminRequired">Non si dispone delle autorizzazioni necessarie per installare SQL Server 2014 Express. Rivolgersi all'amministratore.</String>
    <String Name="GeneralFailure">Errore durante il tentativo di installazione di SQL Server 2014 Express.</String>
    <String Name="InvalidPlatformOS">La versione del sistema operativo corrente non supporta SQL Server 2014 Express.</String>
    <String Name="InvalidPlatformOSServicePack">Il sistema operativo corrente non soddisfa i requisiti di livello di Service Pack per SQL Server 2014 Express. Installare il Service Pack più recente dall'Area download Microsoft all'indirizzo http://www.microsoft.com/downloads prima di continuare l'installazione.</String>
    <String Name="InvalidPlatformOSLanguage">La versione italiana di SQL Server 2014 Express può essere installata unicamente in un sistema operativo Windows nella stessa lingua.</String>
    <String Name="AnotherInstanceRunning">Un'altra istanza del programma di installazione è già in esecuzione. Per continuare, è necessario attendere il completamento di tale istanza.</String>
    <String Name="BetaComponentsFailure">È stata rilevata una versione beta di .NET Framework o SQL Server nel computer. Disinstallare le versioni beta precedenti dei componenti di SQL Server 2014, dei file di supporto di SQL Server o di .NET Framework prima di continuare.</String>
    <String Name="InvalidPlatformArchitecture">Questa versione di SQL Server 2014 Express non è supportata per l'architettura del processore corrente.</String>
    <String Name="InvalidUpgradeNotExpress">L'istanza di SQL Server denominata 'SQLEXPRESS' non è un'istanza di SQL Server Express. Impossibile eseguirne l'aggiornamento a SQL Server 2014 Express.</String>
    <String Name="InvalidUpgradeNotExpressCore">L'istanza di SQL Server Express denominata 'SQLEXPRESS' contiene componenti non inclusi in SQL Server 2014 Express. Impossibile eseguire l'aggiornamento di tale istanza in SQL Server 2014 Express. Utilizzare SQL Server 2014 Express with Advanced Services.</String>
    <String Name="InvalidUpgradeLanguage">L'istanza di SQL Server Express denominata 'SQLEXPRESS' è una versione in una lingua diversa rispetto a SQL Server 2014 Express. Impossibile eseguire l'aggiornamento di tale istanza.</String>
    <String Name="InvalidUpgradeWoW">Impossibile eseguire l'aggiornamento dell'istanza esistente di SQL Server Express (x64 WoW) denominata 'SQLEXPRESS' mediante SQL Server 2014 Express (x64). Disinstallare l'istanza esistente di SQL Server Express e riprovare a installare SQL Server 2014 Express (x64).</String>
    </Strings>
    </Package>
    And this is the product.xml:
    <?xml version="1.0" encoding="utf-8"?>
    <!-- SQL Express 2014 VS Bootstrapper : product.xml : Language neutral information -->
    <Product xmlns="http://schemas.microsoft.com/developer/2004/01/bootstrapper" ProductCode="Microsoft.SqlServer.Express.12.0">
    <RelatedProducts>
    <EitherProducts>
    <DependsOnProduct Code=".NETFramework,Version=v4.5" />
    <DependsOnProduct Code=".NETFramework,Version=v4.0" />
    </EitherProducts>
    <!-- Also depends on MSI4.5 or greater, which is included on all of the OS levels supported (see package.xml) -->
    <IncludesProduct Code="Microsoft.Sql.Server.Express.1.0" />
    <IncludesProduct Code="Microsoft.Sql.Server.Express.9.2" />
    <IncludesProduct Code="Microsoft.Sql.Server.Express.10.0" />
    <IncludesProduct Code="Microsoft.SqlServer.Express.10.5" />
    <IncludesProduct Code="Microsoft.SqlServer.Express.11.0" />
    </RelatedProducts>
    <PackageFiles>
    <PackageFile Name="SqlExpressChk.exe" />
    </PackageFiles>
    </Product>
    I've copied the SqlExpressChk.exe file from the SQL Server 2012 Express package, hoping it is the same (2008 and 2012 versions seems the same, so I supposed it also for the 2014).
    I've delete the part in package.xml about the publicKey, since I don't know it and, further, I think I don't need it.
    In the same file, I've inserted custom parameters, first like in the 2008 and 2012 versions, then doing some attempts (without success).
    Did anyone have this problem? How did you have manage it?
    **NOTE**: I'm using my clickOnce deploy in an empty virtual machine, so there aren't any conflicts o something similar.
    More attempts, more failures, always the same error! I'm deleting the optional stuff to study better the core of the xml, but still no success.. does microsoft have a package of sql server 2014 express?

    refer to this link
    http://bootstrapper-manifest-generator-for-vs20.software.informer.com/2.0/
    remember make the reply as answer and vote the reply as helpful if it helps.
    thanks! =)
    SqlServer usually runs a file (SqlExpressChk.exe) to see if there is already an installation and a sql instance called sqlExpress (for the express installations). Do you know how can do this test with the bootstrapper manifest generator?
    I am not able to test it currently, but I assume that will also check whether that has installed.
    You have tested it, right?
    remember make the reply as answer and vote the reply as helpful if it helps.

  • SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

    Hi All,
    I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
    advice in the end was to post a question here.
    SQL Server Nodes, 2014 (12.0.2480.0)
    1 Share witness (on separate subnet)
    1 Cluster
    1 Listener
    I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
    a small table and hit execute.
    The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
    Availability DB is 200Mb and is not actively used. The nodes are synchronised.
    SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
    Questions:
    1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
    2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
    Msg 983, Level 14, State 1, Line 2
    Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
    an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
    Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
    00001090.00002128::2015/02/25-03:05:08.255 INFO  [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
    00001ee4.00002130::2015/02/25-03:05:10.107 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
    00001090.00002128::2015/02/25-03:05:11.888 INFO  [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
    00001090.00002698::2015/02/25-03:05:11.889 INFO  [GUM] Node 2: Processing RequestLock 2:49
    00001090.00002128::2015/02/25-03:05:11.890 INFO  [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
    00001090.00002698::2015/02/25-03:05:11.890 INFO  [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
    00001090.00002128::2015/02/25-03:05:12.890 INFO  [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
    00001ee4.00002130::2015/02/25-03:05:15.107 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
    00001090.00002128::2015/02/25-03:05:16.988 INFO  [GUM] Node 2: Processing RequestLock 1:28
    Thanks in advance.
    Keegan

    Hi Keegan,
    From these event log , what I can see is "Sending request Netname" wasted the time .
    Could you please tell us the network configuration of that cluster nodes ?
    If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
    https://support.microsoft.com/kb/258750?wa=wsignin1.0
    After that please test again .
    Best Regards,
    Elton JI
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • SQL Server 2014 Express why not support Windows 8.1 Pro ?

    Hi All !
    I tried to setup SQL Server 2014 Windows 8.1 Pro x64, but setup says :
    "The operating system on this computer or its service pack level does not meet the minimum requirements for SQL Server 2014. To determine the minimum required operating system supported for this SQL Server release, see Hardware and Software
    Requirements for installing SQL Server 2014 at:
    An error occurred during the SQL Server 2014 Setup operation.
    Error result: -2067529676
    Result facility code: 1220
    Result error code: 52
    For more information, review SQL Server 2014 Setup logs in your temp folder."
    The log file contains :
    07/08/2014 17:08:25.245 Setup launched
    07/08/2014 17:08:25.261 Attempting to determine media source
    07/08/2014 17:08:25.276 Media source value not specified on command line argument.
    07/08/2014 17:08:25.307 Setup is launched from media directly so default the value to the current folder.
    07/08/2014 17:08:25.323 Media source: E:\Setup\Microsoft\SQL 2014 Express\SQLEXPRWT_x64_ENU\
    07/08/2014 17:08:25.339 Attempt to determine media layout based on file 'E:\Setup\Microsoft\SQL 2014 Express\SQLEXPRWT_x64_ENU\mediainfo.xml'.
    07/08/2014 17:08:25.401 Media layout is detected as: Advanced
    07/08/2014 17:08:25.417 Not a slip stream media, so continuing to run setup.exe from media.
    07/08/2014 17:08:25.448 Error: This OS is not supported
    07/08/2014 17:08:27.479 Setup closed with exit code: 0x84C40034
    Why not supported this OS, if the SQL Server 2012 Express x64 is, and Windows Phone SDK 8.0 also.
    Thanks.

    Hey DBT,
    SQL Server 2014 Express supports your operating system.
    You can see the link below the requirements for each version: http://msdn.microsoft.com/en-us/library/ms143506.aspx
    Did you try to restart the computer and then try installing again?
    There are users that it helps them, it might solve the problem but preventing them expect an error and understand why it happens.
    Sometimes it appears as a result of lack of .NET Framework (check the Microsoft article if you meet the requirements before installation).
    If you are interested to View and Read SQL Server Setup Log Files
    I've provided you a link that explains simply how to do this.
    http://technet.microsoft.com/en-us/library/ms143702(v=sql.110).aspx
    Please Mark This As Answer if it helps to solve the issue
    Tzuri Ben Ezra | My Certifications:
    CompTIA A+ ,Microsoft MCP, MCTS, MCSA, MCITP
    |
    FaceBook: Tzuri FaceBook | vCard:
    Tzuri vCard | 
    Microsoft ID:
    Microsoft Transcript 
     |

  • Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

    Hello everyone.
    We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
    packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
    Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
    MCP

    Hi. Yes...
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="SQLISServer" /> 
      <EventID Qualifiers="0">1</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" /> 
      <EventRecordID>469950</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>abtru1a11.oneabbott.com</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
    exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
    runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
    Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
    Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
    behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data> 
      </EventData>
      </Event>
    MCP

  • SQL SERVER 2014 - Project consistency check failed. The following inconsistencies were detected: package.dtsx. has a different ProtectionLevel than the project.

    I am getting the following error when I right click on a package in solution explorer and execute using SQL Server 2014:
    Project consistency check failed. The following inconsistencies were detected: package.dtsx. has a different ProtectionLevel than the project.
    Luckily my solution only has 10 packages.  I have verified and re-verified that everyone is set to dontsavesensitive.
    I have verified and re-verified that the solution has the protection level to dontsavesensitive.
    What on earth is going on here?  I am using windows authentication and have no need for the package to save any sensitive information, nor should there be any.
    Can someone please help me out here?
    The Degenerate Dimension

    Hi MMiligan,
    Just as the error message said, the exactly issue is that the package package.dtsx has a different ProtectionLevel property value than the project.
    So please double check the value of project ProtectionLevel property, like DontSaveSensitive, then make sure all packages in the project use the same ProtectionLevel value.
    If there is still an error message indicated that some packages use a different value, please right-click the indicated package to select View Code, then make sure there is a line like below(the DontSaveSensitive
    protection level corresponds to the value of 0):
    DTS:ProtectionLevel="0"
    The following similar thread is for your reference:
    http://stackoverflow.com/questions/18705161/protection-level-changed-mid-project-now-project-wont-build
    Thanks,
    Katherine Xiong
    If you have any feedback on our support, please click
    here.
    Katherine Xiong
    TechNet Community Support

  • I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

    I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big).  I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64 
    bit).  There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
    OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
    OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
    Msg 7303, Level 16, State 1, Line 11
    Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
    Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change?  How can I get this I series server to link to my sql server 2014 server?
    USE [master]
    GO
    /****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
    EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
    /* For security reasons the linked server remote logins password is changed with ######## */
    EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
    GO
    EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
    GO
    Rich P

    Thank you for this reply.  I went to the link and selected the option for DB2s and ran the install.  Then I started up SSMS.  I copied the same script as above, and it executed successfully.  But when I try to run a query against
    a table in a database on this linked sever -- I get this error message:
    OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
    OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
    Msg 7303, Level 16, State 1, Line 8
    Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
    Do I need to change the line containing -- @provider=N'MSDASQL',  maybe?
    this is the query I'm running:
    select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
    The same exact query runs fine on the sql server 2005 linked server.  Is there something I need to configure?
    Rich P

  • TSQL working in 2008 but not in SQL Server 2014

    Hello,
    We recently have been asked to move from SQL Server 2008 to SQL Server 2014. We are trying to run parallel tests and one of our queries that was working perfectly in 2008 is not working in 2014.
    One of the filter on the our query(from 2008) is we convert a varchar field to date and compare it to anotehr calulated filed ("convert(date,Quick_Data_Start_Date) <= convert(date,(Year_ID_to_Use + '-' + Month_ID_to_Use + '-01'))").
    This worked fine in 2008 but when i try to do similar operation in 2014 it returns no result.
    For testing purposes, instead of converting the field to date format, i manully converted the actual value i.e. instead of using "convert(date,Quick_Data_Start_Date)" when i use "convert(date,'8/1/2014')" the code works fine.
    The field "Quick_Data_Start_Date" comes from a pivot query.
    When i create a temporary table for the pivot query and use the temporary table in  my code and then convert the field on fly the code works fine again.
    Seems like the T sql is not able to convert the field from varchar to date on the fly when coming from a different query. We have tried changing the compatbility level to 100 as well and it still would not work.
    Any suggestions and comments will be really helpful. Thanks.
    Regards,
    GM

    Hello, here is my overall review:
    The query is not optimized … agreed!  But that’s not the issue.
    There are a number of indexes that could be created, a number of minor calculations or evaluation criteria that could be improved to make the query more efficient … again – AGREED.
    The query “as is” runs in just under a minute (on SQL 2008 machine with less memory and slower hard drives).  Adding the indexes would take more time to add than they would save.
    NONE of that should make the query NOT WORK.  These deficiencies might make it run more slowly, but should not cause the query to return no results.
    “order by” shouldn’t make any difference because the query plan isn’t assuming or using any special order
    The main table (~10 M rows) is using a clustered index scan (not efficient, but not the point)
    The Time dimension table is using a non-clustered index seek (so the index is sorted but the data in the table is NOT physically sorted that way)
    The pivot subquery is using clustered index scan (it’s only 6 rows, so who cares)
    Once again, the order by might make it less efficient, but shouldn’t make it fail.  We get no errors or warnings – it just returns no rows.
    Because the query DOES return results when we 
    Either dump the Pivot query result into a #temp table(single row) and use the #temp table instead of the pivot query in the big SQL or  
    The “input” tables are limited to X rows but DOES NOT when the inputs have more rows
            This strongly suggests a memory issue.
    The server has 64 GB of RAM, but this probably isn’t enough to hold millions of rows and calculations.
    Can we turn on some traces to see what’s happening to the data in the query?  How and what are we looking for?
    Once the memory capacity is exceeded, SQL should be pushing these results to a temporary table (either in the local database or the tempdb).  Can we test to see if that is happening? 
    How?
    Is there a permissions issue?
    I have successfully done large copies outside of SQL (copied 300+ GB file from one location to another) that had to use the disk instead of just memory … means the disk write operation
    isn’t restricted from my user account.
    I can also confirm that the account that runs the SQL Service (“Network Service” account) has full permissions to the drives and paths where the mdf and ldf files are stored (including
    master and temp).
    If this doesn’t work, our upgrade is basically frozen and cannot proceed.  I’m really out of ideas … anything?

  • Trouble Turneing on FileStream/Ad Hoc Query with new SQL Server 2014 64-BIt Version

    SQL Server Help,
    I have recently installed SQL SERVER 2014 on my Window 7 SP1 Acer laptop.
    I am trying to do a simple upload of an Excel file into SQL Server using the OPENROWSET command:
    Which I found requires some configuration change I attempted below.
    When I execute this:
    execute sp_configure 'show advanced options', 1;
    RECONFIGURE;
    execute sp_configure 'Ad Hoc Distributed Queries', 1;
    RECONFIGURE;
    GO
    I get this message
    Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
    Msg 5593, Level 16, State 1, Line 2
    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    Msg 15123, Level 16, State 1, Procedure sp_configure, Line 62
    The configuration option 'Ad Hoc Distributed Queries' does not exist, or it may be an advanced option.
    Msg 5593, Level 16, State 1, Line 4
    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    When I go to the SQL Server Services and Properties on the Server and try to change the FileStream options to be on..I get the error:
    "There was an unknown error applying the FILESTREAM settings.  Check the parameters are valid (0x80070002)."
    Perhaps my issue is with the Windows Share Name:  .  I have put in a local driver C:\A_Excel....also the computer name, my user ID.   Is there a special format or way to define a Share Name that I am unaware of?
    Is there a way to fix this?  Can I not load Excel files with a 64-Bit system?  Or what is the easiest way that I can do this with my configuration?
    Thanks for any help.

    FILESTREAM feature is not supported on WoW64. The feature is disabled.
    By the error message it seems you have a 64 bit OS, but have installed a 32 bit SQL Server and here in WoW64 mode filestream seems to be not supported. Install a 64 bit SQL Server instead.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • SQL Server 2014 Bug - with Clustered Index On Temp Table with Identity Column

    Hi,
    Here's a stored procedure.  (It could be shorter, but this will show the problem.)
              CREATE PROCEDURE dbo.SGTEST_TBD_20141030 AS
              IF OBJECT_ID('TempDB..#Temp') IS NOT NULL
                 DROP TABLE #Temp
              CREATE TABLE #Temp
               Col1        INT NULL
              ,Col2        INT IDENTITY NOT NULL
              ,Col3        INT NOT NULL
              CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
              SET IDENTITY_INSERT #Temp ON;
              RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
              INSERT INTO #Temp (Col1, Col2, Col3)
              SELECT 1,2,3
              RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
              SET IDENTITY_INSERT #Temp OFF;
    In SQL Server 2014, If I execute this (EXEC dbo.SGTEST_TBD_20141030)   It works.   If I execute it a second time - It fails hard with: 
            Msg 0, Level 11, State 0, Line 0
            A severe error occurred on the current command.  The results, if any, should be discarded.
            Msg 0, Level 20, State 0, Line 0
            A severe error occurred on the current command.  The results, if any, should be discarded.
    In SQL Server 2012, I can execute it over and over, with no problem.  I've discovered two work-a-rounds:   
    1) Add "WITH RECOMPILE" to the SP CREATE/ALTER statement, or 
    2) Declare the cluster index in the TABLE CREATE statement, e.g. ",UNIQUE CLUSTERED (COL2)" 
    This second option only works though, if the column is unique.    I've opted for the "WITH RECOMPILE" for now.  But, thought I should share.

    Hi,
    I did not get any error Message:
             CREATE TABLE #Temp
               Col1        INT NULL
              ,Col2        INT IDENTITY NOT NULL
              ,Col3        INT NOT NULL
              CREATE CLUSTERED INDEX ix_cl ON #Temp(Col2)
              SET IDENTITY_INSERT #Temp ON;
              RAISERROR('Preparing to INSERT INTO #Temp...',0,1) WITH NOWAIT;
              INSERT INTO #Temp (Col1, Col2, Col3)
              SELECT 1,2,3
              RAISERROR('Insert Success!!!',0,1) WITH NOWAIT;
              SET IDENTITY_INSERT #Temp OFF;
    SELECT * FROM #Temp
    OUTPUT:
    Col1 Col2
    Col3
    1 2 3
    1 2 3
    1 2 3
    Select @@version
    --Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) 
    Oct 19 2012 13:38:57 
    Copyright (c) Microsoft Corporation
    Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    Thanks Shiven:) If Answer is Helpful, Please Vote

  • Moving databases from SQL Server 2012 to SQL Server 2014

    Hi
    I need to move all my SP 2013 databases from a SQL Server 2012 to a SQL Server 2014. I have read these articles:
    http://technet.microsoft.com/en-us/library/cc512725(v=office.15).aspx
    http://sharepointpromag.com/sharepoint-administration/simple-guide-moving-sharepoint-content-databases-new-server
    The TechNet article says:
    The new database server must run either the same version of Windows Server and SQL Server as the existing database server or one of the following versions:
    SQL Server 2008
    SQL Server 2012
    SQL Server 2014
    And the article in SharePoint Pro Magazine says:
    Obviously you’ll need your target SQL server (or instance) installed and configured. It should use the same version and patch level of SQL Server as the source SQL server
    So I'm a bit confused. Which article is right?
    Thanks
    Jakob

    it is fully supported and a simple process to move to a new sql server (anything 2008+ works).  just don't go back in versions.  you can go 2008-2012, 2008-2014, 20120-2014, just not 2012-2008, etc.
    just be sure not to detach/attach the databases in sql, do a sql database backup, then a sql database restore on the new server and point sharepoint (hopefully using aliases, as it makes this all much smoother) to point to the new server.
    Also, be sure to put SP1 and the April 2014 CU or newer on the farm BEFORE moving the databases.  2014 is "supported before the April CU, but there are several compatibility issues prior to april CU.  one example is that user profile sync doesn't
    work properly with sql 2014 if sharepoint is not at least april 2014 CU.
    hope that all is clear and helps you out, let me know if there are more questions.
    Christopher Webb | Microsoft Certified Master: SharePoint 2010 | Microsoft Certified Solutions Master: SharePoint Charter | Microsoft Certified Trainer| http://tealsk12.org Volunteer Teacher | http://christophermichaelwebb.com

Maybe you are looking for