RE: Difficulty with ASP and Client Access ODBC driver

On the server, I see the Client Access driver in the ODBC administrator,
Drivers tab. There's also a QDSN_10.121.17.7 DSN in User DSN.
I believe that part (finding the DSN) works correctly because if I use DSNs
and supply the wrong name, I get "Microsoft OLE DB Provider for ODBC Drivers
error '80004005', [Microsoft][ODBC Driver Manager] Data source name not
found and no default driver specified, /dbtest2.asp, line 59". I prefer
using the DSN-less connection if possible.

Thanks,
Loyd

--  
Loyd Goodbar
Programmer/analyst
BorgWarner Incorporated
ETS/Water Valley
662-473-5713
lgoodbar@xxxxxxxxxxxxxx


-----Original Message-----
From: DeLong, Eric [mailto:EDeLong@xxxxxxxxxxxxxxx] 
Sent: Tuesday, August 19, 2003 9:32 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Difficulty with ASP and Client Access ODBC driver


Loyd,

Are you sure there's a valid ODBC DSN defined on the production server?
Check your ODBC admin settings and verify that the IBM drivers are available
and properly defined.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Goodbar, Loyd (ETS - Water Valley) [mailto:LGoodbar@xxxxxxxxxxxxxx]
Sent: Tuesday, August 19, 2003 9:26 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Difficulty with ASP and Client Access ODBC driver


Here's the scenario: I have some ASP (classic/3.0) pages that access AS/400
data. Everything works correctly on my machine, running a local installation
of IIS. I can access remote SQL server data or AS/400 data.

However, when I run the ASP pages on our application server, the ASP page
always "hangs" on the "open connection" line when retrieving AS/400 data. I
have Client Access installed on the application server. The server can
access the SQL server database, but not the AS/400 database. The web page
doesn't time out, but sits there for a very long time (I stopped timing it
after 5 minutes).

<snip>