#dominoforever | Product 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

Fix the LS2J bug "Error loading USE or USELSX module.." It has been around forever!

When using LS2J often you will get the error "Error loading USE or USELSX module.."   at   UseLSX "*javacon" in LotusScript in the Designer.

There is no error!  ... but the Designer reports an error and you can not compile.

It is very annoying because you never know when it will happen and there is no clear fix for this. So please fix this error  

  • Guest
  • Aug 3 2018
  • Needs review
  • Attach files
  • Guest commented
    28 May 07:10am

    I come to you guys with important news about this annoying problem.

    HCL has just given to me a temporary trick to avoid the Javacon Error:

    I post here the link to the KB article. You can subscribe to it:


    The trick is: "open the code in Designer client without using Menu option in Tools (Show java debug console) "

    In few words if you start first client Notes but don't use menu "Tools" and after this you open Designer and your LS2J agent, you won't get the error! Then you can use "Tools" menu...

    Let me know if it works for you...

  • Guest commented
    30 Apr 02:14pm

    Pleaseeee...HCL solve this error!!!

    I suppose the *javacon error starts when you have many databases in the queue on client Domino Designer. My colleagues are much more organized than me and inside their Designer clients doesn't happen it!

  • Guest commented
    10 Mar 09:20am

    You can temporarily resolve the problem:

    1. Delete cache.ndk

    2. Compact Workspace

  • Guest commented
    5 Nov, 2020 09:52am

    Also upgrading to V11.0.1 fp1 .. Same error appearing randomly and to resolve I have to close Notes client/Designer/Admin and restart.

    Please correct it! Thank uoy

  • Guest commented
    9 Aug, 2019 09:17am

    Just to keep the stupid error alive. No change at all, after updating to V10.


    Start Java Debugger Console and open any Library in your application (LS2J / Java) ... then watch your libraries getting redcrossed *WTF*


    Open any Library in your application first (LS2J / Java) and then you are not able to start the Java Debugger Console *WTF²*