Hi @dhruvssawant20,
You can take to troubleshoot and resolve this issue:
Check Connection String Format:
- Ensure that your connection string is correctly formatted. It should look something like this:
- jdbc:postgresql://<servername>:<port>/<database>
- Make sure there are no spaces or incorrect characters.
Verify Network Connectivity:
- Ensure that the server hosting the PostgreSQL database is reachable from the machine running Automation Anywhere A360. You can test this by pinging the server or using a tool like telnet to check if the port is open.
Database Credentials:
- Double-check that the username and password you are using are correct and have the necessary permissions to access the database.
Firewall and Security Groups:
- Ensure that any firewalls or security groups are configured to allow traffic on the PostgreSQL port (default is 5432).
JDBC Driver:
- Make sure that the JDBC driver for PostgreSQL is correctly installed and configured in Automation Anywhere A360. Sometimes, the error can occur if the driver is missing or not properly set up.
Automation Anywhere Configuration:
- Verify that all necessary configurations in Automation Anywhere A360 are correctly set up. This includes ensuring that the database connection settings are properly defined.
Sure, let me check on this. I have one question about the firewall, login, and JDBC driver—if these aren’t configured correctly, could they cause the process to fail outside of Automation Anywhere as well? When I connect directly to the database from my machine, it works, but it fails when running from Automation Anywhere.
Yes, incorrect configurations of the firewall, login credentials, and JDBC driver can cause the process to fail outside of Automation Anywhere as well.