Usability - Productivity - Business - The web - Singapore & Twins

LotusScript LSI_INFO potentially harmful on (64Bit) Domino

There is a handy, but undocumented LotusScript function LSI_INFO that can lead to crashes of the Domino server, especially on 64Bit systems. Since the function never had been documented, a fix for that can't be expected any time soon (or at all). Unfortunately that function is used in OpenLog an incredibly useful logging application written by Julian Robichaux. Here is how to fix this:
  1. Make sure you use the latest release (you also can use the code contained in TaskJam, it is extended to be able to log XPages)
  2. Edit the OpenLogFunctions script library and add into the initialize statement: NoLSIStackTrace = True
  3. Make sure all applications that use OpenLog get the updates library (if you copied it with intact inheritance a "load design" will do)
As usual YMMV

Posted by on 24 April 2012 | Comments (7) | categories: Show-N-Tell Thursday


  1. posted by Tommy Valand on Wednesday 25 April 2012 AD:
    You forgot to mention what "NoLSIStackTrace = True" does. What are the pros and cons of this?

    I've been using OpenLog on servers for 4-5 years without any problems. Does this setting(?) decrease the amount of information logged?
  2. posted by Stephan H. Wissel on Wednesday 25 April 2012 AD:
    @Tom: NoLSIStackTrace = True instructs OpenLog not to use LSI_Info and thus not crash the server. Problem seems to be confined to 64Bit servers. What it changes in the behavior of OpenLog? I haven't checked - look at the source, it is open Emoticon biggrin.gif
  3. posted by Stephan H. Wissel on Thursday 26 April 2012 AD:
    There is, given your skills, the distinct possibility that your Error statements are never called, or at least seldom enough so it isn't an issue for you.
    I suspect the frequency and interval plays a significant role.
  4. posted by Tommy Valand on Thursday 26 April 2012 AD:
    I also have it running on 64bit Domino servers.. I guess I'll have to take a look at it if the servers crash due to LSI :P
  5. posted by Tommy Valand on Friday 27 April 2012 AD:
    That's probably correct. When an app is under development/just has been put into production, there might be an increase in error documents for a few days. After that, errors seldom occurs in LS code.

    Most of the errors in the logs stem from strange browser errors that I sometimes can track down, and sometimes not. :)
  6. posted by Clark on Friday 18 May 2012 AD:
    I hate 64 bit.....
  7. posted by Dominic on Wednesday 30 May 2012 AD:
    Unfortunately, I have been able to reliably reproduce the server crash on a 32 bit instance of Windows Server 2003.

    On one particular agent, where the Openlog uses LSI_Info the server WILL crash, where it does not the code runs to completion and all is fine.

    This is the first time I have found this problem, after using OpenLog for many years.