unable to use Both Username/Password & Scratch Code toge

[nottinghub]

I have a strange issue with FirstSpot 7.0.6 using MySQL 6.0.9 (using mysql-connector-odbc-3.51.30-winx64 drivers) on Windows Server 2008 R2 Enterprise 64-bit.

When I set up Login Option as "Username/Password", then everything works fine. Users are able to login with no problem with a username/password.

When I set up Login Option as "Sratch Code", then everything works fine. Users are able to login with no problem with a scratch code.

But when I set up Login Option as "Both Username/Password and Scratch Code together", then none of the previously succesfully used scratch code or username/password work. The user systematically get "Invalid Logon. Please try again..."

when the username doesn't work, here's an extract of what the log (firstspot_gw_srv_2012.04.02_12.02.2 shows:
02/04/2012 12:03:16 ** AuthLoginODBC: Authenticate[eid101b]
02/04/2012 12:03:16 ** AuthLoginODBC: Authenticate Failed[eid101b]


For reference, here's the log extract when the username works:
02/04/2012 12:09:54 ** AuthLoginODBC: Authenticate[eid101b]
02/04/2012 12:09:54 ** RetVal[1]
02/04/2012 12:09:54 ** AuthLoginODBC:[eid101b] recur_option[0], week_sch[0], start time[-1], end time[-1]
02/04/2012 12:09:54 ** AuthLoginODBC: Current Time [Mon Apr 02 12:09:54 2012], EDate [N/A]
02/04/2012 12:09:54 ** AuthLoginODBC:[eid101b] browser Information (Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0))
02/04/2012 12:09:54 ** AuthLoginODBC: haveIbMsg [0]

[alan]

We cannot reproduce your issue. Please:

1) restart FirstSpot
2) reproduce the problem by logging in using a username and a scratch code once
3) post your firstspot_gw_srv_[timestamp].log file under FirstSpot\log directory here (you can select the log file content first, and then click the forum "Code" button. This will stop the forum from reformating your log file).
_________________
~ Patronsoft Limited ~

[nottinghub]

Problem was resolved.

It was due to an error caused by some changes we put in the login.tpl file. Reverting to the default tpl fixed the issue.