Frequently Asked Question

The Plato config process allows database connection strings to be entered into config.ini. When config.exe runs, it tests the connections and then encrypts them so casual browsing does not allow access to database credentials.

If you encounter errors with database connection strings entered into config.ini, you can validate the connections outside config.exe. This helps to determine whether there is a database connection issue or a Plato config.exe issue.

If you encounter error messages indicating that an ODBC driver or DSN does not exist but you can see it in ODBC Data Source Administrator: check whether you are running an x86 (32-bit) or x64 Plato application, since Windows apps can only use matching drivers or other resources. Depending on your version of Windows you may need to install additional 32-bit drivers or other resources. 

If it's not a driver or resource issue, an easy way to test connections is via Windows PowerShell.

Running PowerShell

If you are running an x86 app and want to run 32-bit PowerShell for a detailed test, in newer versions of Windows you can select PowerShell x86 via Windows Start:

or you can start it from the cmd.exe Command Prompt:

%SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

Validate an ODBC connection using PowerShell

Run a PowerShell script along these lines:

$conn = New-Object System.Data.Odbc.OdbcConnection("Paste connectstring here")
$conn.open()
$conn.close()

If connection succeeds, no errors will be displayed and your connection string can be expected to work in config.ini. If connection does not succeed, useful error messages are displayed. e.g.

In this case, access to the database server is denied.

Basically if your proposed connectstring cannot connect in PowerShell, it can't be expected to work in config.exe either. Once the issue is resolved you can paste your successful connectstring into config.ini and it should work. 

To Test an ODBC DSN:

Sometimes connections will use a special ODBC DSN (Data Source Name) with inbuilt credentials. You can test these the same way using PowerShell, with a connection string that usually includes DSN=. If connection fails, you can expect to see something like:

If you cannot connect using your DSN in PowerShell, it can't be expected to work in config.exe either. After the issue is resolved you can paste your connectstring into config.ini and it should work.

If you encounter a DSN or connection string that works in PowerShell, but config.exe on the same machine throws errors after the exact connectstring is pasted into config.ini, please raise a support ticket and Plato will investigate. Plato will not charge and will quickly provide a remedy if there is a Plato bug or issue, rather than a connection fault.