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.

Students Click Here

Invalid security token

Invalid security token

Invalid security token

Windows 2003 SP1 - Pervasive SQL 2000i SP4.  
In the pvsw.log on the server we get this error
  A status 94 was generated for user PC127\reception on file D:\DATA\FILE.DDF because the MicroKernel received an invalid security token.
It's not always file.ddf,it could be any of the ddf's or any of the data files.  

A bit of history on this.  This originally started happening about 8 weeks ago, I visited the client site and the Active directory and windows infrastructure was a mess so I basically rebuilt the entire domain and all was good, IE no errors until about 1 week ago until the errors started again.

All users do have the appropiate rights to the directory where that data is located as they can launch the program initially and use it.  The only other thing is if we reboot the server all is OK for a day or so and then the errors start again.

Any help appreciated.

All you need in this life is ignorance and confidence; then success is sure.
  - Mark Twain

RE: Invalid security token


We had something similar to this back in 2004 - BUT - it was on P.SQL 8.  We got a new service pack installed and that fixed the problem.  

I would suggest trying a higher service pack - unfortunately p.SQL 2000i is no longer supported but you may be able to get hold of the higher service packs if you get in touch with Pervsive directly.

The web site is http://www.pervasive.com/support/lifecycle_psql.asp

Best of luck,

RE: Invalid security token

SP4 was the last service pack for PSQL 2000i.  
Have you run a virus scan recently?  You might turn on Windows auditing to get a feel for what is happening a the OS level to cause this.  Here's an old KB solution I found on Pervasive's site that talks about 94s and security auditing:


Solution ID: 00015981

Status 94 (Permission Error) running the Btrieve for Windows NT server engine on a volume formatted for NTFS

Problem Description:  
Status 94: "The application encountered a permission error" running Btrieve for Windows NT server engine on a volume formatted for NTFS

Problem Environment:Btrieve v6.15 Windows NT  
Microsoft Windows NT Server  
NTFS Volume  

Cause of this problem:

Solution Notes:  
To fix the error:  
1. Go to User Manager for Domains in the Administrators Tools group.  
2. Under Policies, select Auditing-> Audit These Events-> and check File & Object Access->Use of User Rights  
3. Exit User Manager, and run Explorer.  
4. Select the directory that Btrieve is trying to access, and in which the permission error is generated.  
5. Go under properties, choose ->Auditing->check Add->select "Everyone"->check add->click OK.  
6. Check Replace Auditing on Existing Subdirectories and Replace Auditing on Existing files. In the lower check boxes, check the following:  
-Read Success Failure  
-Write Success Failure  
-Execute Success Failure  
7. Click OK.  
8. Exit and login to generate the original error.  
When you get the error, go into the Event Viewer, select Security from the file menu, and inspect the event log. WindowsNT logs all successful or failed file or directory accesses, and the reason for success or failure.

Certified Pervasive Developer
Certified Pervasive Technician

RE: Invalid security token


At this moment in time getting moved to V8 or above is not an option, something to do with the logic in the programs so the programmers tell me.  I'm trying to push them to make the necessary changes but it's not easy.


I've obviously ensured that the users have the necessary rights to the directory with the btrieve files in it but it's an interesting idea to turn auditing on.

The only other things I found whilst browsing the internet for this error was things like invalid SAT entries in the registry on the PCs and the possibility of the named pipe connection being broken between client and server.

I've cleared all the invalid SAT entries out using the pvsw.exe tool from Pervasive and turned off the Runtime support feature on the client (there are no netware servers involved)

If we still get errors after this I may turn my attention to the anti virus software that they run.

All you need in this life is ignorance and confidence; then success is sure.
  - Mark Twain

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! Already a Member? Login

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