This document outlines the steps to enable OneClick for eHealth (OneClickEH) debug logging on the OneClick client side.
Any supported version of OneClick for eHealth
To investigate problems on the Windows client where OneClick for eHealth is running, it is possible to enable OneClick client side debug logging by creating an empty OneClickEH.dbg file in the user’s “%APPDATA%\CA\OCE” directory of the client machine. Just create a plain text file and name it OneclickEH.dbg
- On Windows 2008, Windows 2012 and Windows 7: create the file in the user's "Application Data\CA" folder; e.g. C:\Users\<username>\AppData\Roaming\CA\OCE
- On Windows 2003: create the file in the user's "Application Data\CA" folder; e.g. C:\Documents and Settings\<username>\Application Data\CA
This will immediately start logging to the OneClickEH.log file in the same directory.
There is no need to restart the OneClick for eHealth on the client.
When problem being investigated is reproduced, collect OneClickEH.log file and provide it to Technical Support for investigation.
Remember to disable the debug when done to avoid the user's disk fill up. To disable debugging, just remove or rename OneClickEH.dbg file.
These steps are normally used together with those from Knowledge Base document “TEC515079 - How to enable OneClick for eHealth (OneClickEH) server side debug logging” in order to perform a complete troubleshooting of OneClick for eHealth problems.