Hello,
You are right. An HP Response Center engineer suggested the same thing.
She ordered the most current versions for us and we should get them
tomorrow. At her suggestion, I DSCOPY'ed the files off our development box
to our production box and "wal-la" it works like magic.
One suggestion I might make for anyone else trying to troubleshoot the
situation is to enable the checkboxes on the PC-side ODBCLink/SE
configuration for
1) Trace ODBC calls on client to file ODBCLINK.LOG
2) Trace SQL calls on the server
Each attempt to use ODBC will create/append records to the log file in the
current folder on your PC called ODBCLINK.LOG and also the server in
ODBCLOG.ODBCSE.SYS
These log files have proven very helpful in our situation.
Eben
-----Original Message-----
From: Melvin R Rees [mailto:[log in to unmask]]
Sent: Tuesday, January 02, 2001 8:02 PM
To: [log in to unmask]
Subject: Re: MPE6.5 ODBC SE
Hello,
I've hade the same error when the ODBC versions did not match. Make
sure you have the same ODBC on both HP 3000's.
You could try downloading the drivers seperately from each machine and
then installing and trying them in sequence. They should ne require a
re-boot of the PC to switch back and forth.
Also, the latest versions of ODBC are much better than older ones. We
had at least one problem with tables that seem to disappear because
something went wrong after reading a large amount of data. (They would
reappear after rebooting the PC).
Hope this helps.
Rgds
Mel Rees
CMT, Inc.
On Tue, 2 Jan 2001 18:00:52 -0600 (Central Standard Time), EBEN YONG
<[log in to unmask]> wrote:
>Hi,
>
>I have been able to successfully connect to our IMAGE DB's via ODBC on our
>development e3000, but am not successful on our production machine. Here's
>what the log says:
>
>101/01/02 15:42:46 0120 ODBC Listener Started
>101/01/02 15:43:14 0120 Listener created new connection as SYS1 (PIN 89),
>IP=19
>2.20.30.184
>101/01/02 15:43:14 0089 ODBCLNSE E.57.08 started from sockets
>101/01/02 15:43:15 0089 User MGR.AIH connected to HLTHDBE.DATA.AIH,
>ODBCVer=2.0
>0 ClientVer=E.56.12
>101/01/02 15:43:15 0089 Normal exit, Received 4 requests (247 bytes), Sent
0
>re
>cords (94 bytes), CPU=1 (94.5%)
>101/01/02 15:44:08 0120 Listener created new connection as SYS2 (PIN 278),
>IP=1
>92.20.30.176
>101/01/02 15:44:08 0278 ODBCLNSE E.57.08 started from sockets
>101/01/02 15:44:09 0278 User MGR.AIH connected to HLTHDBE.DATA.AIH,
>ODBCVer=2.0
>0 ClientVer=E.56.12
>101/01/02 15:44:10 0278 [Allbase]Table/View [log in to unmask] not found.
>(DBERR
> 2206)
>
>The first attempt receives a NORMAL EXIT, when trying to connect using
Win32
>Perl 5.6, but the script returns this error:
>
>C:\APACHE\PUB\cgi-bin>PERL ODBCTEST.PL
>DBD::ODBC::db prepare failed: [ODBCLN32.DLL] Data transmission error:
>(SQL-S100
>0)(DBD: st_prepare/SQLPrepare err=-1) at ODBCTEST.PL line 10.
>Can't prepare SQL Statement: [ODBCLN32.DLL] Data transmission error:
>(SQL-S100
>0)(DBD: st_prepare/SQLPrepare err=-1) at ODBCTEST.PL line 10.
>
>The second attempt is from MS Access 2000, and that fails with a dialogue
>box that says "ODBC--call failed, [ODBCLN32.DLL] Data (#-34)". You can see
>from the log above that it is looking for a table/view that does not exist!
>
>I've set up the IMAGESQL DBE identically on both e3000s but it's not
>connecting to the Production box. Any ideas would be appreciated. Thanks.
>
>Eben
>
|
