Re: Client Access and V5R1 and ODBC

Jose,

Have you started the cae history log ?

programs, client access express, service, history log
you will be prompted that the history log will be started
Run what you are doing again
After the error occurs, go back to the history log and locate the error
message.
Click on the error message.  More info on the error is displayed.

Hope this helps,

Steve Richter


----- Original Message -----
From: "Rodriguez, Jose Amable" <jarodriguez@grupom.com.do>
To: <midrange-l@midrange.com>
Sent: Friday, December 21, 2001 11:29 AM
Subject: Client Access and V5R1 and ODBC


> Hello all,
>
> I have a couple of problems with our new 820.  Here's a little
> history.  We were running V4R5 on an older 600 box and have now upgraded
to
> an 820 running V5R1.  We are having trouble with two things as of now:
>
> 1.  Client access V4R5 will not connect to the V5R1 box (using TCP/IP of
> course).  I cannot get it to work.  The error messages I get are as
follows
> when I verify the connection:
>
> CWBCO1003 Winsock error, function connect returned 10061
> CWBCO1006 unable to connect to server mapper (port 449) on system DKSA2TCP
> CWBCO1016 Connection Verify failed.
>
> I have checked the host servers and have started all of them.
> I have verified that the QUSER profile is active and with its correct
> settings.
>
>
>
> 2. ODBC acts strange with Crystal Reports on V5R1.  Every table I
reference
> has a *N.Libray.Table as it's name.  The puzzling item to me is the *N.
>
>
> 3. WHen I try to creat a new report with crystal reports, I get the
> following error message when I use ODBC:
>
> ODBC error: [IBM] [Client Access Express ODBC Driver
(32-bit)]Communication
> link failure. comm rc=10053 - CWBC01003 - Winsock error, function returned
> 10053, DKSA2TCP
>
>
> Any help on these items will be greatly appreciated.
>
> Thanks in advance,
>
> Jose Amable Rodriguez
> Dominican Knits, S.A. (GrupoM)
> (809) 241 - 7171 x 3253
> jarodriguez@grupom.com.do
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>