Error 1918
I have packaged Oracle 10G client 10.2.0.3. But when the Msi installs it stops just before it is completed with this error:
"Error 1918.Error installing ODBC driver: Oracle OraClient10g_home1,ODBC error 13: Could not load the setup or translator library. Verify that the file Oracle in OraClient10g_home1 exists and that you can access it."
I have try all the solutions that are the net but it is not woking.
Does anyone have any ideas how to get round this?
Thanks
"Error 1918.Error installing ODBC driver: Oracle OraClient10g_home1,ODBC error 13: Could not load the setup or translator library. Verify that the file Oracle in OraClient10g_home1 exists and that you can access it."
I have try all the solutions that are the net but it is not woking.
Does anyone have any ideas how to get round this?
Thanks
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
nheim
17 years ago
Hi Kofi,
please log the installation. See: http://itninja.com/question/what-is-pxe?3
Then search the logfile for 1918 and have a look, which file it is exactly relating to. You got back only the file key so far, but need to figure out the real name of the file.
Another approach would be, to open the MSI and search for this file key.
Regards, Nick
please log the installation. See: http://itninja.com/question/what-is-pxe?3
Then search the logfile for 1918 and have a look, which file it is exactly relating to. You got back only the file key so far, but need to figure out the real name of the file.
Another approach would be, to open the MSI and search for this file key.
Regards, Nick
Posted by:
spartacus
17 years ago
Are you using the MSI ODBC tables in your package, by any chance ?
Use of these tables is known to be pretty unreliable (particularly with non Microsoft ODBC drivers) and several contributors on this forum have, in the past, recommended deploying such settings through the registry table instead - it tends to be more reliable.
Regards,
Spartacus
Use of these tables is known to be pretty unreliable (particularly with non Microsoft ODBC drivers) and several contributors on this forum have, in the past, recommended deploying such settings through the registry table instead - it tends to be more reliable.
Regards,
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
