SBR EE with Mysql on windows

[Fahad_khan_]

Hi Folks,

I have installed MySQL and SBR installed on my windows 7 machine and trying to authenticated using the login credentials stored in MySQL, But somehow unable to test it successfully, Can you please help. I have installed ODBC driver and have tested the connection successfully. I tried multiple ways in [Settings] section of sqlauth.aut, please help in finding the problem.

In Mysql, I have a table "auth" having  only two fields - name and password

sqlauth.aut

[Bootstrap]
Enable=1
LibraryName=sqlauth.dll
InitializationString=SQL

[Settings]
;Connect=DSN=<dsn_name_here>;UID=<username_for_dB>;PWD=<password_for_dB>
;SQL=SELECT password, profile FROM userlist WHERE name = %name/40
;Connect=DSN=SQL;UID=root;PWD=root123
;Connect=root/[email protected]L
Connect=DSN=SQL://192.168.1.50:3306/db_test;UID=root;PWD=root123
SQL=SELECT password FROM auth WHERE name = %name/40
ParameterMarker=?
MaxConcurrent=1
ConcurrentTimeout=30
ConnectTimeout=25
QueryTimeout=25
WaitReconnect=2
MaxWaitReconnect=360
PasswordFormat = 0
DefaultResults = 0
ShutdownTimeout = 1
ErrorMap=<mssql.ini|mysql.ini|oracle.ini>
LogLevel=0

Thanks in advance

[kalagesan_]

Hi Fahad,

What is the error you see in SBR debug logs? can you upload the SBR debug logs captured with log and trace level =2 by replicating the issue?

Also, does this SBR  server authentication works with native user authentication method?

Regards,

Kannan

[Fahad_khan_]

I have attached the log file, perhaps this would help in isolating the problem. Yes native authentication is working fine.

[jcanchola_]

Hi Fahad,

It looks like SBR can't find the DSN name in the Windows SQL driver.  Can you make a successful connection with that DSN using ODBC?

[Fahad_khan_]

Yes, I can make successful connection...Do you think settings in sqlauth.aut is correct?

[jcanchola_]

My Only question is how do you have the connection defined in ODBC?  When SBR tries to connect to the database it connects to the ODBC driver.  The error you are getting in the SBR logs indicates that the ODBC driver can't find this DSN.