Dear William
Access violations can occur for several reasons, however, in order to be able to determine a likely cause, first we would need addtional information:
- Do the AV's seem to occur only when performing a specific operation? If so, please describe in detail exactly at what point the AV occurs within Ledger (i.e. after clicking OK during entry of a transaction in the 'Edit Batch XX entry XX, line XX' detail entry screen OR after clicking 'Post' on the 'Edit Batches' screen etc.).
- Are there any other users in Adagio Ledger at the same time you are?
- Are there any users in any other module (in the same dataset) at the same time you are doing something in Ledger?
- What type of environment is Ledger installed on? (i.e. Adagio installed standalone, or on a Network Server? What NOS is being used? If Novell, what version of Novell Client is being run on the workstation etc.).
- Does any other workstation have the same problem?
- Can you duplicate this in ALWIN\Samdata?
Following is information on reported issues of Access Violations, known causes and suggestions on other possible problem areas:
Access Violation errors can occur when trying to print reports to printer or when doing a print preview, however, they are not limited to the print process. They can pop up during any process and will usually give information as to the file that is the problem.
KNOWN (verified) CAUSES & RESOLUTIONS:
1. User having problem may not have had sufficient rights (ADMIN) during the installation of program and/or ALLWKST.
a) Must grant FULL ADMIN rights to this USER, then redo the installation. (You can then change rights back afterwards, if required.)
2. Users having problem may not have full ACCESS and/or rights to the associated Adagio folders and/or files.
For example,
The Network Administrator said that the User had all rights given to the Softrak directory but when the Dealer got there, this User did not have "S"upervisor rights or "A"ccess control checked off. Once the User was given "Access control" they were able to complete an invoice batch and post it. This User was given Supervisor rights as well, but this is not necessary after the main install or ALLWKST.exe has been performed.
3. Printer defined in File | Options (either Windows? Default, or Specific) is not currently connected to the system.
a) Reconnect the printer and try again.
4. O/S is Windows XP Home Edition.
a) Apparently, with XP HE, you can right-click on a program icon, and select to run it in Windows 95/98/NT or 2000 mode. In this case, they chose W2000 mode, and this seemed to make the Access Violations go away.
5. Print Boss is being used.
a) At time of writing, we are aware of what causes the problem and R&D is working on a fix that will get implemented in a future release. Contact Wellspring for a ptf for this ? has to do with how many paper sizes are in PB ? more defined than Adagio has.
OTHER REPORTED AV?s (but not verified with known resolutions):
1. On a Novell network, Novell client being used is not up to date, or is a version that is known to cause problems.
Novell 3.12 and higher should be installed on all stations using W95/W98.
Novell 4.72+* should be installed for all stations using NTWS or W2K as their local O/S.
*NOTE There were recent issues reported when using V4.83.0.0 of Novell Client 32.
2. Only station having issues was using Win95 as their O/S and had intermittent ?Access Violations? such as:
?Access Violation 0000. Read of address FFFF.?
This occurred in a variety of processes, including Editing Banks and printing checks from Adagio Payables.
Instances where the Access violation pointed to the executable program file
(eg. ?Access Violation in xxWIN.exe, read of address ?..?).
Solutions to this range from re-installing the Adagio program with FULL ADMIN rights for the User logged onto the network and/or local station (after renaming the program folder), to removing the registry entries on the station having the problem, then re-installing the program as explained, and/or re-doing the ALLWKST on the problem station ? again logged on as the User with FULL ADMIN rights.
Hope these suggestions help. In the meantime, we are looking into the specific addresses you gave us. We will update you with our findings, if we are able to pinpoint a problem area.
Regards,