Error Messages (S) A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #Specified driver could not be loaded The "Specified driver" message suggests environment or driver name problems. If you receive "specified driver" errors, take the following action:1. cd into the root directory of your OpenLink client installation. 2. Run one of the following commands:. ./openlink.sh //For Bourne and Bash shells source openlink.csh //For C shells 3. Run the following command:echo $ODBCINI If ODBCINI is set, test your connection. If ODBCINI is not set, take the following action:1. cd into the root directory of your OpenLink client installation. 2. vi openlink.sh or openlink.csh. 3. Record the variables set in the file. 4. Set the variables on your command line. For example:export ODBCINI=/usr/openlink/bin/odbc.ini export ODBCINSTINI=/usr/openlink/bin/odbcinst.ini export UDBCINI=/usr/openlink/bin/udbc.ini 5. Test your connection.If the problem persists, open your odbc.ini file. You will find this file in the /bin sub-directory of your client's OpenLink installation. Then, find your DSN. For example:[OpenLink] Driver = /usr/openlink/lib/oplodbc.sl.1 Description = Sample OpenLink DSN Host = nkhatam ServerType = SQLServer 7 FetchBufferSize = 99 UserName = sa Password = Database = Northwind Next, insure Driver passes the full path to oplodbc.so.x or oplodbc.sl.x. The oplodbc.so.x or oplodbc.sl.x file is the driver file. It appears in the /lib sub-directory of your client's OpenLink installation. The file's extensions (.so/.la) and versions (.x) vary.Evidence Name of .taz files odbc.ini File Output of set uname -a