We had a server failure on our ACCPAC server and had to recover to a new machine.
The new server has Pervasive 8.6 with ACCPAC version 5.3A installed on it and we restored our ACCPAC folders.
Pervasive sees the data tables and ODBC sees and tests the data files just fine.
We edited the registry path to point to the new server and reconfigured the ODBC and pervasive databases on the workstations.
At that point ACCPAC would come up and ask for the login. They click OK and we get the big old.
"Cannot access database (error=49153). See Help for more information"
Well frankly help is useless on this error.
We have restarted the server and workstation to make sure pervasive got off on a good foot. And I have ensured that the users have full control through both the file share and file permissions to the ACCPAC folders and files.
Essentially the issue was that you not only need to configure the odbc and the pervasice db connection but you need to go into ACCPAC and run the database setup and configure the data sources there.
ACCPAC support said that in the newer versions this is not an issue as it just uses the odbc connection.
Thankfully the problem has been solved!
0
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Essentially the issue was that you not only need to configure the odbc and the pervasice db connection but you need to go into ACCPAC and run the database setup and configure the data sources there.
ACCPAC support said that in the newer versions this is not an issue as it just uses the odbc connection.
Thankfully the problem has been solved!