SQL Server does not exist or access is denied (intermittently)

I use the Microsoft Access 2010 front end with linked tables when installing SQL Server 2012. Local Area Network. When Access starts, a VBA script is launched that connects to the SQL server and performs some checks. I recently upgraded from SQL Server 2008 to 2012, when communications between the client and server began to break intermittently.

When the connection between my client and server fails, I see a general message, "SQL Server does not exist or is not available for access." This is described in the Microsoft support article http://support.microsoft.com/kb/328306 . The potential causes described in this article are not consistent with the problem I am facing.

This connectivity issue is intermittent. The problem occurs about 3 times a week and lasts about 30 minutes at a time. Between these 30-minute crashes, the system works perfectly.

My Current VBA Connection String: (tried several times to fix the problem):

Dim conn As ADODB.Connection
Set conn = New ADODB.Connection
conn.Open "Provider=SQLOLEDB;Server=Server3.companydomain.local;Database=My_Database;Trusted_Connection=Yes"

I hope I can find something in the SQL Server logs (which I have access to), but I don’t know which log file I should examine.

+3
source share
3 answers

Well, 7 months have passed. Here is a solution to this problem (in my case): My secondary DNS server was an external server. He could not find my database (192.168.xx) because it is an internal address.

DNS- SQL Server, . DNS , DNS, . , - . .

+2

, , IP- , SQL-... , , DHCP, IP- ? , , IP- .

, IP- ( NIC-), .

+2

This is a little strange, but I found that I get this error when I do not have the appropriate code like "CLOSE DB CONNECTION" on my site. And then when too many users get to the site, I start getting this error.

Solution: Make a complex closure of DB connections after each db call. Yes, most DB connectors have cleaning procedures, but this is not enough with a heavy load.

In addition, set a limit on the maximum number of database connections in the web.config file

+1
source

All Articles