ppastor's account

Hi, I have attached the transaction. Thanks for your response.

Duo,

After several attempts, the call back is still failing. We followed the steps outlined and here is one of the results from testing with postman

"Server error occoured. Error - A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)".

We installed, SSMS on the DMZ server where notification is installed and we are able to connect to the database no problem. Port 1433 is open. 

Here is the last transaction:

{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_COMPLETE","sessionUser":"155cdc8d-0827-44aa-b6bb-c824d26af306","packageId":"5FUsBW5_TDz_dNCCDjoUZr0GF1c=","message":null,"documentId":null,"createdDate":"2023-06-15T20:20:38.986Z"} 
Reason(s): java.util.concurrent.TimeoutException 

Duo,

Good morning. The LF Server is installed inside their domain server LFAPP5, the notification service/server for OneSpan is installed on a DMZ server LFAPP3. Is there a port that needs to be open from both servers?

If needed be, we can also test installing the LF Web Application on the LFAPP3 (DMZ) server.

Thanks,

Paul

Duo,

Good morning. I copied the app_config xml to that location and re-tried the signing. It still did not update the document I have in Laserfiche.

Best,

Paul

Duo,

The WebAccessConfig.xml from the internal Web Server and copy it to the DMZ server location correct?

Best,

Paul