Access violations are today's generic error message. It can be difficult to track them down, but here's some 'generic' thoughts as you have not really said when exactly they occur.

1. If they occur during a printing process, then it could be the printer driver being used. Check the properties of the printer driver. PCL6 emulation is known to cause problems. If this is the version of the driver, it is best to install the older PCL5 driver, as there are no known problems surrounding it's use.

2. Check to see that the proper file-handling settings are in place:
- Opportunistic Locking should be OFF or Disabled on stations and Server, if NT, W2000 or XP.
- Novell Client32 should have either File Caching = OFF, or Opportunistic Locking = Disabled or Off. This depends on the version of Client32 installed on the station.
- All Adagio program and data folders, subfolders and files must be fully accessible and shared.
- User must have full access rights to these.

3. Data Integrity Check - is it error-free? In OE, AR, IC?

4. Is this the only station having the problem? If so, since they got a new system - are they still using the same NIC? Same printer? Did the User have full admin rights during the workstation setup or install of Adagio to the Server? Especially on XP, this is necessary as Adagio writes to the Local User's registries.

Hope something here helps, if not - we really need more specific information.

Regards

This can be puzzling, yes. AV's are in my opinion one of the most common, but hard to track issues.

Ok - based on your other posts, we know that Opplocks was not disabled and that Novell file caching was not set to OFF. Considering this, I will tell you that not having the proper Oplocks setting configured can and will corrupt datafiles. If caught in time though, perhaps your company has escaped this - I hope so.

There are 3 settings for the local workstation for Opportunistic Locking that must be set in the Registry. If you do not see any Oplocks keys at all in the registry settings, Opportunistic Locking is actually ENABLED (ON) by default.

All 3 must be set or you will continue to get errors.

The Options are under HKEY_LOCAL_MACHINE
System\CurrentControlSet\Services\LanmanServer\Parameters for EnableOplocks. Set Value to 0
System\CurrentControlSet\Services\LanmanWorkstation\Parameters for UseOpportunisticLocking. Set Value to 0
System\CurrentControlSet\Services\MRxSmb\Parameters for OplocksDisabled. Set Value to 1

Edit or Add Value name EXACTLY as described above, as a REG_DWORD data type.
A value of 1 is true.
A data value of 0 is false.

NOTE: Setting the above registries correctly AFTER getting errors will not 'fix' a situation that has already damaged the data. Because you could be still working with data that has become unstable, it is always good to check the integrity of the data with Adagio's DIC. If errors are found, try using the Rebuild option to see if they can be fixed.

Depending on the release date of Adagio that you are using though, the DIC may not pick up all errors caused by improper file caching configuration. If you are in doubt, you should contact your Dealer who is a Softrak Partner, who can work with us directly to try to resolve this once and for all.

Regards,