error=2 cannot access database

[lanmaninsi]

I have just finished installing Accpac version 5.2 (upgrade), now I cannot access my databse. I get Accapc error=2 cannot acces database when i try to open the company. I have setup my pervasive engine link to this database on my server and it also shows on the client end as being linked. Any ideas what is the problem??? My Accpac worked fine before this upgrade... thanks Accpac.
L
I have the database on a Win 2000 server and my computer runs Win98, if that helps.....thx in advance

 

[zemp]

What database engine are you running? If Pervasive then 5.2 requires 2000i SP4 or higher.

Take Care,

zemp

"Show me someone with both feet on the ground and I will show you someone who can't put their pants on."

 

[lanmaninsi]

Yes, i am using pervasive sp4. I was using sp3 untill I upgraded my Accpac but then as you said; it required SP4, so I installed that. Now I cannot connect to the database and receive a error=2 pervasive error when I try to open a company that was accesible before.

 

[zemp]

Do you have all the lateset 5.2 ptf's? I am assuming that you do but just making sure.

Maybe installing SP4 changed the way your database was setup. Check to ensure that all users exist and have correct permiossions, etc., etc..

Take Care,

zemp

"Show me someone with both feet on the ground and I will show you someone who can't put their pants on."

 

[africanernie]

Hi,

MicroKernel Database Engine Status Codes

2: The application encountered an I/O error
This status code typically indicates a corrupt file, an error while reading from or writing to the disk. One of the following has occurred:

The file is damaged, and you must recover it. Refer to the Pervasive.SQL Advanced Operations Guide for more information on recovering files.
In NetWare, at least one MicroKernel data file is flagged as Shareable. All MicroKernel data files should be flagged as Non-Shareable. The MicroKernel is the only user that accesses the files (on behalf of many users). As the only user, the MicroKernel can control the integrity of the data files. If you flag your MicroKernel data files as Shareable, data corruption can occur.
For pre-v6.0 data files, there is a large pre-image file inside a transaction, and there is not enough disk space for a write to the pre-image file.
For pre-v6.0 data files, there is one pre-image file for multiple data files. For example, if you name the data files CUSTOMER.ONE and CUSTOMER.TWO, both files have pre-image files named CUSTOMER.PRE.
For pre-v6.0 data files that are larger than 768 MB, there is a conflict among locking mechanisms. The file has not been corrupted. Your application can retry the operation until the conflict is resolved (when the competing application releases the lock your application requires).
A pre-v6.0 Btrieve engine attempted to open a v6.x or later MicroKernel file.
With Btrieve for Windows NT Server Edition v6.15.445, 32 bit Windows application may return Status 2 or "MKDE Terminated with Service Specific Error 0" after running an application for an extended period of time.
There was a conflict with the assignment of token handles and permissions. You may receive status 2 or corruption on very busy SMP boxes, when a user is deleted from the Btrieve Monitor and the user immediately reopens the files. There is an FTF for Pervasive.SQL v.7.0 Windows NT and Service Pack 3 for Pervasive.SQL 2000i Windows NT.

Hope that helps a bit,.

Regards

e