Noticed that the first time I try to access an MSACCESS database configured as linked server in SQL server via dbForge Studio it causes the SQL Server service to crash (Service stops).
The error message I get:
"The connection 'ANDRE-PC' was closed due to the error 'A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)'."
And I find SQL Server service stopped and must restart it.
The linked server connection to MSAccess databases are configured as "MICROSOFT.ACE.OLEDB.16.0"
The work around I found: Only after accessing any of the Access database tables via MSSSMS first, it works back in dbforge studio for as long as dbforge studio is open. The problem/bug usually occurs after dbForge Studio was shut down for some time.
I am using those links to transfer Access databases to SQL server in a structured way.