Besides the causes mentioned in the actual error message (the database being offline or the user used to connect in SSMS not having permissions) this can also be caused by Certificate Validation issues.
If you have started getting this error after upgrading from a version prior than 7.2.0, please note that we've updated the Microsoft.Data.SqlClient library. For security reasons, this library now sets the TrustServerCertificate parameter to a default value of false in more scenarios.
You can either resolve the certificate validation issues on your system or work around this by explicitly setting the "Trust Server Certificate" property to true (available in the SSMS connection dialog options screen).
42
-26
Was this article helpful?
8 out of 42 found this helpful
Articles in this section
- The process cannot access the file 'C:\Users\*******\AppData\Local\Red Gate\SQL Source Control 7\Caches
- Duplicate definition troubleshooting in SQL Source Control
- The target principal name is incorrect
- SQL Source Control can't access this database - make sure the database is online and you have permission to access it
- Meanings of the colored dots in the SSMS Object Explorer for SQL Source Control
- Last Changed By column shows Unknown
- How to Link SQL Source Control to TFS
- How to link to an existing SVN repository
- GIT Push/Pull greyed out
- Objects changed by unknown