|
Electronic
Commerce Solutions ECS/ie
and Client Access ODBC Errors ECS/integrated
email relies on Client Access ODBC for Client/Server connectivity. This
configuration is normally very reliable once configured, but as with any
communications, the set up is the most troublesome time. The
most common ODBC related error messages are:
-
The Microsoft Jet database engine
cannot find the input table or query ‘IESP’. Make sure it exists and
that its name is spelled correctly. Error ref: 3078.
-
ODBC—insert
on a linked table ‘???’ failed.. Error ref: 3155.
-
ODBC—call
failed.. Error ref: 3146.
- The Microsoft Jet database engine stopped the process
because you and another user are attempting to change the same data at the
same time.. Error ref: 3197.
Please
perform all the steps in this check list until the problem is resolved: (1)
Confirm that the Server (AS/400) installation procedure was executed, and that
the that you ran the program "IESETUP" as documented in the following
document <ecsie_install.htm> (2)
Check that you have a Client Access DSN named "ECSIE" and that it is
configured correctly, as specified in document <ecsie_database_setup.htm>
be especially careful that the "Default Library" in the
"Server" tab has the library "ECSIE". (3)
If you are using Client Access V5R1 or V5R2, there are known problems with ODBC.
We recommend that you download and install the latest Client Access service pack
from IBM at
http://www-03.ibm.com/servers/eserver/iseries/access/casp.html
Ensure
that you delete and recreate the DSN called "ECSIE" following the
application of this service pack [back to step (2)] (4)
If you are using Client Access Express V5R1 or V5R2 the configuration panels look
different to earlier releases. Check that the following applies:
-
Confirm
that the name of the Client Access DSN is "ECSIE"
-
Confirm
that the "SQL Default Library" within the "Server" Tab is
set to "ECSIE"
-
Ensure
that "Commit Mode:" is configured as "Commit immediate
(*NONE)" (this
option is located under the "Server" tab within the
"Advanced" settings)
-
Confirm
that the option to "Convert binary data (CCSID 65535) to text" is checked.
This can be located under the "Translation" Tab.
(5)
Perform an independent test of the PC and AS/400 ODBC connectivity. Click
here for instructions.
(6)
If you receive the ODBC Connect Error: "Local relational database not
defined in the directory"
You
need add the relational database ECSIE. To add this enter WRKRDBDIRE
on the AS/400 command line. Enter a 1 in the Option column and ECSIE in
the Relational Database column. Press the Enter key. Then enter *LOCAL on the
Remote Location Name or Address line. Press the Enter key and the database will
now be defined.
(7)
The Client Access SQL Package can get corrupted, especially following the
upgrade of Client Access, which causes unpredictable ODBC
errors. The SQL Packages can be deleted and will be automatically regenerated. The
SQL Packages are normally created in QGPL, ensure this library
exists in your library list and then on an AS/400 command line, enter:
DLTSQLPKG
SQLPKG(ECS*) (8)
The ODBC Trace can help ECS Support diagnose potential ODBC errors, especially
error relating to the vague error message "ODBC Call failed,
ref:3146". To Enable ODBC Tracing perform the following:
-
Open the
ODBC Data Source Administrator tool.
-
Click the Tracing
tab .
-
Click Start
Tracing Now to enable tracing. Now, this button reads Stop Tracing
Now .
-
You can
specify the name of the log file in the Log File Path text box along
with the full path.
-
Click OK
.
-
Attempt to
reproduce the error within ECS/integrated email.
-
Report the problem to ECS for detailed analysis.
-
Remember
to click Stop Tracing Now .
(9)
Finally, contact ECS Support for assistance. |
