Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.


Btrieve error 11 specified filename is invalid

Btrieve error 11 specified filename is invalid

I'm getting this error on about 80% of the computers when I try to create an odbc connection to pervasive.  On a few there are NO problems and it goes thru fine.  But on most I get that  stupid error.  I'm using pervasive 2000i sp 4.  the full error message is below.

[pervasive odbc client interface][LNA pervasive interface data][record manager] the specified filename is invalid (btrieve error  11)

I've done some searching and google and found very veiled and confusing information about this error.  


RE: Btrieve error 11 specified filename is invalid

Where's the data?  
WHat's your "Embedded Spaces" setting set to?
Does this occur in the Pervasive Control Center or an application?  If it's an app, does PCC fail too?  
When exactly does this error occur?
Are you using NetWare?

Certified Pervasive Developer
Certified Pervasive Technician

RE: Btrieve error 11 specified filename is invalid

The data is on a novell server.  I'm not sure what your're referring to by "embedded spaces".  I get this error when I try to test the odbc connection in the 'ODBC data souce administrator' which is in admin tools in control panel.  I've tried using both relative and unc path names with no success.

On the computers that have no problem either a relative or unc work.  

RE: Btrieve error 11 specified filename is invalid

Are you creating an Engine DSN on the client?  You should create a Client DSN on the client pointing to an Engine DSN on the server.
Are you using the Novell client?  If so, check out the following from another site:


There is a patch for the 4.91 SP2 Novell Client that may fix this problem. It is the "Novell Client Post 4.91 SP2 CALWIN32.DLL" patch located at

Certified Pervasive Developer
Certified Pervasive Technician

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close