I am having an issue with SSMS 2017 (latest build) on a single server only.
The set up is this: -
In preparation for upgrading SQL Server from 2012 to 2017, we have restored our two servers into an isolated network. This allows us to have the servers with same names, IP addresses, and same domain just in an isolated network completely separated from the main domian. There is no internet access on this network.
The two servers are the main DB Server & its DR server. Log shipping & restoring is set up between DB & DR Servers.
I can install SSMS 2017 on the DB Server with no issues and on this server I can connect to the SQL instance on the DB server and to the DR server with no issues at all.
SSMS appears to install fine on the DR server, but when I try to run it I get the following error:
Method not found: "Void
System.Data.SqlClient.SqlConnection.set_AccessToken(System.String)".
(Microsoft.SqlServer.Management.Dac.DacWizzard)
I should note that this only seems to happen with SSMS 2017 as SSMS 2012 continues to function correctly and I can install SSMS 2016 and that also works fine.
Any help or advice is greatly appreciated,
Related
After installing SQL Server 2019 & SSRS 2019 developer editions, I am not able to use the object explorer in SSMS to connect to SSRS. (I am also unable to use a web address to open SSRS currently due to my security software.) I think the reason I can't use SSMS is due to one or more of the following:
an error in installation
problems with older version files still left on the computer
an error in using the report server configuration manager
the rsreportserver.config file not getting properly updated.
Before installing 2019 developer editions, I have installed and tried to uninstall most versions since 2012, including 2019 express & evaluation. When I tried to install 2019 evaluation software, I created a new db engine (MSSQLSERVER02) while installing SQL Server. After I installed SSRS, I used the report server configuration manager to use this new engine as the database). This tested correctly. I opened up SSMS & connected to this db engine. When I tried to go to SSRS, the only option was a previous db engine (MSSQLSERVER01). Though I put the new name in the config mgr, there still existed an rsreportserver.config file which had the old db engine (MSSQLSERVER01) and a coded database name.
When I uninstalled the eval ed., then installed the dev versions, I still had the same problem with the old db engine (MSSQLSERVER01) name appearing. When I chose the older db option, I get a lengthy error:
Cannot connect to LAPTOP-999999\MSSQLSERVER01. Unable to connect to the server at LAPTOP-999999\MSSQLSERVER01. The specified URL might not be valid or there might be a problem with the report server version or configuration. Specify a different URL, or contact your server administrator to verify that the report server runs SQL Server 2008 or later. (Microsoft.SqlServer.Management.UI.RSClient)
When I type the the new db engine (MSSQLSERVER03) over the old, I get an error: "TITLE: LAPTOP-999999\MSSQLSERVER03 cannot be found.The Reporting Services instance could not be found. (Microsoft.SqlServer.Management.UI.RSClient)
I also tried putting in the web address into the server name (suggested by DeanOC in a similar question).
Any direction on what to do next would be greatly appreciated!
thanks,
Ginger Burton
c
I have downloaded, installed, & tried to configure evaluation copies of 2019 SQL Server & 2017 SSRS.
When I used Report Server Configuration Manager, I put my new instance of the SQL database engine (MSSQLSERVER05) into the database name.
This connected properly.
Through multiple tries, I have created multiple report servers & temp report servers.
However, when I try to access SSRS from the Object Explorer of SSMS 18.5, 2 old DB names & "SSRS" are the only instances I see.
I have tried using SSRS, but the error says the reporting service instance cannot be found.
If I type in the name of the new database engine (MSSQLSERVER05), I get the same error.
I have had earlier trials of SQL, but tried to uninstall all of them.
I notice that the file rsreportserver.config has "SSRS" in it as well as a coded database name.
This likely needs to change somehow. I would appreciate any help!
Thanks!
Ginger
First, use Developer Edition instead of Evaluation Edition for non-production scenarios, as it's not timebombed.
when I try to access SSRS from the Object Explorer of SSMS 18.5,
There's not really much use in using SSMS to connect to the Report Server. Just open the Report Manager Portal in your browser.
old DB names & "SSRS" are the only instances I see
Not sure, but SSRS 2017 is not installed as part of a SQL Server instance, and you can't have multiple instances installed on a computer. This change was part of the transition of SSRS be a scaled-down edition of Power BI Report Server.
I had an SQL Server 2012 database instance installed on server A.
I then installed SSRS 2016 only (not the the complete SQL Server 2016) on server B but pointed the SSRS instance to host its ReportServer database on the SQL Server 2012 instance installed on server A.
At this point all worked well.
I then had a requirement to upgrade SSRS 2016 to SSRS 2017.
I used the Microsoft SQL Server 2017 Reporting Services stand alone installer from https://www.microsoft.com/en-us/download/details.aspx?id=55252
In SSRS 2017 configuration manager, i selected to use an existing database and pointed to ReportServer database i have in the SQL Server 2012 instance i have on Server A.
In SSRS 2017 configuration manager, i have deleted all encrypted data.
I can browse to the reports web portal url, see data sources and the deployed test report files but when i try to open a report, i get the error blow.
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '2017'. The expected version is '173'. (rsInvalidReportServerDatabase)
i have tried to run delete from ReportServer.dbo.ServerUpgradeHistory where ServerVersion = 173 but i still get the same error.
Looks like the old version value is still being stored somehwere in a config file.
Where else should i look, what else should i try?
I resolved the issue by
1- Taking backup of ReportServer databases, then deleting them
2- stopping all report services' windows services. Made them Manual startup.
3- Opened the Reporting Services Configuration form Start Menu > SQL Server {Version}
4- Starting the service from the Configuration application
5- Recreating database from Database tab
Solution is to upgrade SQL Server 2016 to Service Pack 2: SQLServer2016SP2-KB4052908-x64-ENU
https://www.microsoft.com/en-us/download/details.aspx?id=56836
The least intrusive solution I found was this:
USE [ReportServer]
DELETE FROM ServerUpgradeHistory WHERE ServerVersion > 173
Thanks to #Henrik H in the following post:
https://serverfault.com/a/893739
I have an AWS instance, on which SQL Server 2014 has been running for more than 3 years.
But a few days ago, suddenly the SQL Server stopped running.
I checked the server and tried to start SQL Server service from services, from SQL Server Configuration Manager etc. but I'm not able to start the server and got following error:
So I checked event viewer entries and I found these two errors:
I started some research work over web to overcome on this issue and I found that I can start SQL service using below command using T902:
net start MSSQL$REVCORD /T902
And SQL Server service started successfully.
But I want to make SQL Server / services back to normal as before so I can start / stop services normally.
I found on web that this cause is due to corruption in master SQL Server database, I don't have backup of master SQL Server database so I cannot restore it back.
I checked multiple threads over web and tried multiple things to overcome this issue but no luck.
So finally I decided to reinstall/recover SQL Server 2014, but I am getting another error while reinstalling:
Based on finding over web, all threads showing that I have to uninstall and reinstall SQL Server to make it normal again.
Please help! It's a live server with multiple calls continously so I cannot uninstall/reinstall SQL Server there due to possible data loss.
The first thing:
select * from sys.sysmessages where error = 5833
The message:
The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
Check your edition, and fix the affinity mask so that the number of CPUs satisfy the number which is supported by your edition.
You can fix it in SSMS on the Processors tab in your server properties, or using sp_configure
I've inherited the job of maintaining an application which uses a local SQL Server 2008 R2 SP2 Express database as a back-end. I successfully installed the application some months back after upgrading to Windows 10 so that I could start testing and development, but after reformatting recently, I've been unable to get the database running. I'm using the exact same installer, and so far as I can tell, everything else configuration-wise is the same, with the exception that I'm now on a newer W10 insider build.
The application installer installs SQL Server 2008 R2 with the following parameters:
/TCPENABLED=1 /ACTION="INSTALL" /SQLSVCSTARTUPTYPE="automatic"
/SECURITYMODE="SQL" /SAPWD="password" /INSTANCENAME="app"
/FEATURES=SQLENGINE,REPLICATION /BROWSERSVCSTARTUPTYPE="Automatic"
/SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /IACCEPTSQLSERVERLICENSETERMS
/INDICATEPROGRESS /QS
The installer is built using Advanced Installer, and is configured to run a database setup script after installation has completed, but when it reaches this step the database times out and the install fails. To test the database I tried using a UDL file, and though the database itself is visible, when I attempt to test the connection I get
"Test connection failed because of an error in initializing provider.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied."
I've tried absolutely everything I can think of to fix this problem. I've removed all traces of every version of SQL Server from my computer, purged the registry of any remaining keys, and deleted any remaining directories. I've checked and restarted all SQL services, tried different SQL service accounts, different versions of the SQL installer, ran the installer(s) as an administrator, ran them in compatibility mode, and checked log files. I haven't found anything helpful on StackOverflow or on Advanced Installer's forums. Nothing's worked, and I'm completely out of ideas at this point.
According the MS only SQL server 2012 SP2 and up are compatible with Windows 10.
You might try this instruction to install SQL express 2008 R2, but I never tried it: https://www.youtube.com/watch?v=DUCbvfFEO34