I have a Microsoft VPC image (MDAX 2012) with a SQL server 2012 R2 Enterprise edition istalled. It was delivered with an evaluation license. This has expired and I have downloaded an image with SQL Server 2012 R2 Enterprise edition. I have started it and used Maintenance Edition upgrade, selected license key, selected instance and upgraded. I am still not able to start the SQL service as the license period has expired and I cant start the SSMS.

When I rerun the upgrade I can see that the SQL server instance (MSSQL server)  has changed to Enterprise Edition while Instance Tabular and Powerpivot still are evaluation Shared components have no edition.

I have tried to upgrade all instances without any luck.

Can you assist me in what I am doing wrong

/Erik Kornerup

I have a client that someone installed the enterprise 2008 sql server evaluation edition on a production server. We just found out about this issue a couple of days ago. Yesterday we ordered SQL server 2008 standard edition from dell through volume licensing. Today dell told us that they were not sure how soon the fulfillment on this would happen. I have in the last few hours talked with Microsoft Volume Licensing and Pro Support.  Volume licensing worked hard to find a way to expedite the order or find a work around for us on the server to keep the evaluation edition running for a bit longer to make sure it doesn't turn itself off before we can install the full version we have purchased. They refereed us to Pro Support when they were unable to find a fix. Pro support sent us to a few weblinks that didn't address the issue and then told us to post our question here as they were unable to help us.

Is there anyway to extend the trial version by a few days to give us a bit of a grace period to allow the fullfulment on our Full Version SQL Server 2008 standard to show up?

I very much would appreciate any help that anyone can give me on this issue. If the evaluation license expires before we install the upgrade it will shut my client down cold as in out of business.

Thank you,

Scott Carle
Carle Enterprises, Inc.

Hi,

I have SQL Server 2012 Enterprise / Standard Edition - Per core and Windows Server 2012 is in VM environment running on VMware ESX and not Hyper V 

Can I install SQL Server 2012 Ent/Std on Windows Server 2012 Standard Edition (VM machines running on VMware ESX) or SQL 2012 is supported on VM machines running on Hyper-V

Regards,

Nikhil P Desai

Hi

I have SQL Server 2014 Standard Edition- Per core and Windows server has two processor each with 10 cores- total 20 cores

SQL Server 2014 Standard Edition has limitation of using 16 cores.

Suppose if I install two SQL Server instances only on one Windows 2012 server having 20 cores so how can I come to know number of cores used by each SQL Server instances.

Regard,

Nikhil P Desai

Hi

I would like to upgrade SQL Server from SQL Server 2005 - 9.00.4035.00 (X64) Enterprise Edition (64-bit) on Windows Server 2003 R2 bit) (Service Pack 2) to SQL Server 2014 Standard Edition (64-bit) on windows server 2012 R2 (64-bit). How to do this? What are the options?

Thanks in advance...

- KP

I accidentally uninstalled SQL compact server so I got the download from Microsoft website, but when I try to run installer a box pops up and says ''preparing file location'' then box disappears and nothing else happens. I looked and the file location it shows does not exist.

I am a little out of my league here any help would be appreciated.

Hi,

I am trying to isntall SQL Server 2012 on Windows Server 2008 R2, but the Database Engine Services failed to install, and I cannot start the MSSQLSERVER Service after installation.

Installation error:

Error installing SQL Server Database Engine Services Instance Features
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error code: 0x851A001A

W3WP.EXE Crash:

