Home → Using LincDoc 3.1+ → Connecting to Other Software Systems → LincDoc Connector for Laserfiche: Troubleshooting

20.3. LincDoc Connector for Laserfiche: Troubleshooting

This topic describes steps to take when troubleshooting connectivity issues between LincDoc and Laserfiche. The basic goal to be accomplished is to get to a known state. 

Reconfiguring the Environment

Some of these steps may seem superfluous, and not all are absolutely necessary, but they should result in a correctly-running environment.

The general steps to use are as follows (in this order):

  1. Turn off all Laserfiche workflow tasks that are associated with any of the folders to which LincDoc may be attempting to save files.
  2. Confirm you can login to the Laserfiche server using the standard (thick) Laserfiche client software using the same username and password as used in the Connector configuration.
  3. Verify the same login used above can also save a new file into Laserfiche (while running the standard client).
  4. Verify the same login used above can also edit and save data in every template field (while running the standard client) to which LincDoc may be attempting to write data.
  5. Ensure you are logged in to the Laserfiche server as the Administrator.
  6. Stop the LincDoc Connector Windows service using the Service Configuration dialog box.
  7. Unregister the service using the Service Configuration dialog box.
  8. Close the Service Configuration dialog box.
  9. Open the Windows Task Manager application, and locate any java.exe or javaw.exe processes. If any are running, force them to stop.
  10. Uninstall all previous versions of Java.
  11. Re-install the 32-bit Java SE 6 (regardless of your server's operating system, the 32-bit version must be used because the Laserfiche DLLs are still 32-bit).
  12. Go to https://lincdoc.example.com/lwsa (substituting for the appropriate local LincDoc hostname/IP address); login as admin, download the SSL .exe installer (refer to the screenshots below); and run the file on the Laserfiche server.
  13. Verify that the .exe installer worked properly.
    1. Open the Windows Control Panel.
    2. Open the Java preferences.
    3. Click the Security tab.
    4. Select the Signer CA type, and click the System tab.
      You should see the web site certificate listed.
      In this screenshot below (taken from a Windows Server 2008 R2 system), it shows that lw3el0.lincware.com's SSL certificate was properly imported.
       
  14. Re-install the LincDoc Connector software.
  15. Open the Connector configuration dialog box; set up a handler first, and then a connector (remember the names of handlers and connectors are case sensitive); double-check all the settings are correct; and all test buttons report success.
  16. Verify that the enabled check box is selected (checked).
  17. Verify that you have saved all changes for the connector and handler you just configured.
  18. Register the connector as a Windows service by clicking the button.
  19. Start the service by clicking the Start button.
  20. Login to LincDoc.
  21. From the system button, click connectors.
  22. Choose the connector that was just configured. It should show an enabled status, and a last hit value in the last 30 seconds or so. A value of 0 or -1 indicates a problem, in that case try pressing the refresh button. It should look similar to this screen shot.
     

Viewing Log Files

System log files exist under c:\Program Files (x86)\LincWare\Connector\log. The service.log file captures messages when the connector service is running. You may want to open this file in notepad and look for the phrases exception, error, and permission denied.

Understanding SSL Issues

If you see the following error message in the service.log file, or in a warning dialog box:

Error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

it means you should stop the connector service if it is running, close the connector configuration dialog box, and use Windows Task Manager to ensure all java.exe and javaw.exe processes are stopped (by force, if necessary). Once all Java processes are completed, access the LWSA, download the SSL .exe installer, and run that file:

Restart the connector service and/or the connector configuration dialog box.

Similarly, if you press the test button:

And get the following warning:

It means you must follow the same steps noted above to run the .exe.

This page was: Helpful | Not Helpful
← 27.3. Creating an Email Template