Database driver load failed -

Hi list,
I am making new installation of Enterprise Xe release with 4 languages Polish,Russian,Hungarian and Czech. I am working on windows 2000 server system with sp4 and I am installing only one production environment. I have installed deployment server and now I am doing installation workbench in order to install enterprise server. I have installed everything according to installation guide up the point of doing installation workbench. I finished installation plan on deployment and next step is to run workbench which didn't finished successfully. So I have on enterprise only database Ms SQL Server 2000 and Microsoft Visual Studio 6.0 with only C++. I have started up scripts :
DB_SQLSRVR70.sql - creates databases on enterprise server
USERS_SQLSRVR.sql - creates users
and I have started up also LOADALL.bat
On deployment server I copied four CDs with four languages and during installation plan I have checked off only these four required languages.
Everything was good but at the and of workbench when there is a merge tables I received a windows popup with message "Database driver load failed -". I can not find in jdedebug any relevant information saying the same but in details. The problem occured during start-up of last two reports R98722C and R98722T.
In attachment my screen picture and below my jde.log:

1100/1164 Fri Apr 08 13:07:53 2005 jdb_ctl2600
Starting OneWorld

1100/628 Fri Apr 08 13:09:34 2005 jdb_drvm372
JDB9900160 - Failed to load driver library

1100/628 Fri Apr 08 13:40:07 2005 jdb_omp11666
JDB9900254 - Failed to initialize driver.

1100/628 Fri Apr 08 13:40:07 2005 JTP_CM262
JDB9909002 - Could not init connect.

1100/628 Fri Apr 08 13:40:07 2005 JTP_TM960
JDB9909100 - Get connect info failed: Transaction ID =

1100/628 Fri Apr 08 13:40:07 2005 jdb_rq11804
JDB3100013 - Failed to get connectinfo

1100/628 Fri Apr 08 13:40:08 2005 jdb_drvm372
JDB9900160 - Failed to load driver library

1100/628 Fri Apr 08 13:40:09 2005 jdb_omp11666
JDB9900254 - Failed to initialize driver.

1100/628 Fri Apr 08 13:40:09 2005 JTP_CM262
JDB9909002 - Could not init connect.

1100/628 Fri Apr 08 13:40:09 2005 JTP_TM960
JDB9909100 - Get connect info failed: Transaction ID =

1100/628 Fri Apr 08 13:40:09 2005 jdb_rq11804
JDB3100013 - Failed to get connectinfo

1100/628 Fri Apr 08 13:40:09 2005 jdb_cach875
JDB9900003 - Failed to open table F98613

1100/628 Fri Apr 08 13:40:09 2005 jdb_drvm372
JDB9900160 - Failed to load driver library

1100/628 Fri Apr 08 13:40:10 2005 jdb_omp11666
JDB9900254 - Failed to initialize driver.

1100/628 Fri Apr 08 13:40:10 2005 JTP_CM262
JDB9909002 - Could not init connect.

1100/628 Fri Apr 08 13:40:10 2005 JTP_TM960
JDB9909100 - Get connect info failed: Transaction ID =

1100/628 Fri Apr 08 13:40:10 2005 jdb_rq11804
JDB3100013 - Failed to get connectinfo

1100/628 Fri Apr 08 13:40:10 2005 jdecgsc189
MSC0000028 - Could not load F00921 cache

1100/628 Fri Apr 08 13:40:10 2005 jdb_drvm372
JDB9900160 - Failed to load driver library

1100/628 Fri Apr 08 13:40:10 2005 jdb_omp11666
JDB9900254 - Failed to initialize driver.

1100/628 Fri Apr 08 13:40:10 2005 JTP_CM262
JDB9909002 - Could not init connect.

1100/628 Fri Apr 08 13:40:10 2005 JTP_TM960
JDB9909100 - Get connect info failed: Transaction ID =

1100/628 Fri Apr 08 13:40:10 2005 jdb_rq11804
JDB3100013 - Failed to get connectinfo

1100/628 Fri Apr 08 13:40:10 2005 jdb_drvm372
JDB9900160 - Failed to load driver library

1100/628 Fri Apr 08 13:40:11 2005 jdb_omp11666
JDB9900254 - Failed to initialize driver.

1100/628 Fri Apr 08 13:40:11 2005 JTP_CM262
JDB9909002 - Could not init connect.

1100/628 Fri Apr 08 13:40:11 2005 JTP_TM960
JDB9909100 - Get connect info failed: Transaction ID =

1100/628 Fri Apr 08 13:40:11 2005 jdb_rq11804
JDB3100013 - Failed to get connectinfo

