Hi All,

We  performed installation of named SQL Server 2008R2 instance. During the setup instead of configuring latin1_general_ci_as, the defualt collation sql_latin1_general_cp1_ci_as was selected . Now i want to modify the server collation to latin1_general_ci_as. Is it possible without a reinstall. 

I see couple of blogs, where rebuild is suggested and in few other blogs trace flag is used T4022,T3659. Will it work in my case . 

can i modify from sql_latin1_general_cp1_ci_as to latin1_general_ci_as.

Thanks

Udhayan

Good evening all,

Im trying to install SQL 2016 enterprise edition on windows 2012 r2 datacenter.

though i followed all the steps and installed all the prerequisites i'm getting below error.

(Error KB2919355)

even after restarting server and trying to install but same error:

steps i followed downloaded and installed belolw.

1. Clearcompressionflag.exe38 KB

2. Windows8.1-KB2919355-x64.msu690.8 MB
3. Windows8.1-KB2932046-x64.msu48.0 MB
4. Windows8.1-KB2959977-x64.msu2.8 MB
5. Windows8.1-KB2937592-x64.msu303 KB
6. Windows8.1-KB2938439-x64.msu19.6 MB
7. Windows8.1-KB2934018-x64.msu126.4 MB

Thanks,

Vijay

I'm having some trouble upgrading from an Entreprise edition of Sql Server 2008 R2 SP2 to an Evaluation of Sql Server 2014 SP1, and I begin to wonder if it is possible? I didn't found anything about it in the supported version and edition upgrade guide :

https://technet.microsoft.com/en-us/library/ms143393(v=sql.120).aspx

It says that you can't migrate from SQL Server 2014 Entreprise to Evaluation, but it says nothing about previous editions.

Thanks.

I have tried cleaning, then installing 2008 SQL server Express on Vista Ultimate 3 times and spent hours on this. I have installed regular SQL server on 2003 server with no issues many times, but I have huge issues with 2008 SQL server Express. I keep getting the proceeding errors.

Any ideas?

Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x0A2FBD17@1211@1
  Configuration error description: A MOF syntax error occurred.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\SystemConfigurationCheck_Report.htm

Have an interesting situation.

I have a NeverFail cluster on which I loaded SQL Server 2005 and SP1.

All was great. Both nodes had no issues with the initial setup or the SP1 update.

When I forced a failover to the inactive node, MOST of the services like SSIS, Full-Text and SQL Browser came up like a champ.

BUT ... the SQL Server service and the SQL Agent did not come up (or shall I say not fully).

I am now looking at the SQL Server Configuration Manager and I see the following for the SQL Server service:

"Name"      shows the RED block icon for the SQL Server

"State"       shows "Change pending ..."

"Start Mode" is set to Manual

"Log on as"   has my domain account listed

"Process ID"   has the number 2956 (so it has started somewhat).

I then click open the SQL Service item and it shows that it is stopped.

I am given the option to START the service. When I try to start it, the meter bar comes up and moves slowly to the end and then an error returns of ...

"The request failed or the service did not respond in a timely manner. Consult the event log or other applicable errors logs for details"

If I look under windows Services in the Admin Tools section... I see the services for SSIS, FT and Browser listed and started BUT I see SQL Server says its "starting".

If I click open the service from here, once again it show "starting" and all of the option buttons to Stop-Start-Pause-Resume are grayed out and I am not able to use them.

I have looked in the Windows Event Logs for any events but none are present. 

Now I know why the SQL Agent is not running, and of course that is due to is dependency on SQL Server being up and running.

First off WHAT does the "Change pending" message mean?

Then what other logs can I look at for some help or is there someone who has the answers to this dilemma.

Thanks and have a great evening

I have Signed up for SQL sever on Linux evaluation.

On March 16th, I received a download link from SQL server community for release candidate of SQL Server 2016.

But the link takes me to regular SQL server download page.

Was anyone able to successfully install SQL server on linux using the link provided in community newsletter?

