Hello.
I have had the same problem before (http://www.sggu.com/smf/index.php/topic,12335.msg55003.html#msg55003)
What I did was to configure an ODBC DSN with the security options and on the DAP I specified "dsn" as the server (without the "quotes") and the DSN name as the Database name (in the example below, it would be URS_DB).
My DSN file (on a Linux server where the DB Server is installed, on /etc/odbc.ini) looks like this:
[code]
[URS_DB]
Database = URS_DATABASE_NAME
Driver = SQL Server
Server = 10.0.0.1
Port = 1433
User = USER_NAME
TrustServerCertificate = Yes
[/code]
My DSN drivers file (/etc/odbcinst.ini) looks like this:
[code]
[SQL Server]
Description=ODBC Driver 18 SQL Server
Driver=/opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.0.so.1.1
UsageCount=1
[/code]
The packages that I installed on my Linux server where DB Server reside are:
- unixODBC.i686
- unixODBC.x86_64
- unixODBC-devel
- msodbcsql18
- mssql-tools18
The last two packages are from Microsoft's repository, so you might need to add them to your repository manager (assuming RHEL):
[code]
sudo curl https://packages.microsoft.com/config/rhel/7/prod.repo -o /etc/yum.repos.d/mssql-release.repo
[/code]
If your DB Server is on a Windows Operating System, you probably need to create a System DSN inside your ODBC Manager (create both in 32 and 64 bits to be sure).
Hope this helps