When trying to use an ADPW task or attempting to create a new ADPW task it takes minutes and then it fails, on QMM console machine in the Event Viewer the following error is being logged:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Time: 8:42:17 AM
Faulting application ADPW.exe, version 22.214.171.124, faulting module AEgzip.dll, version 126.96.36.199, fault address 0x0000b8c5.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 41 44 50 ure ADP
0018: 57 2e 65 78 65 20 37 2e W.exe 7.
0020: 30 2e 30 2e 32 39 20 69 0.0.29 i
0028: 6e 20 41 45 67 7a 69 70 n AEgzip
0030: 2e 64 6c 6c 20 31 2e 30 .dll 1.0
0038: 2e 30 2e 37 20 61 74 20 .0.7 at
0040: 6f 66 66 73 65 74 20 30 offset 0
0048: 30 30 30 62 38 63 35 000b8c5
Attempts to reinstall the tool or to re-register the mentioned DLL (and absolutely all DLL's) didn't help.
In this particular case it was noticed that QMM contained too many History entries and when attempting to open and view them the QMM GUI became unresponsive. Since such History entries do not have any particular value and cannot be used in future decision was made to delete all the History entries from ADAM Project.
After this was done all tasks started to work as expected and new ADPW tasks could be created without any issues.
IMPORTAT: The information in this article applies to older unsupported versions of QMM only.
Start QMM and delete all History entries from QMM (the History node is visible in the left pane at the bottom in QMM).
It might take minutes before QMM will display the history entries and it might take some time when deleting the entries, this can be done only by selecting and deleting the entries one by one.
If unable to remove the entries please contact Quest Technical Support and request assistance by cleaning up the ADAM DB from History entries.
Please backup ADAM before calling support or opening a ticket.
It has been determined that high amount of History entries in QMM is slowing down the tool and causing unpredictable issues with migration and product usage, especially when using older QMM versions. This is not fully QMM related but also partially happens because of ADAM Project becoming big and unresponsive.
Quest development is aware of this issue and is considerign to implement an option in future QMM releases which will allow to decide whether the history should be saved (preserved) or not. An official Enhancement Request has been created.