SQL Server 2014 issues

Hello:
I have bumped upon a design issue with SQL Server 2014.
I want to report this to Microsoft, where it can be addressed and corrected in the upcoming Service packs.
This is something critical.. (that's what at least....I feel).
Please let me know the link/Forum where I can post this.
Thanks

Two possibilities. On Microsoft connect
https://connect.microsoft.com/SQLServer/Feedback
or in SQL Server forums.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Similar Messages

  • Hybrid Connection fails for Windows SQL Server 2014 - SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted

    Hello,
    I have configured BizTalk Services Hybrid Connection between Standard Azure Website and SQL Server 2014 on premise.
    Azure Management portal shows the status of Hybrid Connection as established.
    However, the website throws an error when trying to open a connection
    <
    addname="DefaultConnection"
    connectionString="Data
    Source=machine name;initial catalog=AdventureWorks2012;Uid=demouser;Password=[my password];MultipleActiveResultSets=True"
    providerName="System.Data.SqlClient"
    />
    (The same website, with the same connection string deployed on SQL Server machine works correctly).
    I tried various options with the connections sting (IP address instead of machine name, Trusted_Connection=False, Encrypt=False, etc. the result is the same
    [Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
    [SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.
    I tried various machines - on premise and a clean Azure VM with SQL Server and it results in the same error - below full stack
    The certificate chain was issued by an authority that is not trusted             
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.            
    Exception Details: System.ComponentModel.Win32Exception: The certificate chain was issued by an authority that is not trusted
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.                  
    Stack Trace:
    [Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted]
    [SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)]
    System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5341687
    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +546
    System.Data.SqlClient.TdsParserStateObject.SNIWritePacket(SNIHandle handle, SNIPacket packet, UInt32& sniError, Boolean canAccumulate, Boolean callerHasConnectionLock) +5348371
    System.Data.SqlClient.TdsParserStateObject.WriteSni(Boolean canAccumulate) +91
    System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode, Boolean canAccumulate) +331
    System.Data.SqlClient.TdsParser.TdsLogin(SqlLogin rec, FeatureExtension requestedFeatures, SessionData recoverySessionData) +2109
    System.Data.SqlClient.SqlInternalConnectionTds.Login(ServerInfo server, TimeoutTimer timeout, String newPassword, SecureString newSecurePassword) +347
    System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) +238
    System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) +892
    System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) +311
    System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData) +646
    System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) +278
    System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) +38
    System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +732
    System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) +85
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +1057
    System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +78
    System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) +196
    System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +146
    System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +16
    System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) +94
    System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +110
    System.Data.SqlClient.SqlConnection.Open() +96
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +44
    [EntityException: The underlying provider failed on Open.]
    System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +203
    System.Data.EntityClient.EntityConnection.Open() +104
    System.Data.Objects.ObjectContext.EnsureConnection() +75
    System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) +41
    System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable<T>.GetEnumerator() +36
    System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) +369
    System.Linq.Enumerable.ToList(IEnumerable`1 source) +58
    CloudShop.Services.ProductsRepository.GetProducts() +216
    CloudShop.Controllers.HomeController.Search(String SearchCriteria) +81
    CloudShop.Controllers.HomeController.Index() +1130
    lambda_method(Closure , ControllerBase , Object[] ) +62
    System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters) +14
    System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +193
    System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +27
    System.Web.Mvc.Async.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41() +28
    System.Web.Mvc.Async.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _) +10
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
    System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) +32
    System.Web.Mvc.Async.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() +58
    System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +225
    System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) +10
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
    System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) +34
    System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +23
    System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +99
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +50
    System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +27
    System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +14
    System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
    System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +39
    System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
    System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +29
    System.Web.Mvc.Controller.System.Web.Mvc.Async.IAsyncController.EndExecute(IAsyncResult asyncResult) +10
    System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +25
    System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +23
    System.Web.Mvc.Async.WrappedAsyncResult`1.End() +55
    System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +31
    System.Web.Mvc.MvcHandler.System.Web.IHttpAsyncHandler.EndProcessRequest(IAsyncResult result) +9
    System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +9651188
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.36213            
    Regards,
    Michal
    Michal Morciniec

    Same issue here, looking for more information !

  • 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

  • Issue of Text Qualiffier after upgrading to SQL Server 2014 Standard

    Hi,
    I'm facing an issue of Text Qualifier after I upgrading my system to SQL Server 2014 Standard Edition (Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
        Feb 20 2014 20:04:26
        Copyright (c) Microsoft Corporation
        Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    I have a csv file with format: Text Qualifier is double pipes ||, Vertical Bar (|) as Column Delimiter and  Row Delimiter is CRLF.
    For example file:
    ||Col1|||||Col2||
    ||ABC|||||XYZ||
    This file is working OK in SQL Server 2008 R2 (SP2) but it does not work in SQL Server 2014. It raised error message while running.
    Error: An error occurred while skipping data rows.
    [SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on MediaAgencyGroup returned error code 0xC0202091.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
    code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the failure.
    Any suggestion here?
    Thanks,

    Yes
    There's a difference in the way text qualifiers are parsed from 2012 onwards
    see
    http://www.proactivespeaks.com/2012/06/22/my-5-favorite-sql-2012-ssis-features-so-far/
    http://blog.concentra.co.uk/2013/06/24/ssis-2012-flat-files-now-greatly-improved-but-are-they-good-enough-yet/
    ANyways my preferred way to do this is as below
    http://visakhm.blogspot.in/2014/06/ssis-tips-handling-embedded-text.html
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Issues enabling AlwaysON in SQL Server 2014 Standard

    Hi 
    I am trying to configure AlwaysOn and having issues enabling in SQL Server configuration manager
    OS : Windows Server 2012 R2
    SQL : SQL Server 2014 Standard Edition
    Here is what i see in config manager : 
    The AlwaysOn Availability Groups feature requires the x86(non-Wow) or x64 Enterprise Edition of SQL Server 2012 (or later version) running on Windows Server 2008 (or later version) with WSFC hotfix KB 2494036 installed. This SQL Server edition and/or Windows
    Server system do not meet one or more of these requirements.
    I patched both the nodes and ran the cluster validation as well which didn't report any missing patches. Couldn't find any documentation/solution for this. 
    Can someone please help me with this ???

    Thanks. 
    Is the configuration of Always on FCI is same as Traditional WSFC ?
    Yes just think of it as a regular clustered sql instance
     An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes
    and, possibly, across multiple subnets. 
    https://msdn.microsoft.com/en-us/library/ms189134(v=sql.110).aspx

  • DB-Library BCP issue with SQL Server 2014

    Hello,
    My application uses DB-Library (ntwdblib.dll) to communicate with SQL Server 2014. We are having issues calling bcp related functions like bcp_init which always returns FAIL status. Our application was working fine with SQL Server 2012 and all other previous
    SQL releases. But we are getting below error in SQL 2014,
    msg 4801, state 1, severity 16 : Insert bulk is not supported over this access protocol.
    Can anyone please help ?
    Thanks,
    Himanshu

    Hi Himanshu_kus,
    Is this still an issue, or can we close the thread?
    [Personal Site] [Blog] [Facebook]

  • Issues in Importing Access Database into SQL Server 2014 Express

    I have been trying to import the Northwind.accdb database into SQL Server 2014 Express using the SQL Server Import and Export Wizard. Every time I try, I end up with the following messages. I have reviewed previous replies given to similar queries but
    I am not getting anywhere. Appreciate if anyone can help. Thanks.
    Error 0xc0202009: Source - Customers [1]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E37.
     (SQL Server Import and Export Wizard)
    Error 0xc02020e8: Source - Customers [1]: Opening a rowset for "`Customers`" failed. Check that the object exists in the database.
     (SQL Server Import and Export Wizard)
    Exception from HRESULT: 0xC02020E8 (Microsoft.SqlServer.DTSPipelineWrap)

    Tried that. It doesn't support SQL Server 2014. Tried using SQL Server 2012. Ended with following error:
    First I got this message:
    You are connecting to SQL Server version that is different the version specified in the SSMA project. This may lead to schema not converted correctly and synchronisation issues. Do you want to continue?
    I replied with 'Yes' and that ended with the following error.
    Connection to SQL Server established successfully.
    Connection string: Server=VPCL12S1E\SQLEXPRESS2014;Trusted_Connection=TRUE;Encrypt=FALSE;TrustServerCertificate=FALSE;Application Name=SSMA for Access;Pooling=False;
    Error collecting data. See the inner exception for details.

  • SQL server 2014 DB creation issue

    Hi,
    I have created VM (windows server 2012) which is installed with SQL server 2014 standard version from gallery. when I tried to create a DB in SQL server it is taking too much time (more than half an hour it will be in the executing state) to create. so I
    restarted SQL server and finally deleted the VM and created new one but no luck, the problem remains the same.
    please help me to resolve this.
    thanks in advance!!
    regards,
    Naveen

    Naveen you need to show us the query you ran to create Database. If you scripted out Database script from some other huge database it would have huge initial size and it would take time for SQL Server to get thoes space plus instant file initialization
    also comes into picture. If that is missing it would again take too much time
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Unable to install SQL Server 2014 Express LocalDb on Windows 8.1 Update 1

    Apologies if this is not the right place or this has been posted before (I looked and didn't find anything)
    I am unable to install SQL Server 2014 Express LocalDb on Windows 8.1 Update 1, as I get an 'Operating System not Supported' error message right away.
    What can I do to get this working?

    Hi Zgreve,
    Usually, from
    hardware and software requirements for installing SQL Server 2014, we can install SQL Server Express version on the Windows 8.1. For more information, see:
    Microsoft SQL Server 2014 Express.
     Before you install SQL Server 2014 Express version, you should ensure installing the .NET Framework 4, then run as administrator for the SQL Server setup.exe again.
     There is a similar detail about install SQL Server Express LocalDB via GUI and command line. You can also review the following steps.
    http://www.mssqltips.com/sqlservertip/2694/getting-started-with-sql-server-2012-express-localdb/
    If the same error about OS still exists,  I recommend you submitting a feedback to Microsoft such issues at
    https://connect.microsoft.com/SQLServer/Feedback, Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the
    exciting projects on Microsoft Connect.
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

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

  • Power Pivot Configuration error while refreshing connection on excel sheet for SharePoint 2013 and Sql server 2014 using BISM file connection

    I am getting following error while refreshing connection on excel sheet in power pivot gallery,
    my scenario,
    using BISM file connection to create and  refresh power pivot excel sheet in power pivot gallery
    throws error and we have sql server 2014 CU6 updated installed plus sharepoint 2013. i checked following msolap110.dll is available in our environment but assembly
    Microsoft.AnalysisServices.ChannelTransport is not available. 
    i found error in event viewer,
    "Activation context generation failed for "C:\Program Files\Microsoft Analysis
    Services\AS OLEDB\110\msolap110.dll". Dependent Assembly
    Microsoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
    not be found. Please use sxstrace.exe for detailed diagnosis.
    what should i do to fix it?
    Thanks for help.
    Deepak Patel

    Rebecca,
    yes, this is issue i am getting.
    Activation
    context generation failed for "C:\Program
    Files\Microsoft Analysis Services\AS OLEDB\110\msolap110.dll".
    Dependent AssemblyMicrosoft.AnalysisServices.ChannelTransport,processorArchitecture="MSIL",publicKeyToken="89845dcd8080cc91",version="11.0.0.0" could
    not be found. Please use sxstrace.exe for detailed diagnosis.
    let me know if you can find fix for it.
    THanks,

  • Export to Excel Error in SQL Server 2014 Report Builder/Viewer

    Hi,
    I am using the 2014 version of ReportViewer in a WinForm to display an RDL report.
    The report was originally created in Report Builder 2.0 (SQL 2008 R2), but has since been edited in Report Builder 3.0 (SQL 2014).
    The report loads and displays OK, and even exports to Word and PDF. But when exporting to Excel and then opening the Excel document, the following error occurs:
    "We found a problem with some content in <filename>. Do you want us to try and recover as much as we can? If you trust the source of this workbook, click Yes."
    If you click Yes, then a second message appears:
    "Removed Part: /xl/styles.xml part.  (Styles)
    Repaired Records: Cell information from /xl/worksheets/sheet1.xml part"
    The Excel document then opens, and the data is there, but there is no formatting (no border columns, colours, bolds etc.)
    The three interesting things are:
    - When exported from SQL 2008 R2 Report Builder 3.0, which exports to .xsl instead of .xslx, it works
    - A brand new report created in 2014 Report Builder 3.0 exports to .xslx great
    - In Report Builder 2014, I stripped everything back and removed all rows and columns so the original table in the report only has one empty row and column it the export still errors - it is only by removing the original table and creating a brand new table
    that export works OK
    It appears to be a problem with the tablix, but ideally we don't want to have to recreate our reports from scratch to fix this issue.
    Has anyone come across an issue like this before, and know of any potential resolutions to it?
    Thank you.

    Hello,
    Based on your description, you render a report originally created in Report Builder 2.0 (SQL 2008 R2) and export the report to excel with format of Excel 2007-2010.
    Edit the report in Report Builder will not upgrader the report. In that case the report still with SSRS 2008 R2 RDL schema. Please try to upgrade the report by open the report in Report Designer in SQL Server Data Tools (SSDT) and then try again.
    If you don’t want to upgrade the report, please try to export the report
    with Excel 2003 rendering extension and check if the issue persists.
    The SQL Server 2014 and SQL Server 2012 Reporting Services Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010 with .xlsx as file extension. Only the Excel rendering extension is available by default.
    You must update the Reporting Services configuration files to make the Excel 2003 rendering extension available.
    For example, changing the value of Visible to
    true in the following line in the RSReportServer.config:
    <Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering"
    Visible="true"/>
    Reference:Upgrade Reports
    Exporting to Microsoft Excel (Report Builder and SSRS)
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • Install SQL Server 2014 in Windows Server 2012 R2

    Hi,
    I had install a Windows server 2012 R2 Standard version in my VM and i make it as my domain server as well. I had create another account "ABC" and login with this new created account "ABC" in the same machine to install SQL server 2014,
    it give me a warning for rule "Computer domain controller" which I understand that I'm installing the SQL server in the domain controller is not recommended. I continue to install and when reach to Server Configuration, I found that SQL Server Analysis
    Service account is missing where I cannot found it. 
    May I know is there any features that I missing or any way to make it done?
    Thank you.

    I found that SQL Server Analysis Service account is missing where I cannot found it. 
    May I know is there any features that I missing or any way to make it done?
    Thank you.
    IIRC (If I remember correct)Configuring Analysis service account is after you have passed the Server configuration page. Did you selected analysis service checkbox when  on feature selection page. What editoon of SQL server 2014 you are installing are
    you installing express edition ? SSAS is not present in express edition
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

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

  • Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

    I've been searching for HOURS how to resolve this issue:
    I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
    ======================================================================================
    Rule Check Result
    Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
    This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
    =====================================================================================
    This is the Configuration Report issue:
    Microsoft SQL Server 2014 - System Configuration Check Report
    UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
        KJRTMUpgradeBlockRule     
    Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack.     Failed     The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
    required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
    ====================================================================================
    I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
    out!!!
    Thanks.

    Hi again
    This is the scenario:
    -I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
    -As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
    resolved immediately with the Windows Update service.
    -Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
    Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
    with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
    Now we are on 12.0.2000.8
    Thanks anyway and all of you for your interest!!!

Maybe you are looking for