Hey Guys. Have a quick question. I have a fellow engineer here who wanted to set up a SQL server for me for a Skype for Business installation. he did not specifically use the SQL sysprep tool, he just sysprepped the box and renamed the default instance and indicated that it will work fine. After doing some googling, I have found a decent few opinions indicating that this is frowned upon and could cause issues. I am not even remotely a SQL guy but I have experience elsewhere so I'm a bit hesitant to proceed this way.

I wanted to get the opinions of the folks on the SQL board here. Is this safe for production, or is this risking immediate or future issues? Thanks all and please let me know if you need any further info. 

I have an existing 2 node active/active SQL 2012 FCI using local storage for TempDB. I added another standalone instance of SQL 2012 on the WSFC (I want to reiterate the fact that it's a standalone instance not clustered). The standalone instance is using local storage and works fine when Node1 is active but if the instance that resides primarily on Node1 fails-over than the stand-alone instance stops accepting connections but SQL Server Service is still up and running. I'm not sure what the issue could be we're using static ports 1433 for the clustered instances and 49664 for the stand-alone instance. Does anybody have any experience with this type of setup?

Johnny

Hi,

my default directory for "Program Files" is on "D:\", when I install SQLServer 2012 SE on my Windows 10 it fails saying can't find the installer log file on "'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160504_164014' infact this path is on D:\ I can't find anyway to make it change on correct path: any idea?

Hi,

We installed a SQL 2012 version in our PROD instance with 2008R2 version running on the same server. We are facing a couple of issues as listed below

1. When we open report manager URL in IE it keeps asking for username password whereas Chrome and Firefox doesn't have the same problem. The other browser allow user to run report, browse the report manager. The reporting service is running with LocalSystem account. When we tried network service we had the same issue in all browsers.

2. In chrome the reports were working fine but after some time when we run report we are getting errors as 

Exception of type System.OutOfMemoryException was thrown

3. SQL Server Agent jobs says login failed for user or unable to connect to instance name. We have created all the needed proxy accounts to run the jobs. The same jobs run in DEV instance where we have only 2012 version running.

Did anyone encounter such issues. How to resolve them?

Thanks,

Gayatri

I have a SQL Server RC2 instance that has expired. When I try to go into Windows Services and start the SQL Server instance it fails to start and an error log entry in the Windows Application event log indicates this is due to "trial expiration". I see RC3 was release late last month and I'd like to upgrade to RC3. I've downloaded the SQL Server 2016 RC3 ISO and made it through all the wizard questions only to have it give me the following error

It appears an upgrade cant occur unless the SQL Server instance to be upgraded is running. In this case the SQL Server instance to be upgraded can not be started because the trial is marked as expired. What can I do? I have quite a bit of data in this database that needs to be preserved.

Thank you.

I attempted to upgrade an expired installation of SQL 2012 Evaluation version to 2014 Developer Edition. Programs and features list the current version as Microsoft SQL Server 2012 (64-bit) so I ran the 64-bit install of 2014. Since the evaluation had expired the SQL service would not start and I ran the installer from the command line as noted in this KB article (https://support.microsoft.com/en-us/kb/2020443).

The install cannot complete because the BlockMixedArchitectureUpgrade test fails.

I'm including a portion of the installation log. Can you help me determine what the cause of the failure is and how to resolve it?

(10) 2016-08-18 07:24:23 Slp: Initializing rule      : SQL Server 2014 edition upgrade
(10) 2016-08-18 07:24:23 Slp: Rule is will be executed  : True
(10) 2016-08-18 07:24:23 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionUpgradeMatrixCheck' looking for installed version data for feature package 'sql_as_Cpu64'.
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionUpgradeMatrixCheck' looking for installed version data for feature package 'sql_engine_core_inst_Cpu64'.
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionUpgradeMatrixCheck' looking for installed version data for feature package 'sql_rs_Cpu64'.
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionUpgradeMatrixCheck' detection result: IsValidEditionUpgrade=True IsEditionDownGradeFalse
(10) 2016-08-18 07:24:23 Slp: Evaluating rule        : EditionUpgradeMatrixCheck
(10) 2016-08-18 07:24:23 Slp: Rule running on machine: RAL-SQL2012TST
(10) 2016-08-18 07:24:23 Slp: Rule evaluation done   : Succeeded
(10) 2016-08-18 07:24:23 Slp: Rule evaluation message: The selected SQL Server instance meets upgrade matrix requirements.
(10) 2016-08-18 07:24:23 Slp: Send result to channel : RulesEngineNotificationChannel
(10) 2016-08-18 07:24:23 Slp: Initializing rule      : SQL Server 2014 edition downgrade
(10) 2016-08-18 07:24:23 Slp: Rule is will be executed  : True
(10) 2016-08-18 07:24:23 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionDownGradeCheck' looking for installed version data for feature package 'sql_as_Cpu64'.
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionDownGradeCheck' looking for installed version data for feature package 'sql_engine_core_inst_Cpu64'.
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionDownGradeCheck' looking for installed version data for feature package 'sql_rs_Cpu64'.
(10) 2016-08-18 07:24:23 Slp: -- SkuUpgradeRule : Rule 'EditionDownGradeCheck' detection result: IsValidEditionUpgrade=True IsEditionDownGradeFalse
(10) 2016-08-18 07:24:23 Slp: Evaluating rule        : EditionDownGradeCheck
(10) 2016-08-18 07:24:23 Slp: Rule running on machine: RAL-SQL2012TST
(10) 2016-08-18 07:24:23 Slp: Rule evaluation done   : Succeeded
(10) 2016-08-18 07:24:23 Slp: Rule evaluation message: The selected edition downgrade path is valid.
(10) 2016-08-18 07:24:23 Slp: Send result to channel : RulesEngineNotificationChannel
(10) 2016-08-18 07:24:23 Slp: Initializing rule      : Upgrade architecture mismatch
(10) 2016-08-18 07:24:23 Slp: Rule is will be executed  : True
(10) 2016-08-18 07:24:23 Slp: The document specified by its root path '/Extensions/Msi/PackageInstallMap' does not exist in data store.
(10) 2016-08-18 07:24:23 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.ObjectDatastoreIntegration.ReadPropertyFromDatastore(String propName, Type propertyType, String rootPath, String xPath)
   at Microsoft.SqlServer.Configuration.SetupExtension.ObjectDatastoreIntegration.SetDatastoreInputPropertiesOnObject(Object pendingObject, TextWriter loggingStream)
   at Microsoft.SqlServer.Configuration.SetupExtension.RuleDatastoreIntegration.SetPropertiesOnTestingRuleHandler(Object notification, Object[] objectArray)
   at Microsoft.SqlServer.Chainer.Infrastructure.NotificationHandler.Invoke(Object notification, Object[] objectArray)
   at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.Execute(Boolean stopOnFailure)
(10) 2016-08-18 07:24:23 Slp: Rule initialization failed - hence the rule result is assigned as Failed

I am trying to install SQL Server 2008 and i encounter an error 'The following error has occurred: Attempted to perform an unauthorized operation. Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup'

the Log file looks like this;

Overall summary:
  Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
  Exit code (Decimal):           -2068709375
  Exit facility code:            1202
  Exit error code:               1
  Exit message:                   A failure was detected for a previous installation, patch, or repair during configuration for features [SQL_Browser_Redist,]. In order to apply this patch package (KB968369), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.
  Start time:                    2016-08-19 08:33:04
  End time:                      2016-08-19 08:34:17
  Requested action:              Patch
  Log with failure:              C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20160819_083248\Detail.txt
  Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.2531.0%26EvtType%3d0x7281D40D%400xC2B0B50B%401202%401

Machine Properties:
  Machine name:                  SSSEBAGGALA-PC
  Machine processor count:       4
  OS version:                    Windows Vista
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          32 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered 
  Sql Server 2008                                                          Management Tools - Basic                1033                 Standard Edition     10.0.1600.22    No        
  Sql Server 2008                                                          Management Tools - Complete             1033                 Standard Edition     10.0.1600.22    No        
  Sql Server 2008                                                          Client Tools Connectivity               1033                 Standard Edition     10.0.1600.22    No        
  Sql Server 2008                                                          Client Tools Backwards Compatibility    1033                 Standard Edition     10.0.1600.22    No        
  Sql Server 2008                                                          Client Tools SDK                        1033                 Standard Edition     10.0.1600.22    No        
  Sql Server 2008                                                          Integration Services                    1033                 Standard Edition     10.0.1600.22    No        

Package properties:
  Description:                   SQL Server Database Services 2008
  SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
  ProductName:                   SQL2008
  Type:                          RTM
  Version:                       10
  SPLevel:                       1
  KBArticle:                     KB968369
  KBArticleHyperlink:            http://support.microsoft.com/?kbid=968369
  PatchType:                     SP
  AssociateHotfixBuild:          0
  Platform:                      x86
  PatchLevel:                    10.1.2531.0
  ProductVersion:                10.0.1600.22
  GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
  PackageName:                   SQLServer2008-KB968369-x86.exe
  Installation location:         d:\083c7b43e2e2ee7cc8\x86\setup\

User Input Settings:
  ACTION:                        Patch
  ALLINSTANCES:                  False
  CLUSTERPASSIVE:                False
  CONFIGURATIONFILE:             
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTANCENAME:                  <empty>
  QUIET:                         False
  QUIETSIMPLE:                   False
  X86:                           False

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               The rule result report file is not available.

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException
    Message: 

        A failure was detected for a previous installation, patch, or repair during configuration for features [SQL_Browser_Redist,]. In order to apply this patch package (KB968369), you must resolve any issues with the previous operation that failed. View the summary.txt log to determine why the previous operation failed.
    Data: 
      ChainerInvalidOperationExceptionData = ProductInstallProperty
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.CheckFailedConfiguration()
        at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.CollectProductData()
        at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinitionAllInstances()
        at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinition()
        at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase..ctor(ServiceContainer context)
        at Microsoft.SqlServer.Configuration.PatchFeatureTree..ctor(ServiceContainer context)
        at Microsoft.SqlServer.Configuration.PatchFeatureTree.InitializePatchFeatureTree(ServiceContainer context)
        at Microsoft.SqlServer.Configuration.SetupExtension.InitializeUIDataAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

Hi,

I have SQL 2016 on same box as my TFS 2015. Recently I run out of space on one of the drives. I found out, that SQL 2016 is creating mdmp files. Is there any fix? How can I solve it?

Petr

Hi,

Do u know if version of SQL Server (Standard or Enterprise) flow for possibility of use EBS (external blob storage) ?

Thx

Michal

Hi All,

I am trying to upgrade SQL Server 2012 evaluation edition to SQL Server 2014 Evaluation edition.

On Installation wizard when I click on upgrade option, it is not displaying the option for selecting instance.
Where as only shared components are upgrading to 2014.

I have downloaded new setup files from MS and tried also but no use.

Even I tried using SQL Server 2014 developer edition. but no use.

Previously I was able to upgrade from SQL Server 2012 evaluation edition to SQL Server 2014 Evaluation edition. But it is not working this time.

Please find the screenshot below.

In the below screenshot it should have select instance option, but its not there in the file.

Please help me here.

Thanks and Regards!!

Raghavender Chavva

Thank You. Regards, Raghavender Chavva

I am have a problem with my SQL Server 2014 installs on my machine.  I first did a default instance and a few months later did a named instance Test_Dev.

I have been having some issues so I happened to be looking in the properties box of the default instance and saw the name of the Named Instance at the top.

So I ran the following queries on both instances and got the same results  Machine\Test_Dev or just Test_Dev:

This would seems to be a problem, but I don't know how to fix it, if I can, or if I should.

Any assistance appreciated.

Nancy

nlytle It's all in a dream in the blink of an eye on the whim of a wish of a cloud

Update KB3072779 Fails with Code 851A0042

When I go into the logs to try to find the issue, this seems to be the first thing that goes wrong:

InitializeMsiExtension; No matched disk size is detected for 'all_vista_runtime'+'all_vsta_designtime'+'directory SystemDrive'+all_VSHelpLP_Cpu64'

Any help would be appreciated.  I don't have much experience with SQL.MJ