Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Accpac 5.4 Incorrect version of database 3

Status
Not open for further replies.
AlexJhb

AlexJhb

MIS
Dec 13, 2001
90
ZA
After upgrading to version 5.4 and using Pervasive 9.1 or 9.5. we get the following error when starting Accpac from the workstation."incorrect version of database".

Everything wWorks fine on the server and in TS mode.

SM SP3 was loaded but gave trouble. So removed it and tried SP2. Same. Now on Sp1. Can access database with Function Executer in PV utils.
 
Sort by date Sort by votes
WE have it working on 9.5 on a test server with the same configuration except that we are using ERP500. The client has ERP200. I do not expect that this should make a difference.

Is this a known issue that one needs 9.6 for Accpac 5.4?

Is the 9.6 a service pack upgrade?
 
Upvote 0 Downvote
Accpac 5.4 runs fine with P9.5, P9.6 is more for Vista compatibility. P9.6 is only available on CD from Accpac, you cannot download it from Pervasive.
The "incorrect version of database" error relates more to the Pervasive ODBC DSNs, so try recreating your DSNs on the server and workstations.
Is this Pervasive Server or Workgroup?
 
Upvote 0 Downvote
Hello Boet.
We have other 9.5's working, so this is confusing. We formatted the server last night and reloaded. Same problem. We have now installed a spare server at the client so they can work and that works fine, with 9.5 and all the same stuff as the other one. Intel server, so maybe we should look at the hardware?
We will try that DNS tip but they were new after formattinbg the server.
The server has PVSW Server and clients on the workstation. I try never to use Workgroup because I believe it has problems. If I can get 9.6 will try that as well.
Dankie.
 
Upvote 0 Downvote
The problems sounded like Pervasive Workgroup.
SM SP3 actually solves many problems, including some Pervasive issues and memory issues.
This sounds like a fun install, hope you find a solution.
 
Upvote 0 Downvote
SM SP3? We were told by Accpac local to avoid it because it caused so many problems. So have done so all along. Would you suggest we load it? Customer is on a loan server at the moment, so we can test it before we format again.
The reason we would format again is that the IT guys at client did it before but now we even have problems mapping a drive. So the server seems sick again. So we want to do it ourselves and leave things like Norton off this time.
 
Upvote 0 Downvote
SM SP3 is just fine, I highly recommend it. And if you don't like it, you can roll back to SP2.
 
Upvote 0 Downvote
We are running SP3 at many of our sites, no problems here.
I know some people have reported problems with Pervasive, but I have not seen any.
 
Upvote 0 Downvote
We have gone mad here with this problem.
Loan server working fine. We have formatted the client Intel server and loaded PV-SQL Server and client on workstation and cannot get it to work. Have tried all combinations. Now keep getting error 98.
PV seems to work fine by using Access to connect to data via ODBC.
We just cannot get PV working on this server in Client/Server mode. Using PV 9.5, not 9.52.
 
Upvote 0 Downvote
What data path are you using when you setup the database in PCC?
 
Upvote 0 Downvote
OK, made some progress.
Checked the UNC. Deleted everything and went through it step by step. Still can't connect but I think it is now permissions. Have the folder where Accpac is and c:\PVSW shared with full rights. but the test says it cannot create a file, open or all those things except if I point it to the test data in c:\PVSW.
Are there any other folders that need sharing or Registry keys that could cause this?
I loaded up another server in the office and that one works fine.
 
Upvote 0 Downvote
Hello Kleinboet,
Believe me or not, what Ettienne said about the problem being related to Pervasive ODBC DSNs is very much true. I had the same problem with an installation for a week and almost lost the client. We normally make the mistake of rushing through the steps because they are so deeply entrenched in our minds that we believe we cannot go wrong.

FWIW, I suggest you retrace your steps "very slowly" - delete all the ODBC DSNs on the workstations firstly and then on the Server lastly. Recreate the DSNs on the Server and make sure that the path you're using is in UNC on the Server then you will be alright.

Rgds,
SeisaT
 
Upvote 0 Downvote
What you say is very very true. We nearly lost this client as well. Lucky they have their own IT guy who is responsible for that side.

We proved to them by taking our own server and installing it as a loan in workgroup mode. We then proved that whatever he did on their server was causing a permissions problem. We solved this by joining the server to the domain. Can't explain why it was not on the domain to start with. As soon as we did this the problem went away.

So in summary, their server was duff and secondly our one worked even in workstation mode.

What you say about the DNS's is also true. We made progress by doing these over after Ettienne suggested this and proved it on our server. When we did the same on their server we hit the permissions problem. It would seem that there is extra security in PV9.x as everything worked with PV8.6 and Accpac 5.3. In fact, I recall 9.5 worked for a few days till SP3 was applied. After that it would not work any more.

I once had a site where if you loaded Accpac with the Web components, it smashed the registry. And that was a MS-SQL database. After that I always removed the Web components when loading. They are selected by default. So it is possible that this caused the whole problem again. Nobody can remember if that switch was on in the original load.

So the problem was solved, thanks to all your input as well. I really appreciate guys who take time out on these forums to help us helpless guys. YOU GUYS ARE COOL!
 
Upvote 0 Downvote
Servers that are not part of a domain generally cause a problem because the user's passwords are not synched, and other security issues.
 
Upvote 0 Downvote
Right. So we live and learn. Never ending process.

I am starting to understand that there must be a problem with Accpac and PV 9.5, because why is there a 9.6 only for Accpac and I believe Pastel.
 
Upvote 0 Downvote
P9.6 is for Vista compatability, this was pushed out before P10 became available.
P9.5 runs fine, I have many sites running on it. Accpac 5.4 runs faster on P9.5 than on P8.7 FWIW.
 
Upvote 0 Downvote
FWIW, I stand corrected, 9.6 is not required. I have some 9.5 sites, I've been going up to 9.6 lately just to "keep with the latest version".
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

ExtraLean
  • Locked
  • Question
ACCPAC VisionPoint 10 - Need workstation installer or another way to put on new machines
Replies
0
Views
288
ExtraLean
ExtraLean
NKOS13
  • Locked
  • Question
Password is incorrect
Replies
3
Views
262
NKOS13
NKOS13
vbdbcoder
  • Locked
  • Question
Macro editor can't be launched in Sage version 2023
Replies
0
Views
233
vbdbcoder
vbdbcoder
jsh8286
  • Locked
  • Question
Can Not Access Database 49153
Replies
1
Views
172
DjangMan
DjangMan
jsh8286
  • Locked
  • Question
Sage Accpac 300 V2021 - Canned Reports for Modules Printing in a Different Font
Replies
2
Views
158
jsh8286
jsh8286

Part and Inventory Search

Sponsor

Back
Top