Ignore the SQL component from ISO and manually configure the SQL Server details in Sage X3 Console and build the database from the one-off script.

Refer Sage X3 Console instruction here: https://online-help.sageerpx3.com/erp/12/public/configuration-console_console.html#CONSOLE/SOLMINI.htm

This part specifically:

Very often I am being barred from accessing the RDP of the SQL Server to install anything there (I get immediate pushback from DBA) so Manual configuration is the way.

I never need to install Sage X3 AdxAdmin and DBSQL component on SQL Server anymore, even on AWS RDS which is very nice.

It worked. Using the method you showed me, I was able to successfully connect the database and create a solution.
I am now one step further. This is my first installation of Sage X3

Unfortunately, I rejoiced too soon. Although the solution has been created, it has not yet been configured. The database configuration works, but an ODBC error occurs when configuring the application.

I am probably doing something wrong when creating the "sagex3" database. It did not exist and I therefore created it manually. This is what my odbc.ini currently looks like:

# A_D_O_N_I_X_Solution_ODBC_START : SAGEX3
[ODBC Data Sources]
SAGEX3 = MSSQL Server

[SAGEX3]
Description = MSSQL Server
Driver = /opt/microsoft/msodbcsql18/lib64/libmsodbcsql-18.3.so.3.1
Server = tcp:10.231.196.5,1433
Database = sagex3
Encrypt = yes
TrustServerCertificate = yes
TDS_Version = 7.4
# A_D_O_N_I_X_Solution_ODBC_END : SAGEX3

A connection using isql works.

From your Sage X3 Console, at Runtime section:

Encrypt = No

Trust Server Certificate = Yes.

Did you customize MS SQL Server to support certificate access? If so, which Sage X3 version and patch level?

chunheng said:

Did you customize MS SQL Server to support certificate access?

I assume not, is there a guide on how I can do this?
I have installed x3-12.0.35.iso from the ISO.

From SQL Server, I cannot comment.

From Sage X3 side:  ALERT: Using Microsoft SQL Server secure connections with Sage X3 

Is it also possible to establish the connection without a certificate?
This is my current configuration:



And this is a screenshot of a Sage employee performing an installation on a Windows server.

There are two additional parameters in the runtime: Connection Encryption and Trust Server Certificate.
These two parameters are not there at my configuration.

I wonder how it even works to add a new parameter in the console.

Does nobody really know that? I have to set two new parameters in the console that are not there yet, how does that work?
The two parameters exist in solutions.xml and I have entered the values there. Unfortunately, the console ignores the newly set parameters.

Hi Armin W. 
You need to be trained. You don't add parameters to the console, you click on "expert mode" button to have all the parameters appear. I'm sending an agenda today or tomorrow.

I have not seen parameters disappear from the console but that likely means they are not relevant to your configuration. So adding them back manually, I would expect them to be ignored. Unfortunately, I do not have the answer to how you move forward.

If you are a business partner, the support team can either assist via a support ticket, or engage the Sage expert services to consult with you. If you are a customer, please consult with your Sage partner on this implementation.

I have not seen parameters disappear from the console but that likely means they are not relevant to your configuration. So adding them back manually, I would expect them to be ignored. Unfortunately, I do not have the answer to how you move forward.

If you are a business partner, the support team can either assist via a support ticket, or engage the Sage expert services to consult with you. If you are a customer, please consult with your Sage partner on this implementation.

Phil Kennedy said:

I have not seen parameters disappear from the console but that likely means they are not relevant to your configuration.

Ok, I didn't know that, I had assumed that I needed these two parameters because of the error.