Microsoft ODBC Drivers are not updated during an upgrade of Desktop and Laptop Option

Article: 100062779
Last Published: 2024-01-25
Ratings: 0 0
Product(s): Desktop Laptop Option

Problem

During an upgrade of Desktop and Laptop Option (DLO), the Microsoft ODBC Drivers are not updated to the latest supported version.

Although both Microsoft OLE DB and ODBC Driver packages are included in the DLO installation package, when an upgrade is carried out, only the OLE DB components are updated.

NOTE:
A new installation of DLO will install both Microsoft OLE DB  and ODBC Driver packages.

 

Error Message

None

 

Cause

DLO upgrades are not automatically updating the Microsoft ODBC Drivers, due to historical issues applying these on WIndows 2008/2008 R2 systems.

 

Solution

Workaround:

To manually update the Microsoft ODBC Drivers, follow the procedure below; 

  • Expand the DLO installation package (i.e. Veritas_Desktop_and_Laptop_Option_9.8.2_98204a_64-bit.zip)  used during the DLO upgrade.
  • Navigate to the 'msodbc' sub-folder.
  • Extract the msodbcsql_x86.msi  or  msodbcsql_x64.msi  file (use the version that matches the bit-level of your SQL server installation).
  • Run the extracted  msodbcsql_xx.msi file and complete the installation to install the version of ODBC Drivers supported by that version of DLO.

The version of ODBC Drivers can be identified by reviewing the  Control Panel - Programs - Programs and Features  in the Operating System of the DLO Administration Server. 
In the list of installed Programs, look for 'Microsoft ODBC Driver ## for SQL Server' and check the Version column (i.e. 'Microsoft ODBC Driver 17 for SQL Server'  is version 17.10.5.1)


 

This issue is currently being considered by Veritas Technologies LLC to be addressed in the next major revision of the product.  There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time.  Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.


 

Was this content helpful?