Hello All,

I have a quesiton for Data base migrate.

we MIgrage database from low version(11.0) to high version. Now we have to migate the database from the high version to low verion.

I try using Copy, it give one error (exceute SQL Server Agent Job Error) of 5. and package was not able to created.

"Backup and restore" : System give error message: data base could be restored on lower version SQL.

try to "Export  Data-Tier Application" and SQL server gives 3 errors of 7. We get operation fail as a result.

How can we transfer the data from 14.0 to 11.0? 

Please give advice.

brgds

Liu Wei

Hello,

I've been struggling to install sql server 2017 for a few days now. I keep getting message:

Oops... Unable to install SQL Server(setupe.exe). Exit code(Decimal)-2068052377 Error description:Invalid command line argument.Consult the Windows Installer SDK for detailed command line help.

 I've tried to delete all sql folders , registry keys, uninstall everything related to SQL Server, installing as admin, cleaning and fixing the registry, rebooting,... Still cant install. Please help. Thanks in advance. I attached 3 log files inhttps://mega.nz/#F!J4FUCS5Q!S9lRhfgZfDafzM4AG9Py-Q

We are provisioning a server for a customer and have purchased SQL Standard 2017 Core Edition. The customer has just asked us to install 2014 instead, as they cannot upgrade their database version yet.

I think there are downgrade rights to 2014 but will I need to purchase a downgrade kit with a license key or is it a keyless installation?

Hi all,

Relatively basic question but much harder to actually get any solid numbers on.

Currently in the process of upgrading our main servers and trying to weigh up options of current Intel and AMD offerings.

Does anyone have any experience with the new EPYC 7002 series vs 2nd gen Intel Xeon Scalable? If you want specifics, I'm looking for comparison of the Xeon Gold 5222 and EPYC 7262. Currently using Xeon E5-2637 v3 chips and whilst I expect Intel will still offer a performance advantage, AMD does offer a much more compelling platform with PCIe 4.0 and faster memory support.

Any first hand experience would be fantastic, thanks in advance.

I was using SQL Sever 2008 R2 on my notebook but I need to replace hard disk with SSD and have to install fresh copy of windows 10.
On new machine I tried to install SQL Server 2008 R2 but it stuck on almost ending process of SqlEngineDBStartConfigAction_install_configrc_Cpu64 shown in below screenshot. I also checked in Services and found that SQL Server service keeping in "starting" mode.

I tried below link trick but not able to find registery key "AppCompat" on Windows 10 machine. https://www.networkworld.com/article/2228061/tricky-sql-server-install-on-64-bit-machines---use-switchback-.html https://blogs.msdn.microsoft.com/sql_protocols/2010/08/13/windows-7-appcompat-changes-and-sql-server-client-and-setup-hangs/

Can anyone please help me as I could not upgrade to newer version of SQL Server.

Hi,

I searched a lot but did not found any solution. So, now I am here.

I´m trying to install MS SQL 2014 Failover Cluster on a WindowsServer 2012 R2. In test environment everything went fine, now in the prod environment we are running into a failure.

The installation is nearly complete up to the point "BringAgentResoucreOnlineAction". It fails with following error message:

TITLE: Microsoft SQL Server 2014 Setup
------------------------------

The following error has occurred:

The cluster resource 'SQL Server Agent' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
.

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

Error Log gives following details:

(01) 2018-03-09 16:04:07 Slp: ----------------------------------------
(01) 2018-03-09 16:04:07 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2018-03-09 16:04:07 Slp: Inner exceptions are being indented
(01) 2018-03-09 16:04:07 Slp:
(01) 2018-03-09 16:04:07 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
(01) 2018-03-09 16:04:07 Slp:     Message:
(01) 2018-03-09 16:04:07 Slp:         The cluster resource 'SQL Server Agent' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
(01) 2018-03-09 16:04:07 Slp:         .
(01) 2018-03-09 16:04:07 Slp:     HResult : 0x86d8003a
(01) 2018-03-09 16:04:07 Slp:         FacilityCode : 1752 (6d8)
(01) 2018-03-09 16:04:07 Slp:         ErrorCode : 58 (003a)
(01) 2018-03-09 16:04:07 Slp:     Data:
(01) 2018-03-09 16:04:07 Slp:       resourceName = SQL Server Agent
(01) 2018-03-09 16:04:07 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
.
(01) 2018-03-09 16:04:07 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
(01) 2018-03-09 16:04:07 Slp:       DisableRetry = true
(01) 2018-03-09 16:04:07 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
(01) 2018-03-09 16:04:07 Slp:         Message:
(01) 2018-03-09 16:04:07 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
(01) 2018-03-09 16:04:07 Slp:                 .
(01) 2018-03-09 16:04:07 Slp:         HResult : 0x86d70002
(01) 2018-03-09 16:04:07 Slp:                 FacilityCode : 1751 (6d7)
(01) 2018-03-09 16:04:07 Slp:                 ErrorCode : 2 (0002)
(01) 2018-03-09 16:04:07 Slp:         Data:
(01) 2018-03-09 16:04:07 Slp:           ExceptionMessage = Generic failure
(01) 2018-03-09 16:04:07 Slp:           StatusCode = 5023
(01) 2018-03-09 16:04:07 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.