I noticed that during installation w3wp.exe has crashed:

Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeInitializationException
Stack:
   at System.Web.Caching.SqlCacheDependencyManager.Dispose(Int32)
   at System.Web.HttpRuntime.Dispose()
   at System.Web.HttpRuntime.ReleaseResourcesAndUnloadAppDomain(System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

A process serving application pool 'HTTP Pool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4544'. The data field contains the error number.

MSSQL Service:

When I try to start the MSSQL service, I get the following errors in the event log:

- For target, "5B2DA06D-898A-43C8-9309-39BBBE93EBBD.package0.event_file", the parameter "filename" passed is invalid. Target parameter at index 0 is invalid
- Event session "system_health" failed to start. Refer to previous errors in the current session to identify the cause, and correct any associated problems.
- Script level upgrade for database 'master' failed because upgrade step 'u_tables.sql' encountered error 25641, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
- Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

Installation Log:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893606
  Start time:                    2013-06-10 23:02:24
  End time:                      2013-06-11 00:06:27
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Machine Properties:
  Machine name:                  SERVER01
  Machine processor count:       4
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered

Package properties:
  Description:                   Microsoft SQL Server 2012 Service Pack 1
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  Installation location:         N:\Software\Windows Server\Microsoft SQL Server 2012 SP1 (x64)\x64\setup\
  Installation edition:          Web

  Slipstream:                    True
  SP Level                       1
  Patch Level:                   11.1.3128.0

Product Update Status:
  Success: KB 2674319, KB 2793634

Product Updates Selected for Installation:
  Title:                         Service Pack 1
  Knowledge Based Article:       KB 2674319
  Version:                       11.1.3000.0
  Architecture:                  x64
  Language:                      1033

  Title:                         SQL Server 2012 SP1 GDR Product Update
  Knowledge Based Article:       KB 2793634
  Version:                       11.1.3128.0
  Architecture:                  x64
  Language:                      All

  Update Source:                 MU

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130610_224552\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             E:\MSSQL
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER1
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          <empty>
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           ELXTECH\Administrator
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    1
  UIMODE:                        Normal
  UpdateEnabled:                 true
  UpdateSource:                  MU
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130610_224552\ConfigurationFile.ini

Detailed results:
  Feature:                       Management Tools - Basic
  Status:                        Passed

  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A001A
  Error description:             Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130610_224552\SystemConfigurationCheck_Report.htm

I've been having a lot of trouble installing SQL Server 2012.  This was a new install, no other versions of SQL Server were on the machine.

After several restarts, install attempts, and running the installer in Repair mode, Management Studio finally installed but there is no localhost.  But it can connect and query to remote instances.

The installer will not create a local instance.  When I try to connect to localhost or "." in SQL Management Studio, it fails and I get this error:

""

TITLE: Connect to Server
------------------------------

Cannot connect to ..

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

------------------------------
The system cannot find the file specified

""

In Manage->services when I try to start the MSSQLSERVER service it fails and I get this error:

""---------------------------
Services
---------------------------
Windows could not start the SQL Server (MSSQLSERVER) service on Local Computer.
Error 2: The system cannot find the file specified.

""  the service log on tab is set to: NT Service\MSSQLSERVER

Same thing happens when I try to start SQL Agent

""

---------------------------
Services
---------------------------
Windows could not start the SQL Server Agent (MSSQLSERVER) service on Local Computer.
Error 1068: The dependency service or group failed to start.

"" the service log on tab is set to: Network Service

I've spent a day just trying to install SQL 2012, any suggestions welcome!

much appreciated,

I've been reading some documentation from Microsoft regarding an AWESOME feature and noticed my clippings are "relatively" old.  Microsoft came out with a document called "Patching SQL Server Failover Cluster Instances with Cluster-Aware Updating (CAU)" which basically states that using this awesome feature with a cluster with Always On is not supported.

https://msdn.microsoft.com/en-us/library/jj907291.aspx

So... My questions:

Is that document is still correct on SQL Server 2012?  Meaning, does a subsequent version fix this?

Does SQL Server 2014 solve this?

How about SQL Server 2016?

My shop is pretty consistently using Clusters with AO, so I'm dying to find a supportable way to do this.

Thanks,

Keith

W. W. Whiteside

Can someone update this list of what all these products are in this feature pack. I'm trying to find the Data Mining Add-in for Excel but I'm not sure which file it is.

https://www.microsoft.com/en-in/download/details.aspx?id=42295

SQL Server Setup has encountered the following problem:
[Microsoft][SQL Native Client][SQL Server]Cannot update user instances.
Reason: Cannot start user instance 'FF9C0784-9B79-48' for update.
Error code: 0x3c0c..
To continue, correct the problem, and then run SQL Server Setup again.

Any idea what this means and how to fix it?

I ran below commands

SQLEXPR.exe /qb UPGRADE=SQL_Engine,SQL_Data_Files,Client_Components,Connectivity INSTANCENAME=MSSQLSERVER

and

SQLEXPR.exe /qb UPGRADE=SQL_Engine INSTANCENAME=MSSQLSERVER

Thanks.

I am attempting to install SQL Server 2008 Enterprise Trial and receive the follow error during installation.

"The SQL Server 2005 Express Tools are installed. To continue, remove the SQL Server 2005 Express Tools."

I have used Add or Remove programs to remove all components of SQL Server 2005 Express.  I have even reinstalled the Workstation Tools of SQL Server 2005 just so I could indiviually remove those tools, and then completly removed the SQL 2005 installation.

I have used regedit to search for any instance of SQL Server 2005, there is none.

There is still an entry for SQL Server Mangement Express in my all programs listing.  However trying to launch that program fails with errors, so it is partial still installed.

Can anyone tell me how to wipe out these last bits of SQL Server 2005 Express Tools?  I have tried everything I have found searching this forum to no avail.

Bill

Hello

Currently we are evaluating a PureStorage solution.
This storage unit is connected using FC adapter.

Our SQL Server 2012 instance is set to use default network packets size 4K.
I read the FC packet size is 2048.

Would it change something to change the SQL packet size to a value lower than 2048 or is it useless?

Florent

Running SQL Server 2012 SP2 CU6 on Windows Server 2012 R2, and trying to apply service pack 3 for SQL Server 2012. Ran into an issue where SP3 fails due to Object Reference not set to an instance of an object.  We are using the default instance name MSSQLSERVER.

I tried repairs and uninstalling SP3, all failed due to object reference errors.

At this time, I am unable to post the detail.txt file.

What are some things I can look for in the detail.txt file that could point to the real problem?

Any Assistance would be appreciated.

DJ

Hello,

Here is the thing

I have 2 sql servers. each has ent instance with AG configured(servers in a cluster but instances are not) and several non clustered sql2008r2 instances.

I need to patch those 2008r2 instances. If I use the wizard I have an error rule:Cluster_IsOnlineIfClustered

To workaround this I extracted sql2008r2sp2 in a folder and ran

Setup /SkipRules=Cluster_IsOnlineIfClustered /action=patch

But it failed. I can't patch any instance. I would like to place log file here but it's to big.

How to find main error in this huge log ? Thanks

Since installing SQL Server SP3 in production, we are seeing a lot of DB Connection timeouts.  Found several articles pointing to enabling IPV6 on the database server.

Does SP3 require IPV6 to be enabled?  Due to Security, we were told we must disable IPV6, and use only IPV4.

Below is an example of the errors we are seeing.

An exception was handled, but could not be added to the error log in the database. The following values are associated with the error.

ScopeID=8ae2fa6a-4e85-4bd8-9679-c1ce8ad8cd38
UserID=984a9529-d747-40ec-9a72-ea03067f3fa9
SessionID=ommsk02gwxzytbh40r5snhj4
Process= ()
Error Date=2/19/2016 3:56:02 PM
Error Text=Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=14742; handshake=12312;
Error Inner Text=System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
Error Stack Trace=   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection);   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection);   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection);   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions);   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry);   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry);   at System.Data.SqlClient.SqlConnection.Open();   at App.Web.AppForms.MainMenu.OpenConnection();   at App.Web.AppWebForms.MainMenu.Page_Load(Object sender, EventArgs e);   at System.Web.UI.Control.OnLoad(EventArgs e);   at System.Web.UI.Control.LoadRecursive();   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
TransactionInfo=
Error Type=EXCEPTION
Error Source=.Net SqlClient Data Provider

