HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
HCL support recommended "Server_Clock=2" or activity logging. I still would prefer "Server_Clock_User", because this is much easier to enable for quick investigation. Also you can use this an heavily used server in production, where "Server_Clock=2" will result in huge log-files.
I will ask HCL support...
Hi Thomas, which method would that be? Right now I have to troubleshoot an issue where only one specific user is facing a problem with one specific application. Other users with the same permission (ACL group) can use the functionality without any error. I cannot find the root cause with "Client_Clock", hence I would like to investigate at the server. "Server_Clock" is available, but it is complex to filter this log.
HCL Support can provide a method to troubleshoot server transactions for a specific user when needed.