May be a BUG when windows is switching to summer time

[multinet]

Hello to the team !

I believe but i'm not sure that firstpost as a bug when windows is switching automaticaly to the correct time (in France we have done a GMT+2 last week)

Indeed all bulk account i've created to be activated at the first login does not run with the message 'this account as not been activating, please contact your administrator'

in the log i've that :

03/04/2005 23:23:41 ** <- ClientThread(1712)
03/04/2005 23:23:52 ** FSAuth: Authenticate[u01-30min]
03/04/2005 23:23:52 ** PipeProcessThread(932) ->
03/04/2005 23:23:53 ** <- PipeProcessThread(932)
03/04/2005 23:23:53 ** ReadStatusFromDB2: login retry[Unlimit], Expire After [1]day(s), Start Mode[Active at the user first login]
03/04/2005 23:23:53 ** ReadStatusFromDB2: Start Date[Sun Apr 03 23:23:18 2005]
03/04/2005 23:23:53 ** ReadStatusFromDB2: Expire Date[N/A]
03/04/2005 23:23:53 ** ReadStatusFromDB2: login retry[Unlimit], Expire After X day(s)[N/A], Start Mode[Active at the user first login]
03/04/2005 23:23:53 ** ReadStatusFromDB2: Start Date[Sun Apr 03 23:23:18 2005]
03/04/2005 23:23:53 ** ReadStatusFromDB2: Expire Date[Tue Apr 05 00:23:18 2005
]
03/04/2005 23:23:53 ** Authenticate: sdate[Mon Apr 04 00:23:18 2005]
03/04/2005 23:23:53 ** Authenticate: now[Sun Apr 03 23:23:53 2005]
03/04/2005 23:24:21 ** NServiceListenThread: Listening to NService


As you can see the sdate is the CORRECT time and the now is the previous time.

In windows setting i've checked the box for summer time.


If I uncheck this box and I set manualy the correct time all is running.....

So a bug ?

[multinet]

ERROR in the previous message


the sdate IS NOT the correct time that's why the account is not activated at the time the user log in.

But the problem is still the same!

[jason]

Hi Multinet,

May i know what version of firstspot you are using?

I guess this bug has been identified and was fixed in version 3.0.2 (please refer to the version log http://www.patronsoft.com/forum/viewtopic.php?t=381 ). We will send you an email on how to download the fixed version.

Please let me know is there is still any problem

Jason
_________________
~ Patronsoft Limited ~

[multinet]

Hi,

Indeed i didn't have a look to firstspot release ! i'm still with 3.0.1 !

I'm sure that the 3.0.4 will correct my bug but i wonder if it is obligatory to unintall previous version before installing new 3.0.4 (because of parameters and client accounts) ?

Another question : is the 3.x (x=1 and over) only eligible to licence with contract maintenance ?

Thanks a lot

Have a good day

[truzicka]

We experienced the same problem, running V3.01. Can you please send me the link to V3.02. Also last night I tried upgrading to v3.11 but my 3.01 licence key comes up as invalid. Is this not an upgrade we can use? The key we purchased simply states v3

[alan]

Multinet, you need to reinstall FirstSpot to upgrade. Refer to "Upgrade/Migration issues" section in Chapter 5 of firstspot_guide.pdf for details. All v3 customers (with or without maintenance are eligible for all 3.x)

truzicka, we have change the license key in v3.1.x ( see http://www.patronsoft.com/forum/viewtopic.php?t=381 ). We will send you a link to download the latest v3.0.x.
_________________
~ Patronsoft Limited ~

[multinet]

Thanks alan for your answer.

So if i have understand as a standart user i'm able to download lastest v3.1.x and you will send me a new licence key.

Am I right ?

[alan]

multinet, yes you are right.
_________________
~ Patronsoft Limited ~