G
Guest
Hi,
BACKGROUND:
I am using c#. I made an application that connects to our database server
using a system DSN. I am using the System.Data.ODBC instructions. It works
just fine on the client machines.
SYSTEM:
Windows 2000 terminal server
Database server is progress 9.1C
PROBLEM:
When I deploy this app on the terminal server the connection does not
happen. The exception is NO DATA- No information availible. This happens
when I try to fill a simple dataset.
STEPS I HAVE TRIED ON THE TERMINAL SERVER:
1) Made a call to the SQL server using DSN--success
2) Verified the System DSN setup is the same on the terminal server as it is
on my desktop.
3) Mispelled the DSN in the code and got a new Error Cannot find DSN. So I
know I an looking at the correct DSN.
4) Opened an Access link table to the progress database using the same
DSN--success.
5) Tried making a user DSN on the terminal server- failed
6) On the ODBC DSN setup changed the host name to an IP.--failed.
What other things can I try since it works with SQL DSNs, but not the
Progress DSNs. Again the Progress call works on a client machine, but not
the terminal server.
BACKGROUND:
I am using c#. I made an application that connects to our database server
using a system DSN. I am using the System.Data.ODBC instructions. It works
just fine on the client machines.
SYSTEM:
Windows 2000 terminal server
Database server is progress 9.1C
PROBLEM:
When I deploy this app on the terminal server the connection does not
happen. The exception is NO DATA- No information availible. This happens
when I try to fill a simple dataset.
STEPS I HAVE TRIED ON THE TERMINAL SERVER:
1) Made a call to the SQL server using DSN--success
2) Verified the System DSN setup is the same on the terminal server as it is
on my desktop.
3) Mispelled the DSN in the code and got a new Error Cannot find DSN. So I
know I an looking at the correct DSN.
4) Opened an Access link table to the progress database using the same
DSN--success.
5) Tried making a user DSN on the terminal server- failed
6) On the ODBC DSN setup changed the host name to an IP.--failed.
What other things can I try since it works with SQL DSNs, but not the
Progress DSNs. Again the Progress call works on a client machine, but not
the terminal server.