ODBC Error with Terminal Server

ODBC Error with Terminal Server

Post by Carlo » Wed, 19 Mar 2008 20:56:07


We have a server with SQL Server 2000 SP3 and another functioning as a
Corporate Gateway running Terminal Server for users that need to run an
Access Aplication (Access 2003 and an ODBC).

Both of them have Windows Server 2003 R2 Operating System and they have a
Cisco Pix Firewall between them.

The problem occurs when an user initiates a remote session (TS) and after a
while working it appears a message similar to this:

ODBC: call failed.
[Microsoft][ODBC SQL Server Driver]Error in comunication link (#0)

Could you help us to solve this issue?

Thanks in advance.


1. ODBC errors on terminal server

2. Terminal Server Profiles in WIN2003 Terminal Server...moving to WIN2008 Terminal Server

Good morning!

Just a simple, basic question!

Have a client with two WIN2003 Terminal Servers. I have the TS Lockdown
thing going (via GPO and loopback processing). Additionally, we have folder
redirection for My Documents and for Desktop (can not do App Data for really
stupid reasons). Also - and here is part of the question - about to
implement the Terminal Server specific profile. Client is going to be
moving to two WIN2008 Terminal Servers in the near future.

Question: Assuming that I move forward with creating the Terminal
Server-specific profile this week, how is the Terminal Server specific
profile going to be affected when we move to the two WIN2008 TS Boxes?

Am I going to see \\servername\tsprofiles$\username.v2? Read: like when we
move clients that have roaming profiles (not Terminal Server....just
"normal" roaming profiles) from Windows XP to Windows Vista or, now, Windows
7? This 'username.v2' folder is an entirely new profile......which normally
is not an issue. However, in the case of this particular client there are
some things that we need to do to each profile for things to work (Scanners
that are attached to the desktop....I believe that RemoteScan is the
software used....have to copy some files and folders specific to that
scanning software up to the WINDOWS directory in each user's profile).

I am thinking that it would be better to set up the TS specific profiles
once the new TS boxes are in place.

Has anyone done this yet? And can share the experience. Thanks,


3. ODBC SQL Server Error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectioOpen (Connect()).

4. SQL Server ODBC Error: [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectioOpen (Connect()).

5. Advanced Server 7 ODBC error - [DataDirect][ODBC SequeLink driver][SequeLink Client]TCP/IP error, connection refused

6. Advanced Server 7 ODBC error - [DataDirect][ODBC SequeLink d

7. cannot access terminal server after creating new server publishing terminal server rule

8. Windows 2003 Terminal Server and Windows 2000 Terminal server License server

9. Terminal Server and Terminal Server License Server

10. Creating ODBC link over Terminal Server

11. Terminal Server / ODBC

12. How do you publish ODBC via Terminal Server to TS Users

13. ODBC-connection problems with Access application on terminal server

14. ODBC Windows 2003 Terminal Server