1100/628 Fri Apr 08 13:40:11 2005 jdb_drvm372
JDB9900160 - Failed to load driver library

1100/628 Fri Apr 08 13:40:11 2005 jdb_omp11666
JDB9900254 - Failed to initialize driver.

1100/628 Fri Apr 08 13:40:11 2005 JTP_CM262
JDB9909002 - Could not init connect.

1100/628 Fri Apr 08 13:40:11 2005 JTP_TM960
JDB9909100 - Get connect info failed: Transaction ID =

1100/628 Fri Apr 08 13:40:11 2005 jdb_rq13770
JDB3100038 - Failed to get connectinfo

Did you check your ODBC connectivity with SQL DB on deployment server?
Do this and test it successfully, then delete the plan and recreate it and run it ATTANDED MODE.

Do not install the language yet finish the plan then create another plan for language and run it.

One last thing, I think I’m not so sure that you can install one language only OR one at a time

Good Luck

I have checked all datasources and I have created ODBC's in my windows on deployment and also I added it on my enterprise server. I thought also that it will be better to install enterprise server first and after that languages but documentation says that I can do it during normal process of installation. This problem looks strange for me because there is no info about why it happen in logs, and which driver it is looking for.

Then you need to get a fresh copy of planner.mdb and jdeb7.mdb (if you did not apply an ESUs) and create new plan

Hi Sebastiau,

Go to Knowledge Garden and look for Solution 200949255.

Regards,

Hi Sebastian,
Thank you a lot for advice I saw it but I am not using OLEDB but ODBC connections. So this document is not a solution for me. I prepared another installation plan without languages and during workbench the situation is similar, I can not run these two reports. Have you got any other ideas?

Hi,

Verify that your Deployment and Enterprise are compliant
to MTRs : Windows version, SP level, MDAC level,
SQL 2000 SP level, Internet Explorer version.

Regards,

Hi Sebastian,
I checked it and reinstalled my Deployment again and I also prepared different custom instalation plan without languages and result is the same. But I can run other reports without that error. Maybe there is something not written in some tables ? It looks like that to me because I found on the list some other issues similar to mine and there at the end of sebtence "Database driver load failed -" was the name of dll file. For example :
"Database driver load failed - jdboci90.DLL"
in case
ERP9 Installtion Plan Error
#65387 - 12/15/03 02:00 AM

Hi Sebastiau,

Your installation is looking for Oracle databases.
Are you on an Oracle install or an SQL one?
If you're on an SQL install, please check all of your
Data Sources to be sure that none of them is "O".

Sebastian

We were flooded with this same problem after our last upgrade. You need to either load Oracle on the client machine or upgrade it. After our upgrade from Xe to 8.10, we had to upgrade all the client PC's (those running Fat Client) to Oracle 9i. Hope this helps.

Hi Sebastian and Wkunneke,
I am not using Oracle databases, I am using SQL Server database and I mentioned only this example which I found on the list. I have set all datasources correctly. Previously I installed B9, E810 and E811 and didn't see such a error.
Maybe some other recomendations?
I will try to reinstall it again today.

Sebastian,

We are primarily an AS 400 shop, but one custom application I wrote inside of OneWorld makes use of some Oracle GIS data. My CNC guy set up a datasource just for this one Oracle table. Anyone who accesses this application has to have Oracle drivers loaded. Just a thought since the error message you get suggests that you are using Oracle somewhere. I'll be curious to hear what the problem turns out to be. Good luck,

Hi friends,
I found the solution which was as usual very easy. When I created installation plan at the first screen there was a check button "Coexistent with OneWorld" which has to be uncheck. It was checked by default and at the end of workbench it refers to the "AS400 Common" datasource in table F98611. This datasource, I mean this row in the table obviously was empty so that is the reason I get the message "Database driver load failed -" without the name of the dll file. Now it is clear to me

Hi, I tried to do a fresh E1 8.11SP1 installation
(Win2003/Oracle DB 10gR2/Oracle AS 10gR2) this week
and hit the same error "Database driver type name
could not be determined for type O" when I tried
to run Installation Workbench. It was later determined
that Oracle Client 10gR2 on Deployment Server is the
cause. After re-installing Oracle Client 10gR1 on D/S,
the error is gone. Nowhere in the installation guides
and Customer Connection ever spefified this point. :-(

Ying-Jie Chen, Systex Corp, Taipei, Taiwan

Hi all, according to the E1 8.11SP1 MTR. You should use Oracle 10g R1 (10.1.0.4) for DB and client for a
healthy installation. The Oracle version denoted in previous post is incorrect !
Yingjie Chen