Tuesday, November 26, 2013

Upgrade Error - Valid Database compatibility level and successful connection rule

Recently when I was trying to upgrade an SQL Server 2008 R2 instance to SQL Server 2012, I was presented with an error during the upgrade rules validation.
The error message was, "The report server database is not a supported compatibility level or a connection cannot be established."



When I checked the reporting server databases, the databases had the right compatibility level.
Then I found that the SQL Server Name defined in the Reporting services configuration manager was not existing. This caused the validation rule to fail.
After changing the SQL Server Name to right server name, all the validations passed and it let me upgrade the SQL Server Instance. 

16 comments:

  1. thank you for the solution, i have same problem and now all passed fixed ready to upgrade from SS2008R2 SS2012, may God blessing you all.

    ReplyDelete
  2. thank you, i have had the same problem and I resolved it, but know I have No customs security extensions failed

    ReplyDelete
  3. Thanks - I had the same problem...

    ReplyDelete
  4. Thanks, I had this exact error upgrading one of our server to SQL2014. You saved me a lot of time and effort. Much appreciated.

    ReplyDelete
  5. saved my a$$ thanks so much!!

    ReplyDelete
  6. Mil Gracias, me ayudó muchísimo... resulta que cuando instalé el servidor la pc se llamaba SERVIDOR, luego se cambio a SERVER, al momento de instalar esos nombres se guardan y habido que cambiarlos manualmente como tu dices. gracias

    ReplyDelete
  7. Thanks mate, you saved hours for me ;)

    ReplyDelete
  8. May the eternal blessing of the Tao surround and support you, and your family find favour with all the beauty the universe can provide, your guide is excellent and most effective.

    ReplyDelete
  9. Thank you. First hit in the Google search. I would never have figured that out on my own.

    ReplyDelete
  10. Wow, thanks for taking the time to post this solution. Mine didn't seem to be wrong, but just walking through the database connection wizard eliminated the problem.

    ReplyDelete