02-22-2017 08:49 AM
Hi All,
I've been trying to process psts through adding a case file source and evey time I get the following:
"Discovery scan failed", and the reason is "discovery failed as cpu stats could not be gathered"
I've checked each pst for errors by using scan.pst and fixed any errors. I've also opened them using outlook which works. I've even tried to process different psts and I get the same thing. Nothing has been changed with clearwell so unsure as to what to do next. Any ideas?
Thanks
02-22-2017 10:06 AM
02-23-2017 02:03 AM - edited 02-23-2017 02:04 AM
Hi Daly,
Thanks for the response. Unfortunately I've already tried that and it made no difference. I tried again this morning to check and still the same thing.
I should mention that we are using v7.1.5 with chf4 installed
Dan
02-23-2017 08:24 AM
Hello Dan,
Are you able to provide anything out of the log referenced in the technote? It may need a support case.
Daly
02-23-2017 09:36 AM
Hi Dayl,
Just gone through the logs and these are the two errors I see:
2017-02-23 09:46:38,083 WARN [resource.cpu.CpuEventManager] (pool-1-thread-1:) [#71000] Admin Services Error : Unable to get CPU statistics - No CPU information
2017-02-23 09:46:38,083 WARN [resource.cpu.CpuEventManager] (pool-1-thread-1:) [#71000] Admin Services Error : Too Many Errors - will reduce error report frequency. - No CPU information
Dan
02-25-2017 01:54 AM - edited 02-25-2017 01:54 AM
Hello Dan,
If that's all you're seeing and you've already tried that technote, would recommend creating a support case. We (support) would have to try piece together what is going on - to do that we'd need a logset.
Daly
02-27-2017 06:57 AM
Thanks for your response Daly. I'll get a suport case created.
Dan
02-28-2017 04:22 AM - edited 02-28-2017 04:24 AM
The resolution here was to set the following property and restart services:
Property: esa.cpumonitor.statsapproach
To the value: 0
This uses a different method to collect CPU stats.