This error is benign. There are a number of potential causes of it that all basically fall into the same category.
CDM collects information on startup, and periodically, about which processes are running in order to include the Top Memory consuming processes in the physical memory alarm.
CDM first gathers the list of processes then tries to locate and examine information about the executable file associated with the process for these alarms.
The error seen here can occur in certain cases such as:
- an itinerant process which was in the list when CDM scanned but which is not associated with a physical executable;
- a temporary process whose executable file may only exist for seconds and no longer exists when CDM goes to look for it;
- filename for some process running in the environment might be corrupted or has been read incorrectly and so we could not locate the file;
- some other reason why the executable process file could not be found when looking for the list of running processes
Ultimately, this error shouldn't impact monitoring and can be safely ignored.