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!

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

ACCPAC 4.2 For Windows Error messages 1

Status
Not open for further replies.

Lacroix

MIS
Aug 1, 2001
7
SG
1. I was trying to clear transaction history under PO module, Periodic Processing and encountered the following error msg :Operation = DELETE, error=2

2. Thereafter, we tried to run a Data Integrity Check and encountered another error msg : Operation = GET-GE, error=2

we were adviced by our vendor to re-boot our server, after which the above operations would run smoothly. Our server is running on Novell Netware 5.1 and our ACCPAC system was just recently upgraded from version 4.1 to 4.2. Are all these problems encountered related to our server or our ACCPAC? Please advise. Thank you very much!!! ^_^
 
Error = 2 tends to mean that your indexes are corrupted. A dbCopy may help to re-build the file - but it might get stuck on the corrupted file.

Depending on your version of Pervasive you have different options on re-building the corrupted file(s).

The error may not be related to the conversion - it was likely sitting in the table already and when you tried to access the data in that part of the table the bad index was exposed.

Let us know if you need more info.

DjangMan
 
Hi DjangMan!

Thanks for the insight! I've forgotten to add in another point. Every time these errors occur, we would reboot the server where the ACCPAC data is residing on. Thereafter we tried to run the operations again and everything went well. Why would rebooting the server clear up these errors? Thank you very much, once again.

Lacroix
 
I don't have an answer as to why re-booting the server has worked in the past. :-( It may be caching related but either way it sounds like the table is corrupted.

Try a dbDump and you'll be able to see what table ACCPAC 'chokes' on. Then you can re-build that one table and try the dbDump again, in case more than one table is corrupted.

DjangMan
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top