Any ideas?

DJ

On my work laptop, I am running Windows 7 Enterprise (SP1). Several months ago, I installed SQL Server 2016 CTP 2.1, and it was installed successfully. As it happens, I do not need 2016 and I believe it being installed is causing some undesired consequences, so I am attempting to uninstall it. However, as the OS requirements have changed to require Windows 8 or higher to install, I am unable to uninstall. 

So how can I run an uninstall when it thinks my OS is not high enough, despite the program already being installed?

Hi

I have few doubt regarding downgrade and upgrade

Suppose I have 2 Instances of different Version

First Scenario

SQL Server 2014 Standard Edition with database named 'xyz' having compatibility level of SQL 2012 i.e. 110 (these 'xyz' database upgraded from SQL server 2008 compatibility level 110 to instance to SQL Server 2014 with compatibility level of SQL 2012 i.e 110)

I have another instance of SQL Server 2012 Standard Edition. Is it possible to restore 'xyz' database from instance of SQL Server 2014 to instance of SQL Server 2012.

Second Scenario

SQL Server 2014 Standard Edition with database named 'xyz' having compatibility level of SQL 2014 i.e. 120 (these 'xyz' database upgraded from SQL server 2008 compatibility level 110 to instance to SQL Server 2014 with compatibility level of SQL 2014 i.e 120)

I have another instance of SQL Server 2012 Standard Edition. Is it possible to restore 'xyz' database from instance of SQL Server 2014 to instance of SQL Server 2012.

Regards,

Nikhil P Desai