lurcher
Posts: 7
Joined: Mon Jul 24, 2006 10:43 am

Error 13 when installing ODBC driver

Hi,

I have a installer, that installs a ODBC driver. The driver requires some support libraries that are shared over several of our products, so we put these libs in

Program Files/Common Files/Company/Shared

and add that path to the environment variable PATH so they can be found in use.

On Vista this works fine, but on win 2000, the sequence to install the ODBC driver fails with a error 13, as it can't find the support lib.

I have checked the logs, and the path variable is being set before the driver is installed, but it seems that within the install process the variable isn't being set.

Have you seen anything like this before?

Ok, a simple solution would be to install the libs in system32, but that seems to be the wrong solution IMHO.

If there is anything else you need to help me understand how to fix this, let me know.

Thanks (in advance).
gigi
Posts: 2103
Joined: Tue Apr 11, 2006 9:55 am
Contact: Website

Hi,
Have you seen anything like this before?
All environment variables created during execution of a process are available only after the process is finished. In this case they are available after installation. This is because a copy of the environment variables are read when the process begins.

Read more about this here:
http://msdn2.microsoft.com/en-us/library/aa368369.aspx
The driver requires some support libraries that are shared over several of our products
If placing the libs in the system32 folder is not a solution for you then you can create a separate installation to install those libs that writes the libs path to the path environment variable. And use this new installation as prerequisite for all your products.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com
lurcher
Posts: 7
Joined: Mon Jul 24, 2006 10:43 am

Thanks for that, that explains whats happening, and the indicates why it only occurs with 2000

Installing to system32 isn't a problem for me, but it seems to contradict the MS guidelines for vista and later.
lurcher
Posts: 7
Joined: Mon Jul 24, 2006 10:43 am

I may have found a solution that fits the problem.

I have created a tempory copy of the file in the windows directory so its found by the ODBC install. and this gets deleted on the end of the install.

Also I can make this conditional on it being 2000.

Can anyone see any problem with doing this?

Return to “Common Problems”