This page 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. Some of these steps may seem superfluous, and all are not absolutely necessary, but should guarantee getting things running again. With that in mind, these are the steps to follow (in this order):
Turn off all Laserfiche workflow tasks that are associated with any of the folders that LincDoc may be attempting to save files to.
Confirm you can login to the Laserfiche server using the thick Laserfiche client software and same username and password as used in the Connector configuration.
Verify the same login used above can also save a new file into Laserfiche (while running the thick client).
Verify the same login used above can also edit and save data in every template field (while running the thick client) that LincDoc may be attempting to write data to.
Ensure you are logged in to the Laserfiche server as Administrator.
Stop the LincDoc Connector service.
Unregister the service from the Connector Configurator.
Close the Connector Configurator.
Open the Task Manager application, look for any java.exe or javaw.exe processes. Force them to stop.
Uninstall all previous versions of Java.
Re-install 32 bit Java SE 6 (regardless of your server OS, 32 bit must be used because the Laserfiche DLLs are still 32 bit).
Go to https://lincdoc.example.com/lwsa/ (substitute for the appropriate local LincDoc hostname/IP address), login as admin, then download the SSL .exe installer (see screenshots below); run it on the Laserfiche server.
Verify the .exe installer properly worked: open Windows control panel, and open the Java preferences. Go to the Security tab, select the Signer CA type, and System tab. You should see the web site certificate listed. In this screenshot (taken from a Windows Server 2008 R2 system), it shows that lw3el0.lincware.com's SSL certificate was properly imported.
Re-install the LincDoc Connector software.
Run the Connector Configurator, 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.
Ensure the enabled checkbox is checked in the configurator.
Ensure you have saved all changes for the connector and handler you just set up.
Register the connector as a Windows service by clicking the button.
Start the service by clicking the button.
Login to LincDoc. From the system icon choose connectors.
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.
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".
SSL issues
If you see this in service.log (see above), or in a warning dialog:
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 configurator window, and use Windows Task Manager to ensure all java.exe and javaw.exe processes are stopped (by force if necessary). Next, go in to LWSA, download the SSL .exe installer, and run that .exe:
Restart the connector service and/or the connector configurator. Similarly, if you press the test button:
And you get this warning:
It means you must follow the same steps noted above to run the .exe.