| Solution ID: prim21717 |
| Troubleshooting AVAA Event Code errors |
| Status: Reviewed |
| Version(s): 3.5.1, 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0 |
| Problem: | Troubleshooting AVAA0 Event Code errors |
| Problem: | Troubleshooting AVAA Event Code errors |
| Problem: | Event Code: AVAA0-1352-3 Message: Access violation at address 005975EB in module ‘PM.exe’. Read of address 09599000 |
| Problem: | AVAAO errors |
| Cause: | AVAA Errors, or “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. |
| Fix: | See also, Access Violation errors when accessing the Activities view in Project Management AVAA errors have also been observed to be a symptom of corrupt layouts, particularly if they occur mostly while working with layouts, e.g.
A corrupt layout may also be the cause of AVAA errors when opening the software (for example, if the user has disabled the welcome screen and set the software up to open the last project – this will also open the most recently used layout). It is not possible to ‘fix’ a corrupt layout and if it is suspected that a layout has become corrupt, a new, clean layout should be created. Because corruption can potentially be copied across if a corrupt layout is saved to create a new layout, it is best to open a layout which is rarely or never used and save this as the new layout. For further information about how data can become corrupt, please see the following knowledgebase solution: |
| Fix: | Possible fixes for AVAA0 errors include: Client PC: 1. Closing down other programs or processes to free up resources for Project Manager. Click Ctrl, Alt + Delete and choose Task Manager, Performance. Compare Physical Total Memory to Available Memory. AVAA0 errors may occur when less than 25% of total memory is available.
2. Log completely out of Project Manager/Project Management and then log back in. Try running the process again. 3. Reboot the computer. Database: 1. Restore a previous clean Backup of the Project or Database to determine if the Error still occurs. The problem could be data integrity related. |
