Skip to main content link. Accesskey S
  • HCL Logo
  • HCL Notes and Domino wiki
  • THIS WIKI IS READ-ONLY. Individual names altered for privacy purposes.
  • HCL Forums and Blogs
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • API Documentation
Search
Community Articles > Notes.ini File > Notes.inis C - D > Setting CSReportErrors=1 in notes.ini file can help isolate Notes Calendaring issues
  • Share Show Menu▼
  • Subscribe Show Menu▼

Recent articles by this author

Setting CSReportErrors=1 in notes.ini file can help isolate Notes Calendaring issues

Describes the use and benefits of setting CSReportErrors1 in the notes.ini file (applicable to both Domino Server and Notes Client)
Community articleSetting CSReportErrors=1 in notes.ini file can help isolate Notes Calendaring issues
Added by ~Samuel Umjipytheroni | Edited by ~Helga Preluzen on June 9, 2011 | Version 3
  • Actions Show Menu▼
expanded Abstract
collapsed Abstract
Describes the use and benefits of setting CSReportErrors=1 in the notes.ini file (applicable to both Domino Server and Notes Client)
Tags: troubleshooting, notes.ini, error logging, calendaring and scheduling
When analyzing problems related to Notes Calendar & Scheduling functionality, it is often helpful for IBM Support and/or Development to examine the console output from the Notes Client and/or Domino Server

Setting the following notes.ini environment variable will cause more detailed Calendaring & Scheduling error reporting to be written to the console log file.
CSReportErrors=1

The notes.ini file is located in the Notes/Domino program directory by default.  For a typical  Notes Client Windows installation, it is located in C:\Program Files\IBM\Lotus\Notes
 
it is good practice to restart your Notes client or Domino Server after adding this notes.ini setting.


To provide an example, I created a repeating appointment in my calendar.  This results in two documents getting created.  One is a child of the other.  I then wrote a LotusScript agent to delete the parent document.  This causes the repeating appointment to become unusable in subtle ways.
When I try to open an instance of the repeating appointment, I see the following console logging output.
[03FC:0002-0A1C] 06/09/2011 11:21:58.18 AM [C&S]> ERROR | Build V853_06022011 | csinit.cpp(1611) : Invalid or nonexistent parent document (0x3C8)
[03FC:0002-0A1C] 06/09/2011 11:21:58.18 AM [C&S]> ERROR | Build V853_06022011 | csinit.cpp(961) : Invalid or nonexistent parent document (0x3C8)
[03FC:0002-0A1C] 06/09/2011 11:21:58.18 AM [C&S]> ERROR | Build V853_06022011 | csinit.cpp(408) : Invalid or nonexistent parent document (0x3C8)
[03FC:0002-0A1C] 06/09/2011 11:21:58.18 AM [C&S]> ERROR | Build V853_06022011 | csinit.cpp(468) : Invalid or nonexistent parent document (0x3C8)

The error logging example above can help an IBM Developer pinpoint the problem much more quickly.
 
The error logging is written to your notes console log file.

By default, that file exists in the in the Notes Client or Domino Server data directory in a folder called IBM_TECHNICAL_SUPPORT.  
For example:
C:\Program Files\IBM\Lotus\Notes\Data\IBM_TECHNICAL_SUPPORT\console.txt
 
In addition to setting CSReportErrors=1, you should also set CONSOLE_LOG_ENABLED=1.  This will ensure that the logging output is written to the console.txt log file.



  • Actions Show Menu▼


expanded Attachments (0)
collapsed Attachments (0)
Edit the article to add or modify attachments.
expanded Versions (1)
collapsed Versions (1)
Version Comparison     
VersionDateChanged by              Summary of changes
This version (3)Jun 9, 2011, 6:12:40 PM~Helga Preluzen  
expanded Comments (0)
collapsed Comments (0)
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedAbout
  • HCL Software
  • HCL Digital Solutions community
  • HCL Software support
  • BlogsDigital Solutions blog
  • Community LinkHCL Software forums and blogs
  • About HCL Software
  • Privacy
  • Accessibility