Error: Pervasive-ODBC Client Interface-LNA-Pervasive-ODBC Engine Interface-Data Record Manager-The Btrieve file directory is invalid (Btrieve Error 35)

From Sage Intelligence Knowledgebase
Jump to: navigation, search


The following are examples of error messages that may occur:

  • [Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface][Data Record Manager]The Btrieve file directory is invalid(Btrieve Error 35)


This error can occur in the Pastel Partner BIC if the Pervasive Database Name for your data is pointing at a DDF file path that does not exist or is not accessable by the Pervasive Engine.


To rectify the problem open the Report Manager and from the Tools menu launch the PVS SQL DB Manager module. If you are accessing a server then you will need an administrative login to make changes. Drill down to the relevant Pervasive Database Name. Change the DDF file path on the property sheet on the right to a path where the DDF files are located and which is accessible by the Engine and then press apply. If you are not sure which is the relevant Pervasive Database Name you can find out by looking at the "Auto Connect Assumed Pervasive Database Name" property of the Home object in the Report Manager (the format of the name is PAS8 + company folder name e.g. PAS8LG2005). After making this change the connection issue should be resolved.

It is also recommended that the "Default pastel DDF File" property in the Report Manager be changed to point at the same DDF file path since this setting is used for creating any new Pervasive Database Names. Not changing this setting will result in the problem re-occurring when other Pastel companies are accessed.

Applies To

  • Pastel Partner BIC
  • Pervasive Enginge