What is an Access Violation?
An Access Violation is an unhandled error.
The error means some program code tried to act on memory to which it has no permission, did not allocate or that cannot be addressed.
‘Unhandled’ means the error arises from a state that the code writers did not expect or believed to have been impossible.
Access violations are rare and usually specific to an individual computer, its specific configuration and state. AV errors usually follow some other error.
When they do, the preceding error is significant.
Actions, operations and the state of the PC and memory prior to the AV error are always significant in diagnosing the cause.
The AV error message comes from a low level part of the operating system. The effect is like having your neighborhood cordoned off because a neighbor noticed smoke. (Access Violations are not as bad as those "need to exit" errors. They are like having your neighborhood condemned, bombed, and paved over.)
After an AV, there is no easy way to know the extent of damage.
At a minimum, the program involved is in an unstable state -- along with its supporting programs -which could include large swaths of other applications, including the OS.
After an Access Violation Error: Try to shut down what programs you can and reboot - or log-off/close the remote session.
When started up again, or in a new session:
Try to repeat the process that caused the AV. It might or might not happen.
Keep notes of actions, mouse clicks, data selected, and exact wording or screen captures of any error messages.
If the Access violation is repeatable, notify Datacolor
support. Have your notes ready along with names and version numbers of your Windows OS and Datacolor products.
Datacolor support and development will need to reproduce the error to create a fix or protection against its recurrence. Datacolor may request a copy of your database or ask to use a secure remote-control connection to your PC to investigate.
If you cannot repeat the AV, the cause may be in other running processes
Corrupt or incompatible Windows modules, add-ons or shared components
Insufficient free hard disk capacity or file corruption
Too little installed RAM
Insufficient virtual memory allocated for large queries or amounts of data in memory
Anti-virus, firewall, add-on memory managers or anti-malware utilities may be preventing access or proper product installation.
Successfully locating these potential causes can require commitment to monitoring and cooperation/assistance from IT resources familiar with local policies and configurations —especially for network or application server (remote terminal) deployments.