First Time Setup: Certifier unable to connect to database

[eve0021]

Hi, this is the first time I'm setting up a Flyff Server (offline only) and I've been dealing with something for a few hours now.
So I downloaded the source (google drive file only, not downloading anything from git for now) released by Ketchup and followed the guide they suggested in the post.

I followed the guide down to the T but hit a wall when I finally started to run the Certifier. I checked the logs and found this error:

SQLSTATE:28000 error:[Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'account'.

knowing its an authentication issue, I had to double check my settings for passwords and usernames alike but all is clear. So I decided to check SQL's log and found the same thing:

Date        21/01/2023 7:41:30 pm
Log        SQL Server (Current - 21/01/2023 3:58:00 pm)
Source        Logon

Message
Login failed for user 'account'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

Now I'm wondering, where is this issue coming from?
I peeked at the source and found there were resource files as well that points to "account" as username but I always assume the release version would only follow the resource in the same directory (*.ini) right? So where in the tutorial did I mess up or looked passed? or is there something else I should've ticked in the setup? I've been going back and fort in the tutorial and is still not able to get it running.

PS: yes the ODBC has been setup properly as well.

Thanks and regards,

[MentaL]

[Ketchup]

Poor database setup or odbc issue.

I suggest going back and reading groxys guide again and even viewing the pictures that comes with it.

[eve0021]

Poor database setup or odbc issue.

I suggest going back and reading groxys guide again and even viewing the pictures that comes with it.

Hi, thanks for the response. By poor database setup, what does that mean?
I did a simple connection test with JDBC and seems to work pretty fine with System Admin login and password.

As for ODBC setup, here's the settings for each:
all connectivity tested successfully on setup and check.

Microsoft SQL Server Native Client Version 11.00.7462
Data Source Name: character01
Data Source Description: 
Server: PCNAME\SQLExpress
Use Integrated Security: No
Database: CHARACTER_01_DBF
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No

Mirror Server: 
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes

===========================

Microsoft SQL Server Native Client Version 11.00.7462
Data Source Name: log01
Data Source Description:
Server: PCNAME\SQLExpress
Use Integrated Security: No
Database: LOGGING_01_DBF
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No

Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes

===========================

Microsoft SQL Server Native Client Version 11.00.7462
Data Source Name: login
Data Source Description:
Server: PCNAME\SQLExpress
Use Integrated Security: No
Database: ACCOUNT_DBF
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No

Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes

My question now is, is it possible I'm building it wrong? All I did was right click the project solution and hit "Build Solution".
Both app side and dbms side, they both acknowledged that I was logging in with an "account" username which does not exist in the credentials of the dbms.

Pardon my lack of knowledge in VS or other microsoft based systems, I usually work with Java and TypeScript which means I work mostly with oracle products so this is pretty new to me.






EDIT:
Ah, I should've just read the code to figure it out.
The drivers weren't using the mixed auth, from the ODBC,
which means ODBC should use machine auth instead *facepalm*

Eitherway I think that solves the issue. Will make a new thread if I have any other questions,
Kudos!

[Ketchup]

Also if you are using 64bit SQL server you should always use 64 ODBC to as 32bit will give u a headache lol.

[eve0021]

Ah thanks, I have both because of old systems at my workplace that needs patching every now and then.