Troubleshooting External Document Storage
The following information may help you troubleshoot issues you may have when integrating your LogicNets applications with external storage systems.
Document is not Closed Properly
When loading the document LogicNets will display an error page when the LogicNets System is started with a ESS-document/report-key that has been used previously but for which the session was not (properly) closed (using the Submit, Save, or Cancel button). This mechanism ensures that a document is not opened twice by the same user or by a different user at the same time.
If you click Cancel, LogicNets aborts loading the document and displays a page that allows you to close the browser tab or redirect the web browser to the ESS webpage.
When you click Reload, the system reloads the document from the ESS webpage and loads the document into the LogicNets application. The system closes other LogicNets sessions that had this document opened.
Connect Setup to the ESS Web Service Failed
If an error occurs during the connection to/setup up the ESS, the error is frequently caused by a misconfiguration of the ESS connection. They system displays the error screen below, and you should contact your system administrator for further information and help.
Common Error Messages
| Error Message | Description |
| Unknown connect error | The system can reach the host but the socket on the ESS is not opened for receiving a connection. |
| Cannot connect | The ESS hostname is not correctly configured if you used HTTPS. |
| Host not found | The ESS hostname is not correctly configured if you used HTTP. |
| Error initializing locations | The path to the HTTPS server certificate is not valid or the certificates in that configured path are not valid. |
| Unable to get server issuer certificate | The server certificate cannot be validated. Please check whether all certificates in the server certificate chain are saved in the configured certificate file. |
| Could not set client certificate key | The configured client certificate private key is corrupt or the private key does not belong to the configured client certificate. |
| Failed to set client certificate | The configured client certificate is corrupt. |
| HTTP Error 403.16 - Forbidden | Your client certificate is either not trusted or is invalid. |