Have Geek Brain

To force SQL Server to give, does not exist or is denied access

I have a SQL Server 2005 DB that is accessed by an MSACCESS database using link tables.

Sometimes we end up with a SQL server that doesn't support or access the crash messages when it works fine in most other cases. From clients, of course.

What are the possible reasons for this?

Malcolm

EDIT: This is actually an ODBC post.

0


a source to share


2 answers


We've seen intermittent errors caused by distance and firewalls, epsecially for non-standard instances. By distance, I mean clients in New York and we are in Switzerland. Less questions in London, zero in Switzerland.



We switched to "server.domain.tld \ instancename, port" and all problems went away. This avoids the extra hop back (to port 1434) to find the instance port

0


a source


Assuming the server exists and access is granted, this is usually due to network problems or the server load is too high to respond.



0


a source






More articles:


All Articles