(01) 2018-03-09 16:04:07 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
(01) 2018-03-09 16:04:07 Slp:         Stack:
(01) 2018-03-09 16:04:07 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2018-03-09 16:04:07 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
(01) 2018-03-09 16:04:07 Slp:         Inner exception type: System.Management.ManagementException
(01) 2018-03-09 16:04:07 Slp:             Message:
(01) 2018-03-09 16:04:07 Slp:                         Generic failure
(01) 2018-03-09 16:04:07 Slp:             HResult : 0x80131501
(01) 2018-03-09 16:04:07 Slp:             Data:
(01) 2018-03-09 16:04:07 Slp:               WmiErrorCode = Failed
(01) 2018-03-09 16:04:07 Slp:               WatsonData = Failed@5023
(01) 2018-03-09 16:04:07 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.

(01) 2018-03-09 16:04:07 Slp:               ErrorType = 1
(01) 2018-03-09 16:04:07 Slp:               Operation = ExecMethod
(01) 2018-03-09 16:04:07 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL Server Agent"
(01) 2018-03-09 16:04:07 Slp:               ProviderName = WinMgmt
(01) 2018-03-09 16:04:07 Slp:               StatusCode = 5023
(01) 2018-03-09 16:04:07 Slp:             Stack:
(01) 2018-03-09 16:04:07 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
(01) 2018-03-09 16:04:07 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
(01) 2018-03-09 16:04:07 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
(01) 2018-03-09 16:04:07 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2018-03-09 16:04:07 Slp: ----------------------------------------

SQL Server is up and running, the SQL Server Agent cannot be started due to the above mentioned error.

We already tried to re-create DNS entry, re-create AD object, compared the permissions between prod and test system. But we don´t see any differences.

So, now I am hoping anyone of you have an idea.

Regards,
Helen

PS: I can test again on Monday CET.

Hi,

Does anyone have any experience with running SQL Server 2016 on compatibility mode 2008 in terms of performance/ query plans and also general compatibility with 3rd party applications? It will be reassuring if not much changes on the new database.

We are planning the migration of a high volume, few terabytes of data 2008 based system to 2016. We are hoping that performance stay the same (at least).

We will eventually migrate to 2016 compatibility level but not at this stage. Any other advise you can give?

Thanks very much.

Panos.

Hi everyone,

We are a little company with 10 computer stations connected to one server and use SQL server 2008 - version 10.50.1600.1 not clustered. We want to add one more station and we have been told that we need to upgrade to SQL Standard 2017. They charge us a lot of money for that.

My questions are:

- Do we need to upgrade because of the add of one more station? and do we have to pay for 11 licences ?

- For upgrade is it logical that the price is for a new licence?

I don't understand much in all these problems so I'll be glad to get some advices from experts

Thank you in advance all

Sylvie

Hi all,

I wanted to know if there is a quick way to upgrade our  trial SQL2016 cluster to a licensed SQL 2016 cluster without rebuilding the whole server.

Our consultant forgot to mention that he needed to upgrade the trial to a licensed model. And now we are working in Production with the trial. Rebuilding the SQL cluster looks like the only solution, but we hope there is a better way.

I thought it would be possible to remove the cluster connections so you have a stand alone sql server and then upgrade the both servers and make the Clustering complete again. But is that possible with the cluster modules installed on it?

hope some one can help us quickly

Hello everyone, thanks for any help on this issue.  I have recently installed SQL 2008 R2 on a Server 2008 R2 machine cluster.  We ran the advanced cluster prep and completion.  I have SQL Server up and running properly and failing over between nodes.  In the failover cluster manager, when I select SQL Server, I do not have the SQL Server Agent listed under other resources.  When I try to start the Agent from the SQL Configuration Manager it fails with an event 103 and I've found several notes on this error but I am figuring the root issue is that there isn't a cluster resource for the Agent.

Is it possible to create the resource for the Agent? I have run a repair and I have tried to use add a resource, generic service, sql agent but it fails when I attempt to bring it online.

Thanks again for any help on this.

Mike

Installing on Domain Server (only server, small network), 2012 R2

I am a volunteer with very limited network experience

SQL Server Express 2012 is already installed

