lngs.util.LngsException

There was a problem initializing the Lotus Notes thread. Make sure the Lotus dll/so/dylib directory is in your path. Also look at the Troubleshooting section of the Help file.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web42

  • There was a problem initializing the Lotus Notes thread. Make sure the Lotus dll/so/dylib directory is in your path. Also look at the Troubleshooting section of the Help file.
  • There was a problem initializing the Lotus Notes thread. Make sure the Lotus dll/so/dylib directory is in your path. Also look at the Troubleshooting section of the Help file.
  • via lngooglecalsync by jhill2016
    , 1 year ago
    There was a problem initializing the Lotus Notes thread. Make sure the Lotus dll/so/dylib directory is in your path. Also look at the Troubleshooting section of the Help file.
  • Stack trace

    • lngs.util.LngsException: There was a problem initializing the Lotus Notes thread. Make sure the Lotus dll/so/dylib directory is in your path. Also look at the Troubleshooting section of the Help file. at lngs.lotus.LotusNotesManager.getCalendarEntries(LotusNotesManager.java:256) at lngs.MainGUI.doSync(MainGUI.java:331) at lngs.MainGUI$SyncSwingWorker.doInBackground(MainGUI.java:495) at lngs.MainGUI$SyncSwingWorker.doInBackground(MainGUI.java:485) at javax.swing.SwingWorker$1.call(SwingWorker.java:288) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at javax.swing.SwingWorker.run(SwingWorker.java:327) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:761)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago