search : system probes

select a category, or use search below
(searches all categories and all time range)

displaying top 100 results

Comment on System Probe Failing because of csrftoken by External U.
CF System Probe: unable to set the file overwrite check option to false.
First time after editing system probe, it displays "there was a problem running the probe" when the probe is run. After that it displays the appropriate message.
[regression] System Probe not working. HTTP request returned non-200 status code:Connection Failure
System Probe Failing because of csrftoken
Comment on First time after editing system probe, it displays "there was a problem running the probe" when the probe is run. After that it displays the appropriate message. by S P.
Comment on CF System Probe: unable to set the file overwrite check option to false. by CFwatson U.
Comment on CF System Probe: unable to set the file overwrite check option to false. by External U.
Comment on [regression] System Probe not working. HTTP request returned non-200 status code:Connection Failure by External U.
Comment on [regression] System Probe not working. HTTP request returned non-200 status code:Connection Failure by CFwatson U.
Bug 80529:When I create a system probe and rename it, a new probe entry is created in neo-cron
Comment on First time after editing system probe, it displays "there was a problem running the probe" when the probe is run. After that it displays the appropriate message. by Uday O.
Exception in the CF admin, when editing System Probe.
(memory,requests data) portlet.log - Portlet logs probes.log -System probes logs that help in evaluating the status of your ColdFusion application security.log - Security related logs update.log - Logs that pccur while applying the updates webservice.log - Webservice invoke call logs websocket.log -Websocket call logs
in the Debugging and Logging section of the CF Admin. (One might say the same of the system probes and license scanner.) Similarly, the settings for enabling CFStat and Windows Perfmon don't make sense being on the "Debug Output Settings" page. If nothing else, they should be made more clearly distinct from
capable. This is a serious issue that is very restrictive in Microsoft environments. The issue is not confined to CFHTTP but also any CF feature making use of the HTTP requests. A limited list of features impacted by the lack of NTLM / digest support. * cfhttp * Scheduled Tasks * System
/13/10" "18:11:53" "java.lang.String cannot be cast to java.lang.Boolean" "Information" "05/13/10" "18:11:53" "Restoring security settings" "Information" "05/13/10" "18:11:53" "Restoring Server Monitor settings" "Information" "05/13/10" "18:11:53" "Restoring System