As a SQL Server user, it is important to stay up-to-date with the latest releases and upgrades. However, sometimes the upgrade process can be challenging, and you may encounter errors that prevent you from proceeding. In this article, we will discuss a common error that can occur during an in-place upgrade and provide a solution to resolve it.
Error: Valid DSN
During the upgrade process, you may come across an error message stating “Rule ‘Valid DSN’ failed. The report server configuration is not complete or is invalid. Use Reporting Services Configuration Manager to verify the report server configuration.” This error indicates that the report server configuration is incomplete or invalid.
To resolve this error, follow these steps:
- Open Reporting Services Configuration Manager.
- Go to the Database tab.
- Check if the “Current Report Server database” field is empty. If it is empty, this is the cause of the error.
- Click on “Change database” to open the wizard.
- Follow the wizard and provide the necessary details. You can use the default settings if desired.
- Once the steps are complete, go back to the screen that was giving the error and choose “Re Run”.
- You should now be able to proceed with the setup without encountering the “Valid DSN” error.
Error: Valid Database Compatibility Level and Successful Connection
Another error that you may encounter during the upgrade process is “Rule ‘Valid Database compatibility level and successful connection’ failed. 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 level.”
To resolve this error, follow the same steps mentioned above to open Reporting Services Configuration Manager and go to the Database tab. Ensure that the report server database is set to a supported compatibility level and that a successful connection can be established.
By following these troubleshooting steps, you should be able to overcome these common upgrade blockers and successfully upgrade your SQL Server to the desired version.
Have you ever encountered similar upgrade blockers? Share your experiences in the comments below!