Friday, February 17, 2012

Connecting via ODBC

Hi all,
Hope you can help, I am trying to link to some data tables into Access via
the ODBC connection. It worked for me before but i have had issues with my PC
and now i get this message:
[INTERSOLV][ODBC SQL Server driver]Communication link failure.[INTERSOLV]
[ODBC SQL Server driver][SQL Server]ct_connect(): directory service layer:
internal directory control layer error: Requested server name not found.
I suspect this will be a hard question to answer but I'd appreciate any input.
Cheers
Dave
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
This is a pretty general error. It could be caused by your network, or by
SQL Server settings. You didn't say how long ago it worked. Yesterday, or
last year? If yesterday you may have changed something. If last year, it
could be lots of things.
You didn't say what version you are using. If SQL Server 2005, check out the
connectivity tutorial which was designed to help users with just this
problem. http://msdn2.microsoft.com/en-us/library/ms345318.aspx
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Suttd via droptable.com" <u25367@.uwe> wrote in message
news:7e0eab8790a4c@.uwe...
> Hi all,
> Hope you can help, I am trying to link to some data tables into Access via
> the ODBC connection. It worked for me before but i have had issues with my
> PC
> and now i get this message:
> [INTERSOLV][ODBC SQL Server driver]Communication link failure.[INTERSOLV]
> [ODBC SQL Server driver][SQL Server]ct_connect(): directory service layer:
> internal directory control layer error: Requested server name not found.
> I suspect this will be a hard question to answer but I'd appreciate any
> input.
>
> Cheers
> Dave
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
>
|||Hi,
Thanks for your reply, I was using it last week, my PC burnt out and I
replaced it and used my old hard drive as a slave so I could have all my old
applications etc. I am using "Sybase System10" as my Driver? My knowledge
is quite limited in this area sorry if I am missing something silly here.
Regards
Dave
Rick Byham, (MSFT) wrote:[vbcol=seagreen]
>This is a pretty general error. It could be caused by your network, or by
>SQL Server settings. You didn't say how long ago it worked. Yesterday, or
>last year? If yesterday you may have changed something. If last year, it
>could be lots of things.
>You didn't say what version you are using. If SQL Server 2005, check out the
>connectivity tutorial which was designed to help users with just this
>problem. http://msdn2.microsoft.com/en-us/library/ms345318.aspx
>[quoted text clipped - 13 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
|||What version of SQL Server are trying to connect to?
Is SQL Server on the same computer or a different computer?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Suttd via droptable.com" <u25367@.uwe> wrote in message
news:7e34deec0e23c@.uwe...

> Hi,
> Thanks for your reply, I was using it last week, my PC burnt out and I
> replaced it and used my old hard drive as a slave so I could have all my
> old
> applications etc. I am using "Sybase System10" as my Driver? My
> knowledge
> is quite limited in this area sorry if I am missing something silly here.
> Regards
> Dave
>
> Rick Byham, (MSFT) wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server-connectivity/200801/1
>

No comments:

Post a Comment