Ok, every once in a great while this happens. Setup a new client, and the message pops up when launching c:\ists\evoerp.exe "Wbtrvmemo.B could not be opened and Btrieve memos will not be available".  Click on OK, and the EvoERP login screen comes up and everything seems to work just fine after that.  But I cannot seem to figure out
why this error occurs. I have this on 2 systems.  Not occurring on other systems, so it's got to be something local to these 2 systems.  
 
Anyone have an idea?  I have checked permissions for the Pervasive program and ISTS folders, disabled the HIPS (host intrusion prevention), and it still persists......
 
We need a comprehensive troubleshooting document on just this error. The reporting history of past occurrences is incredible....
 
Val

Figured it out myself.  In our environment we have to set the "use btrvmemos" in the taspro7.ini file to 0 instead of 1.
 
We were also getting an error with some programs when in Evo, and when exiting Evo (the users were seeing that "comprehensive" error window that allows you to close application continue application, exit.  In these instances, an install of the Pervasive 11 sp3 client enables both the local micro kernel engine and the remote micro kernel engine. This is creating a conflict that results in the access violations listed in the report from this error screen.  When the client is installed, the proper setting needs to be made in the Pervasive Control center, and it had not been. Once we turned off the local micro kernel engine, it was fine, no more errors.
 
Just an FYI for anyone else who may come across these issues.

Make sure the client it out of Evo.
Run the Pervasive Control Center as the local admin user.
When it opens, find and click on the link "Configure Microkernel Router".
Under "Access" settings there are options for "Use Local MicroKernel Engine" and also "Use Remote MicroKernel Engine". For whatever reason in PSQL 11 SP3 it enabled both.  I went and unchecked the "Use Local MicroKernel Engine" and clicked on "Apply" then OK.  
Exited the PCC.
Loaded up Evo and the error was no longer present.
 
That fixed it for us, YMMV.
 
Kind regards,
 
Val