Managment console for Unix: cannot profile on the mcu-gets an error saying could not start tasks for action: profile
RESOLUTION 1:
1 - Backup the MCU data and save it with the date and time
For instructions please refer to https://support.quest.com/kb/95993
The backup is both as a precaution and in order to further investigate why this happened.
2 - Remove the host from MCU
3 - Then add the host back in and try to profile
In situations we have seen this resolve the issue and the host can now successfully be profiled.
4 - If you need to find out root cause, save another copy of the MCU data with date and time and open up a Service Request with Techinal Support and attach the MCU data before and after from step 1 and 4.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center