I uninstalled the last attempt at installing SQL Server Express 2017, rebooted and installed using the custom option

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

  Feature:                       Python
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                Machine Learning Services (In-Database)
  Component error code:          0x80131509
  Error description:             Cannot find group with identity S-1-5-21-464858192-4288412492-2497808848-1306.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x69EA8169%400xE9BC3D64&EvtType=0x69EA8169%400xE9BC3D64

  Feature:                       R
  Status:                        Failed
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                Machine Learning Services (In-Database)
  Component error code:          0x80131509
  Error description:             Cannot find group with identity S-1-5-21-464858192-4288412492-2497808848-1306.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x69EA8169%400xE9BC3D64&EvtType=0x69EA8169%400xE9BC3D64

  Feature:                       Machine Learning Services (In-Database)
  Status:                        Failed
  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:                Machine Learning Services (In-Database)
  Component error code:          0x80131509
  Error description:             Cannot find group with identity S-1-5-21-464858192-4288412492-2497808848-1306.
  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x69EA8169%400xE9BC3D64&EvtType=0x69EA8169%400xE9BC3D64

  Feature:                       Database Engine Services
  Status:                        Failed
  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:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

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

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Client Tools SDK
  Status:                        Passed

  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

hi,

i am trying to uninstall sql server 2012 64b and get an error like this:

"this sql server setup media does not support the language of the OS,or does not have the sql server English-language version installation files. use the matching language specific sql server media, or install both the language specific MUI and change the format and system locales through the regional setting in the control panel"

how to resolve this error and successfully remove sql server 2012 64b??

Hi

Our current SQL server setup runs with 3 X Windows 2016 servers in failover cluster with 2 X SQL instances. All applications refer the SQL by "Instace\SQLSrvrName". Our management asks to migrate all these clustered instances to SQL high availability model because of various including limitation with backup to take clustered hosts. We never configured SQL high availability, looking for an option to migrate the clustered / multiple instance SQL to high availability with minimum downtime. Also it's hard to change the SQL server reference in all apps, so if possible we have to keep the same format even after migrating to SQL HA model.

Thanks in advance

LMS

Hi,

Anyone can help me with this...

My company want to upgrade to SQL 2017, but don't want to upgrade the so (Windows Server 2008 r2) to reduce costs

For what I read, its not possíble.

Best regards

Joel

Thank you in Advance.

Hi,

I have a SQL server standard edition 2014 which was installed years back, i am going to uninstall and install it again due to some reason, i wanted to make sure while i will install it whether i need to have license key which i do not have since i recently joined to this organization, i asked windows team to provide license keys and they replied its a core based product and it does not require license key to install, earlier they said its a server + CAL license but now saying its core based.

my query is, if it is core based license and taken for without software assurance, and if i install it again by dowloading sql sererv 2014 installation setup will it require license key?

another question is how can i make sure what kind of license is it? 

SQL Server DBA

Not sure if I chose the right category and forum but here is my issue.

Security Update for SQL Server 2017 RTM GDR (KB4505224) - Error 0x80070643

The above is my main issue

I have troubleshooted this for two hours running windows update troubleshooter which said it fixed 3 issues and then I tried the update again and it still failed.

I tried to download the update from the microsoft windows update catalog via internet.

I tried to download a FixMissing MSI .zip file from git hub.

The below error is what I get when I ran the install application file for the KB 4505224

I have saved the error message but this site won't let me add the picture because of Body text cannot contain images or links until we are able to verify your account.

What is the best way to work around this error or fix this issue?

I thought of deleting the software distribution or backing it up and renaming it. It did not allow me to do this.

Thank you for any information you can provide 

Hi,

I set up a new cluster the other day, after doing two others successfully. This particular cluster on windows 2012 R2 is a SQL 2014 installation that has been patched to SP2 CU10. The cluster also hosts 9 other instances and a file share we use for backups for all the instances. 

It will not come online and has the error - "Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available."

I verified that dependencies were set up like the other clustered instance on this cluster, took the IP & Network name offline and then tried to ping it - no response. I put the IP/NetName online and was able to ping it. I changed the IP to a new IP provided by my network team and also known to be available. I have read through several similar threads here that mention validating registry entries and looked at those entries. I've tried bringing it up on both nodes.  The same error has occurred after all these steps.

System Log:

The SQL Server (INST10) service terminated with the following service-specific error: 
Access is denied.

SQL Log:

2018-07-05 11:41:11.59 spid16s     Could not find any IP address that this SQL Server instance depends upon.  Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available.  Error code: 0x5.
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17182, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied. 
2018-07-05 11:41:11.59 spid16s     Error: 17826, Severity: 18, State: 3.
2018-07-05 11:41:11.59 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2018-07-05 11:41:11.59 spid16s     Error: 17120, Severity: 16, State: 1.
2018-07-05 11:41:11.59 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Thanks for your review and suggestions.

Sam

Hi,

I have a requirement to downgrade SQL server 2014SP3 to SQL Server SP2. please guide me how to accomplish this task.

Note: SQL Server installed on cluster mode (2 Nodes) and from SQL ServerSP3 media.

Regards