Error: Specified driver could not be loaded due to system error 126 (Pervasive ODBC Client Interface)

From Sage Intelligence Knowledgebase
Jump to: navigation, search


The following are examples of error messages that may occur:

  • Specified driver could not be loaded due to system error 126


This error occurs when certain elements of the Pervasive ODBC layer have become corrupt or are missing. This can usually be verified by checking for the Pervasive ODBC Driver version numbers under the drivers tab of the Windows Control Panel ODBC Data Source Administrator Tool.


Since the Pervasive ODBC layer is installed as part of the Pervasive Engine installation the current workaround requires the Pervasive Engine to be uninstalled and re-installed. Alchemex are doing further investigating into the issue. If you are experiencing this problem then please assist us with this issue by gathering the information specified below and then contact us.

1. Verify these files exist and note down File size and Product Version and Product Name number of: C:\PVSW\Bin\w3odbcci.dll C:\PVSW\Bin\w3odbccs.dll C:\PVSW\Bin\w3odbcce.dll C:\PVSW\Bin\w3odbces.dll

2. Verify the Windows Path environment variable by going to a command prompt and entering the word PATH

3. Verify/Compare the Windows registry settings for the two ODBC drivers. Below are settings from a functioning installation:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive ODBC Client Interface] UsageCount= 00000001 Driver=C:\PVSW\Bin\w3odbcci.dll Setup=C:\PVSW\Bin\w3odbccs.dll Help=C:\PVSW\Bin\w3odbccs.hlp SQLLevel=0 FileUsage=0 DriverODBCVer=03.51 ConnectFunctions=YYY APILevel=2 [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Pervasive ODBC Engine Interface] UsageCount=00000001 Driver=C:\PVSW\Bin\w3odbcei.dll Setup=C:\PVSW\Bin\w3odbces.dll Help=C:\PVSW\Bin\w3odbces.hlp SQLLevel=0 FileUsage=0 DriverODBCVer=03.51 ConnectFunctions=YYY APILevel=2

Applies To

  • Pervasive Engine