Getting error while trying to connect to Dataflux repostiory on Data management server

[india2016]

Hello Experts,

We have Created a dataflux repository on Dataflux data management studio and was successful in doing that. Have created a database type of repository using SAS Federation server.

Using the SAS Web Infrastructure Platform Data Servers created a separate database in postgres for the same as mentioned in documents(dfdmstudio).

Now copied the configuration of the data management studio server.rcf file to data management server server.rcf file as mentioned.But on the server getting an error. Attached the error screenshot for reference.

Please let us know if anyone has faced same issue and able to solve.

[VincentRejany]

Are you trying to connect to a DataFlux Repository hosted in SAS Web Infrastructure Platform Data Servers through SAS Federation Server?

[RacheLGomez123]

Resolution
Check for ODBC DSN corruption
Create a new ODBC DSN with the minimum connection options required to connect to the database and test connect using the sample applications like ODBC Test, example, etc.
Verify with the database administrator
If the specified Host Name / IP address and port number are correct.
If the user credentials are valid and/or correct.
If the database service is still listening on the specified port, including secondary login brokers that may not have started.
If there are errors in the database logs (e.g. OpenEdge databasename.lg file) when attempting to connect.
What the database version is that you connect to and verify if this version is supported by the driver.
If the database is stressed which could result in refused connection requests. The connection option Connection Retry Count may need to be set to a higher value than the default 0 when the cause is a stressed database.
Specifically for SQL Server, check the below database information to determine if additional connection options need to be set.
1) Is the connection attempt being made to a regular SQL Server instance or a named instance.
2) Is TCP/IP enabled?
Go to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for <SQL Server instance> and ensure TCP/IP is enabled.
3) Is Encryption enabled?
Go to SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for <SQL Server instance> and see if Force Encryption value is set to Yes.
If so, what protocols are allowed by the OS?

Verify with the network administrator
If the specified IP-address / Host name can be reached from the client machine where the driver is installed and that the hostname is pointing to the correct machine.
If there are client / server / network firewalls, packetshapers,.. which might block communication.
If the client and server machines are on different subnets and a router blocks communication.
Verify with the system administrator
If there are firewall / virus scanners active on the client or server side which block communication. Firewalls may come with the system (e.g. windows 2003, 2008,..) or may be included as part of anti-virus software, VPN software.
Clustered environments
Verify that all nodes or server hosts that the connection may be rerouted to are reachable by the client machine.

Regards,

Rachel Gomez