SQL Server 2017
Windows Server 2016 Datacenter
Getting the error below when trying to configure the application for the first time after installation.
Installed Sage X3 V12
We have 2 servers a database server and app server
Configured Database server on console without issue
When we are now configuring the application server we are getting the error looks like not able to create SQL user.
Some of the lines on the trace are
5/01/2020 9:03:57 PM : INFO - Database user X3 and roles are not available. (LibAdm.RunVerifSchemaBaseSqlServer)
5/01/2020 9:03:57 PM : INFO - Database schema check failed. (LibAdm.RunVerifSchemaBaseSqlServer)
5/01/2020 9:04:13 PM : INFO - Database user X3 and roles are not available. (LibAdm.RunVerifSchemaBaseSqlServer)
5/01/2020 9:04:13 PM : INFO - Database schema check failed. (LibAdm.RunVerifSchemaBaseSqlServer)
5/01/2020 9:04:13 PM : ERROR - Error while creating user. Please check file F:\Sage\X3DW\folders\X3\FILPLAT\x3ria_CrUsr.tra on server. (LibAdm.RunCreateUserSqlMainNT)
5/01/2020 9:04:13 PM : INFO - Application configuration failed : main runtime installation status will be reset To 'idle'. (LibAdm. RollbackMain)
5/01/2020 9:04:23 PM : FATAL - Configuration aborted5/01/2020 9:04:23 PM : FATAL - ERR_USER_CREATION
which exact X3 V12 versions are using for the installation? 12.0.19?Where is the management console installed? On the DB-Server or the APP-Server?If it is installed on the APP-Server:
Are you able to connect via MSSQL-Management Studio from the App-Server to the DB-server with the credentials from the console?
We have checked the step given, still we are facing same error. It would be appreciable if you can provide any other solution
Is there any update on above query which i have raised?
Hello,Can you check if you have a adcraps*_X3.sql file in your runtime\tmp folder? It should have a bunch of "create login" and "create role" instructions. Try to execute this script directly in SSMS. Also, make sure the sa user password is correct in the console configuration.Regards,
Thank you for the response.
The solution given is not working for us but we have resolved the issue and cause was ODBC driver version and the collation.