Errors on installation path validation

timvan007

Member
We are installing a deployment server using ERP 8.0 to migrate to new as400 hardware, and running into an issue validating our installation plan. Everything is able to validate except for the machine. We have a iSeries 740 running v7r1, deployment server is Server 2008 R2 with visual studio 2008 and access 2003. When I try to validate the install plan, I keep getting the following errors. I have installed IBM i Access on the server, ODBC drivers are installed, but I cannot track down the next thing to troubleshoot for this.

1660/2980 Mon Jul 28 21:54:25 2014 ODBC_U1.C870
ODB0000170 - SQL Prepare failed in Table F9865
Column SWFMNM
Database Object Librarian - B7334


1660/2980 Mon Jul 28 21:54:25 2014 ODBC_U1.C874
SQL Prepare failed, See Log


1660/2980 Mon Jul 28 21:54:25 2014 ODBC_U1.C875
[IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0204 - F9865 in OL7334 type *FILE not found. - SQLSTATE: S0002


1660/2980 Mon Jul 28 21:54:25 2014 JDBODBC.C1470
ODB0000055 - Describe table failed for table F9865.


1660/2980 Mon Jul 28 21:54:25 2014 jdb_drvm.c824
JDB9900168 - Failed to initialize db request


1660/2980 Mon Jul 28 21:54:25 2014 JTP_CM.C1088
JDB9909007 - Unable to obtain driver request handle


1660/2980 Mon Jul 28 21:54:25 2014 DLG_MSGB.CPP190
Unable to retrieve help information from the F9865 table


1660/2980 Mon Jul 28 21:54:25 2014 ODBC_U1.C870
ODB0000170 - SQL Prepare failed in Table F9860
Column SIOBNM
Database Object Librarian - B7334


1660/2980 Mon Jul 28 21:54:25 2014 ODBC_U1.C874
SQL Prepare failed, See Log


1660/2980 Mon Jul 28 21:54:25 2014 ODBC_U1.C875
[IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0204 - F9860 in OL7334 type *FILE not found. - SQLSTATE: S0002


1660/2980 Mon Jul 28 21:54:25 2014 JDBODBC.C1470
ODB0000055 - Describe table failed for table F9860.


1660/2980 Mon Jul 28 21:54:25 2014 jdb_drvm.c824
JDB9900168 - Failed to initialize db request


1660/2980 Mon Jul 28 21:54:25 2014 JTP_CM.C1088
JDB9909007 - Unable to obtain driver request handle
 
A late but valid update, we chose to take a different route. Rather than starting with a vanilla install and migrating custom code, we copied the entire folder structure of the deployment server, libraries on the as400, and essentially cloned the environment. I did not originally think it would be an option considering we migrated from v5r4 to v7r1, SP23 to SP24, and Server 2000 (deployment server) to 2008 R2 all at the same time, but it ended up solving a multitude of issues and saved a lot of product packaging.
 
Back
Top