At folder import time the console runs a batch file when then runs a SQL script. This script is responsible for creating a database user called SEED, which correlates to a SCHEMA called SEED. My guess is that the script never created either, and thus you are unable to login with SEED.

Within the console you can set the account used to interact with SQL. You should specify the sa or equivalent account there. At the same time, if the problem continues to happen you can run a SQL profiler trace to capture the real database error. Alternatively, if you press F4 inside the console you can see the global trace log for the console and it will give additional details as to the error.

Hope this helps.

Bob

Hi,

I hope the problem with special characters for SQL server user Password (i.e. sa user). while creating a database through console every time X3 will check the SQL sa user account login credentials.

Regards,

Siva

Hi,

I hope the problem with special characters for SQL server user Password (i.e. sa user). while creating a database through console every time X3 will check the SQL sa user account login credentials.

Regards,

Siva

Thank you for the inputs.  The program did create many of the tables in the system.  The problem seems to just pop up on a few of the areas in the program.  For example:

Everything seemed to be working fine (no errors) up to this point.  One thing I noticed is that there is no Native Client 11.0 setup.  It is a 2008 SQL server and it uses Native Client 10.0.  Not sure if this is relevant or not.  The SEED user was created in the process.  

10/12/2014 12:23:57 PM : INFO  - 120 tables loaded - 10% - AOBJSEL.dat

10/12/2014 12:34:13 PM : INFO  - 240 tables loaded - 20% - AYTADVPAR.dat

10/12/2014 12:37:41 PM : WARN  - Warning ! Following table could not be loaded into database : BPSHISUPLN. (LibAdmAdonix.RunValFilImpFldNT)

10/12/2014 12:37:41 PM : INFO  - Erreur no 76

[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'SEED'. : Erreur SQL Server

10/12/2014 12:40:26 PM : INFO  - 360 tables loaded - 30% - CFGLNK.dat

10/12/2014 12:46:05 PM : INFO  - 480 tables loaded - 40% - EFASMTC.dat

10/12/2014 12:52:17 PM : INFO  - 600 tables loaded - 50% - GJOURNAL.dat

It goes on with many successful changes and then comes up with the following:

10/12/2014 1:31:05 PM : INFO  - Checking user script file c:\Sage\SAGEX3V7\X3V7\folders\SEED\init_console.cmd on server. (LibAdmAdonix.CreateFolderDef)

10/12/2014 1:31:05 PM : INFO  - Launching database cleaning script file. (LibAdmAdonix.CreateFolderDef)

10/12/2014 1:31:06 PM : INFO  - Initializing the supervisor (LibAdmAdonix.CreateFolderDef)

10/12/2014 1:31:08 PM : WARN  - Error Connecting for pgm processes (LibAdmAdonix.CreateFolderDef)

10/12/2014 1:31:08 PM : WARN  - Error when initializing the Supervisor. (LibAdmAdonix.CreateFolderDef)

10/12/2014 1:31:08 PM : WARN  - ERR_CANT_CONNECT

can't get key [message.error.cant.connect] in the not loaded resource [com.adonix.x3.comm.client.adonix.CAdonix]. Cause:[Bundle com.adonix.x3.comm.client.adonix.CAdonix not found for locale en_US by classloader Console]. [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'X3'. : ini_com:Erreur SQL Server!(2)

(LibAdmAdonix.CreateFolderDef)

10/12/2014 1:31:08 PM : INFO  - Application setup finished.

10/12/2014 1:31:08 PM : INFO  - [End]

10/12/2014 1:35:02 PM : INFO  - Loading solution...