Hi!
I'd like to upgrade my SSRS 2012 and 2016 instances to SSRS 2017. Upgrading from 2012 to 2016 was fine. However, when I run the stand-alone installer for SSRS 2017 I get no option to upgrade but only install and configure later. I've searched the documentation which is a mix of 2016 and 2017 references but have failed to find an answer.
Can I upgrade from SSRS 2016 to 2017 and if so, how?
The OS is W2K12 and the SSRS instance is named.
Thanks/U
Hello,
After recent updates for Windows 7 x64 we have encountered a problem with SQL Server Management Studio 2012. While trying to make a new query, the following error appears:
https://imgur.com/ecDwhWA
We have tried to reset fonts in Windows and reinstall Management Studio. Restoring system had helped for a while, but after a few days the problem reappeared when updates were installed again. If you know the solution, please help.
Best regards,
Emil
We are wanting to upgrade sql 2012 to sql 2014/2016.
our sql 2012 is in a two node cluster. Next we fail the database (instance) to node 2 then upgrade node 1. next upgrade node then fail the database (instance) back to node 1. How does the database get upgraded from 2012 to 2014 in the upgrade step below? Do we need to keep the database (instance) on the node being upgraded ( instance upgraded simultaneously upgraded on node 1 while the node 2 is upgraded?
Do you have any major preference in a in place upgrade of SQL or should we move the database to a fresh install (sql 2014 or sql 2016)?
Does it make a difference if we upgrade to 2014 or 2016?
dsk
I have been receiving this error for too long and too often. I have done everything that has been suggested in blogs, in documentation, and in every imagining.
HELP!
This is not a new problem. The majority of corrective advice are for previous versions of SSMS and few if any for version 17.
If the installation routine knows a component is missing, can't the routine notify the user and offer to fix the issue?
Resolving this is vital now to my small business and it's success as a startup.
Thank you for your assistance and advice.
Kevin
OG IT Systems
I wish I could share photos and a direct link to the code but my account won't even offer to verify me for some reason. Please remove spaces and replace the word dot with periods and slash with / to get the real addresses to the info I am sharing.
Hi Folks! I seem to be having difficulty installing SQL server 2008 on a laptop. Would any of you have any insights into how to get the install working?
Also, thank you for being here for everybody. I appreciate your help you guys provide to the community.
http:// postimg DOTccSLASH imageSLASH yz5qefcx7
The setup fails (as per the picture above) to install the 3 main components, Database Engine Services, SQL Server Replication and Management Tools. I need to get these working to be able to get some health related people who I represent on the road :)
Here is my details.txt error log from the install:
http:// pasted DOTcoSLASH bf757c69
Thank you again for your help on this matter. It makes a world of difference.
Hi ,
I am trying to install SQL Server 2014 evaluation version on my system
(Windows 7) , all configuration & compatibility test passed but not able to install.
getting below error at the end step.
SQL Server 2014\1033_ENU_LP\x64\setup\sql2008support.msi does not exist
Please help how to fix this error and complete the installation.
I'm getting the above error when trying to install a new instance of SQL Server 2017 developer edition. I've read that this can be caused by the installation trying to install an earlier version of the c++ distributable when visual studio 2017 is installed. So I've tried uninstalling visual studio, repairing then uninstalling the visual C++ redistributable (both) and running the installation under the windows administrator account, but not getting any luck. Are there any other ideas on what might work?
Hi,
My Solution explorer is blank, I open a new solution or Project and all looks like its opened ok, but nothing in the explorer?
When I open the solution in SSMS 2008 it all works fine.
Help?
Hi all.
I have an instance of SQL server that I have tried to inplace upgrade but failed.
Current version SQL server 2014 Ent.
Target version SQL server 2017 Ent.
The upgrade failed with lack of permission to update the permission of the backup destination.
<-------------------- OUTPUT FROM THE SETUP LOG ------------------------------->
Feature: Database Engine Services
Status: Failed
Reason for failure: An error occurred during the setup process of the feature.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using
this command line: setup /q /action=uninstall /instanceid=<INSTANCE_NAME_REMOVED> /features=FULLTEXT,SQLENGINE,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84CF0003
Error description: Updating permission setting for folder '\\SQLBackup-DCD02P.oneadr.net\SQLBackup\Backup' failed. The folder permission setting were supposed to be set to 'D:(A;OICI;FA;;;S-1-5-21-2077435073-541759679-708572619-1383108)'.
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=0x88792597%400xBB814387&EvtType=0x88792597%400xBB814387
<-------------------- OUTPUT FROM THE SETUP LOG ------------------------------->
The log tell us to fix the issue by uninstalling the SQL server instance. I would prefer an alternative if possible :)
I changed the backup destination to local folder and ran the upgrade wizzard again. Now it claims that it does not have anything to upgrade even though the SQL server instance has not been upgraded.
The server was rebooted before the second try.
Any good ideas of what to do ?
Hi Team,
while connecting sql server 2012 from SSMS 2008, please help me with this on urgent basis.
error as follows "A connection was sucessfully established with server, but then an error occurred during the login process, (provider: SSL Provide : 0 -An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error : 10054)
An existing connection was forcibly closed by the remote host..........."
Regards,
v
SQL Server 2016 Std Edition upgrade to SQL Server 2017 Std Edition.
Upgrade fails, see below excerpt from errorlog
2017-10-16 13:27:00.47 spid4s Database 'master' is upgrading script 'ISServer_upgrade.sql' from level 0 to level 500.
2017-10-16 13:27:00.47 spid4s ---------------------------------------------
2017-10-16 13:27:00.47 spid4s Starting execution of ISServer_upgrade.SQL
2017-10-16 13:27:00.47 spid4s ---------------------------------------------
2017-10-16 13:27:00.47 spid4s
2017-10-16 13:27:00.47 spid4s Taking SSISDB to single user mode
2017-10-16 13:27:00.47 spid4s Setting database option SINGLE_USER to ON for database 'SSISDB'.
2017-10-16 13:27:05.53 spid4s Error: 1712, Severity: 16, State: 1.
2017-10-16 13:27:05.53 spid4s Online index operations can only be performed in Enterprise edition of SQL Server.
2017-10-16 13:27:05.53 spid4s Error: 917, Severity: 15, State: 1.
2017-10-16 13:27:05.53 spid4s An upgrade script batch failed to execute for database 'master' due to compilation error. Check the previous error message for the line which caused compilation to fail.
2017-10-16 13:27:05.53 spid4s Error: 912, Severity: 21, State: 2.
2017-10-16 13:27:05.53 spid4s Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 917, state 1, severity 15. 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.
2017-10-16 13:27:05.53 spid4s Error: 3417, Severity: 21, State: 3.
2017-10-16 13:27:05.53 spid4s 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.
2017-10-16 13:27:05.53 spid4s SQL Server shutdown has been initiated
Thoughts and advice welcome.
Hi there
Ok, migrating all databases over time from 2014 to 2016.
Previous upgrades just used detach/attach, all worked ok.
On both servers the dbs and logs are stored on different drives.
I detach from 2014...all fine. Copy mdf and ldf files to correct default locations.
On SQL 2016 SSMS, when I attach and add the mdf file, it does not populate the ldf in the lower window, the mdf does appear ok. The default settings are correct. Indeed if I ok the process, it comes back with an error basically saying it can't create the ldf file because it exists, which indeed it does.
However, if I put both the mdf and ldf files in same location, the attach process works fine even though not the default location.
If I use TSQL, it does work ok. However, I'm used to using the GUI and in the past this has been the easiest option.
Any ideas how to get this working properly, have I missed something obvious?
Regards
Ian
Installed all patches below:
SQL 2012 Service Pack 1 SQL 2012 Service Pack 2 SQL 2012 Service Pack 3 SQL 2012 Service Pack 3 - Hotfix for TLS1.2 Still the SQL SERVER 2012 cannot start as per error below.
A fatal error occurred while creating an SSL client credential. The internal error state is 10013. The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system. TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation. TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation. 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. SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
SQLLog
2018-07-12 11:16:25.10 spid10s The server could not load the certificate it needs to initiate an SSL connection. It returned the following error: 0x80090331. Check certificates to make sure they are valid. 2018-07-12 11:16:25.11 spid10s Error: 26014, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s Unable to load user-specified certificate [Cert Hash(sha1) "1E40ACCA7AB499E2967FE691A9FBCCAA39A122CC"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online. 2018-07-12 11:16:25.11 spid10s Error: 17182, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 2018-07-12 11:16:25.11 spid10s Error: 17182, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 2018-07-12 11:16:25.11 spid10s Error: 17826, Severity: 18, State: 3. 2018-07-12 11:16:25.11 spid10s 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-12 11:16:25.11 spid10s Error: 17120, Severity: 16, State: 1. 2018-07-12 11:16:25.11 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. Is there really a solution for this?
The SSL certificate is not the issue because when i enabled the TLS1.0. The server can start again.Hi all,
I have MS SQL 2014 SP2 Evaluation edition. Now i want to license it to continue working.
I start the Edition Upgrade option and all goes well until the rule check comes. In my case all rules pass except "AlwaysOn Availability Groups feature check".
On this check it seems stuck - for more than 1 hour it has not passed.
Hey there,
Maybe someone had a similar situation and could help me out a little bit.
We are currently planning a migration of all our SQL Instances from a non-clustered Microsoft SQL Server (Single VM, no Failover functionality) to a new Microsoft SQL Failover Cluster environment (2 Nodes, new SQL Failover Cluster Instance for every SQL Instance).
Currently all our database connections are in the following scheme:
SQLServer1/Instance1
SQLServer1/Instance2
SQLServer1/Instance3
Since all the new SQL Failover Cluster Instances require a new DNS/Network name for every single Instance, we will face some trouble (and alot of work) to change the database configuration on every single host. Is there an easier solution than changing every single config file to point to the new database url(s)? Is there a way to use the same old SQL Server DNS Name (SQLServer1) for multiple failover cluster instances?
DNS Aliases? CNames? Anything?
Best Regards
I would like to use sql server agent and it's jobs. I had express edition which I upgraded to developper edition. Then in the sql server installation server I try to add features to an existing installation and I don't know which "bundle" of features i want to add.
I tried searching what I need to install to get sql server agent several times but none of the search results were relevant.
Hello,
Our production SQL server is version 2016.
My dev box is SQL server 2017 dev.
I built a large DB (with compatibility set to SQL 2016) on my dev box and trying to move the DB to the production.
But I failed:
#1. backup/restore. Production server won't take a backup from SQL 2017 (even I set the DB compatible to SQL 2016)
#2. detach from dev and attach on prod. Still don't let me do it.
#3. Create a new DB on Production/SQL2016. Backup and restore on Dev. Populate the DB.
then Backup and restore on Production. Still not let me complaining it was backed up in SQL2017.
Need help on this task.
Thanks in advance.
John
I ran into the problem below while I was trying connect, the following is the error message. Can anybody help solve this problem please?
OK
------------------------------
Platform used is Windows Server 2016 with MSSQL 2016
Are there any settings to be done explicitly to get the support for GB18030? How to confirm that Chinese char set ( with UTF-8 ) is supported and readable by SQL server 2016 database?
With MSSQL DB Collation set to Chinese_Hong_Kong_Stroke_90_CI_AS, its failing as below:
"Could not find a Java charset equivalent to collation 040CD01000." How to resolve this error?
Hi
I have just started working with SQL Server 2012 in my career and would like to install SQL Server Developer on my Home Server (WHS 2011), however it is saying that:
The operating system on this computer or its service pack level does not meet the minimum requirements for the SQL Server 2017.....
Is there a work around for this or another version I can use.