Source Control can't access database

RobMuir

SQL Source Control Version 7.2.4.11418

SSMS 18.6

I just updated to this version and I now get the following error on a DB that has been working for years.

SQL Source Control can’t access this database – Make sure the database is online and you have permissions to access it.

Sergio R

We've now received logs from a user that was experiencing this issue and it looks like this might have resulted from an update to the Microsoft.Data.SqlClient library that occurred in version 7.2.0:
https://documentation.red-gate.com/soc/release-notes-and-other-versions/sql-source-control-7-2-release-notes
If that's the case, this is not a bug: SQL Source Control is now stricter in enforcing Certificate validation, and to resolve this you can either fix the underlying Certificate validation issue or work around it by setting "Trust server certificate" in the Options on the "Connect to server" box in SSMS:

PeterVerschoor

Getting the same error after updating.  the error report mentions that a connection with the server was established, but that logon failed due to the target principal name is incorrect.

HeidiB

I am getting the same error after updating to the same version. And it happens with every database, whether previously linked or not.

Sergio R

I am sorry that you are having issues after upgrading to SQL Source Control 7.2.4
Do you still have issues if you uninstall and reinstall 7.1.29?
Download link for 7.1.29 installer:
https://download.red-gate.com/checkforupdates/SQLSourceControl/SQLSourceControl_7.1.29.11028.exe

DarrylDsouza

This error still exists even with the Trust Server certificate flag ticked, as suggested above.

edwards142

When I was stuck with such a situation in my Access database application I was completely unaware about the reason that makes that happen. After searching a lot about this specific issue I come to know that my database is got corrupted. At that time I urgently need to repair it because my complete database data is at risk. 

I want to fix it manually without the help of any third-party repair tool so started searching for the fixes. At that time I got this informative post on: Access database repair