Search results for query: *

Yes, I have re-installed the pervasive 9.5 client on this computer multiple times with the same result, Macola will run but locks out all other users. When I look at the servers open files, I can see the lock files but only for that one computer.

We are running Pervasive 9.5. I believe it is running remote but how can I be sure that it is not running locally. The problem is isolated to one computer. The user can move to another without experiencing the problem. Therefore I do not believe it is a server permission issue. The computer...

No.

Lck files created for a specific menu option are deleted once that option is closed and .lck files for syscomp.lck and syspass.lck once the user has logged out of Macola. When this workstation is used and creates these lck files this prevents Macola to support multi-users.

What would cause one user out of 20 in an 7.6.300c Pervasive.SQL Macola system to create and leave open '*.lck' files?

Issue resolved. It was a combination of changing the file type to 6.x on files creating a 30 error and modifing the registry setting HLM/SOFTWARE/Btrieve Technologies/Microkernal Worstation Engine/Version 6.15/Settings/Max Files to 256 and Max Handles to 256.

Issue unresolved...

Thank you, we are in Philadelphia, PA.

I came upon postings regarding renbtdll.exe and delbtdll.exe and have not run them because of possible impact on the 20+ other users that are running fine. I will try your solution once I can control system usage within the next week. Thank you for your input.

I believe I am getting closer to the root cause. The following message appears in the MKDEMSG.LOG. Version 6.15 appears to resides in the Macola70 default directory. Now, I need to trace why it is running this client and not the one installed on the workstation. **** Microkernel Database Engine...

I have the global setting set to 6. When we quit paying for support our Exact rep quit calling. I have not spoken with them for years. I can understand how it can interpret the file formats differences as Pervasive has downward compatibility support but I do not understand how it works for all...

no this effects all companies....don't worry I am confussed too.

I questioned the file access issue, permissions etc. but a process monitor showed that the files in question were being read. Thanks again for your assistance.

I believe (I could be wrong) it is a file version issue because I printed a Btrieve File Version Analysis Log and it showed that those files within the selected database/company that were version 7 were displaying the above error and those that were version 6 did not. BTW, the last error message...

FYI, Pervasive.SQL 9 Control Center works without any issues on this machine.

Yes, this is only happening on one machine. (Only machine that I have had to replace a hard drive).

Thank you for responding to my post. I am using Progression Explorer. The same drive mapping is being used as I am able to log in and select modules and options. However, the problem occurs when a module option it is being loaded. It appears that files with version 7 format create the problem...

I recently had to rebuild a XP workstation that had been running Progression 7.6.300c and Pervasive PSQL 9.5 for years. I have many users currently using this configuration without an issue. When I reinstalled Macola and the PSQL client I now receive the error "Error 030 on file x.btr - Message...