Report Server database version not accepted in SQL upgrade

I am upgrading SQL 2008 R2 to SQL 2016 Developer
Ran update advisor and took advice to install SQL 2008 service Pack 4, done successfully
However the feature rule step fails with Valid Database compatibility level and unsuccessful connection
The extended error message advises that:
The report server database is not a supported compatibility level or a connection cannot be established. Use Reporting Services Configuration Manager to verify the report server configuration and SQL Server management tools to verify the compatibility levels.
I knew nothing about the Reporting Service, but since then I have:
  • Checked Services that the SQL Server Reporting Services is started
  • Changed the security on SQL Server Reporting Services to Local system~Windows authentication
  • Stopped and started service
  • Run Reporting Service Config Manager as administrator.  It required a connection on opening.  Fails to Find connection to DESKTOP-PHACT and does not allow me to use other options.
  • Opened SSMS and opened report server.  Even run a Crystal type report (see attachment)  

Any suggestions?
SSMS_reportServer.jpg
Nigel Keith-WalkerContractorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Nigel Keith-WalkerContractorAuthor Commented:
Upgrade is now complete.

I was experiencing connection problems with the Reporting Services Configuration Manager.  I checked on the SQL server configuration manager on the details for the SQL Server Reporting Services, it looked OK on the Service tab so I hit Apply.  This allowed me to access the RSCM.  The database looked fine,  but then I went through the options for choosing an existing report server, I then pointed it to the report server, and then everything worked.

Hope this may help someone in the future
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Nigel Keith-WalkerContractorAuthor Commented:
Maybe I was not so successful.  Attached is the SSMS after the upgrade.  There are no databases because there was an error with encrypted data in the Reporting Services.

This is not disastrous as it is a development sit and I can recreate copies of the Database from production
SQL2016_Error.jpg
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Databases

From novice to tech pro — start learning today.