Data Access Worldwide Knowledge Base

Article ID 2026
Article Title ERROR: "BTRIEVE: Filename bad FILE.DDF" in Web Application
Article URL http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2026
KBase Category PERVASIVE.SQL
Date Created 07/21/2004
Last Edit Date 07/21/2004


Article Text
PROBLEM:
When running a web application created with Visual DataFlex 10 (accessing Pervasive.SQL files), the following error gets added to the Windows Application log:

Session failed to initialize: Fatal error occurred during child process
initialization: BTRIEVE: Filename bad FILE.DDF VDF Error#: 21011 in line: 16359.

I can compile and run the application from the Studio but when running the application directly from a browser (e.g. http://localhost/myapp/mainpage.asp) I get the same error.

Could this be a licensing issue? I am running the Connectivity Kits installed with VDF10.


SOLUTION:
It looks like File.DDF cannot be found. It is not a licensing problem.

Remember that mapped drives cannot be used when accessing applications from the browser -- if they are used, the error you described will be generated.

Also make sure your data path includes the path where the correct DDFs can be found -- or you use BTR_PATH and DDF_PATH keywords in the dfbtrdrv.int configuration file -- and there is no rights issue (VDF Web Server has permission to access workspace and Pervasive files) in the mix.





Contributed By:
Marcia Booth
Company: Data Access Worldwide
Web Site: http://www.dataaccess.com

Web Links Related to this Article
DAW Knowledge Base article 1523: DOC: Error numbers in Pervasive.SQL Connectivity Kit
URL=http://www.dataaccess.com/KBasePublic/KBPrint.asp?ArticleID=1523

DAW Knowledge Base article 953: HOWTO: Access Data on Other Servers from a WebApp Server Application
URL=http://www.dataaccess.com/KBasePublic/KBPrint.asp?ArticleID=953


Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.