Troubleshooting Access Violation Event Code Errors: AVAA or AVAA0 in P6
(Doc ID 896644.1)
Last updated on JULY 24, 2019
Primavera P6 Enterprise Project Portfolio Management - Version 5.0 and later Primavera Contractor - Version 5.0 and later Primavera P6 Professional Project Management - Version 5.0 and later All Platforms
AVAA refers to the error Access Violation at Address followed by a hash value for the memory address being accessed. Access Violation errors are generated by the operating system and they happen when an application tries to access an area of memory that is not designated for that application's use.
If an application were able to write outside of its assigned storage area, it could overwrite another applications', or even Windows', instructions or data. Rather than allow this (which could result in a loss of data or in a more serious crash), Windows generates an error. "Access Violation" errors are the same things as "Invalid Page Faults" and "General Protection Faults" and all three are simply the symptoms of a computer 'crash'.
Access Violation errors are rarely an indication of a major problem with the software and the difficulty in tracing the source of Access Violation errors lies in the fact that they are generic. There isn't a common way to fix all Access Violation errors because there are so many different (and unpredictable) situations which can cause them.
This document will address some of the most common situations in which these exceptions occur and steps for troubleshooting these errors.
If after following this document AVAA0 exceptions still occur for you within the application:
Please submit a new Service Request (SR) using My Oracle Support (MOS) and reference this solution when creating the request.
Please include a detailed description of where the issue occurs, including any steps for duplication and if the occurrence can be duplicated on demand.