You are viewing limited content. For full access, please sign in.

Question

Question

The verification is still pending. Please check back later

Laserfiche Cloud
Updated November 15, 2023
asked on November 15, 2023

Any ideas as to why we cannot verify a connection to a DB in the Cloud data source menu?

 

Everything seems to be there.  Maybe a dozen or so tables in the DB.  In the log files on the server with the Remote Worker it seems to connect:

[Test HR, LF] Sending POST request to /bpm/api/_wms/1.0/deq.
[Test HR, LF] Response code: OK. Requires reset: False.
[Test HR, LF] 0 work items retrieved.

Not sure what else is missing or where to go for further information.

 

Thanks,

Chris

0 0

Replies

replied on November 15, 2023

Hi Chris,

The part of the log you linked is part of the standard communication the Process Automation Worker is doing with Cloud to check if there is any work to do, unrelated to the Cloud Database Verification.

If there is more in the trace file, you can scroll down or search for 'Error' you might be able to find the specific problem that is causing the verification to fail. You can also check the Event Viewer and go to Application -> Laserfiche -> ProcessAutomation -> LocalAgent to look through the errors or warnings listed there. 

We're looking into making the troubleshooting experience easier in a future release.

-Kevin

1 0
replied on November 15, 2023

Thanks Kevin,

This is the only error we get in the logs:

 

Message: 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: TCP Provider, error: 0 - The remote computer refused the network connection.)
        The remote computer refused the network connection

 

I have verified the instance and I have made sure I can log into the Management Studio using the username and password.

0 0
replied on November 15, 2023

Hey Chris,

Often this error comes when either the Process Automation Worker is on a different machine to the machine with the SQL Server and the machines are not set up to communicate, or if there is an issue with the port. 

If they are different machines, you can check it by trying to log in using the Management Studio from the machine with the worker. 

If there is no specific port specified when logging in with the management studio, make sure that there is no port specified in the Data Source as well (or if there is a specific port, making sure it is specified in the data source).

 

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...