Zurück
-
Titel
Essentials keeps freezing on Large migration jobs or scans- receiving "Not Responding" -
Beschreibung
Receiving "Not Responding" meanwhile a job is running at the top header, what does this mean? -
Ursache
The most probable cause of this issue is not having enough CPU / RAM resources available on the machine.
-
Lösung
You can allow more resources to flow through the tool by launching Essentials as an (1) Administrator (2) Navigating to the "Help" Tab (3) "Profile Manager" Tab (4) "Memory Management" and adjusting the tool allocated memory
Alternatively, Actions are still being performed / progressing in the background even though the the GUI of the tool states "Not Responding"
You can check the log files in the following locationC:\Users\USERACCOUNT\Essentials\.metadata and the various .bak_0.log [the most recent current running action uses .log <--- this is the one that'll be updated most frequently with the running job]