10-16-2013 06:55 AM
We have just come across a bug which I thought we should share:
Steps to replicate: ** Do not try this if you are running the new Saleslogix Mobile 3 on your live site **
Open the SLXMobile and enter your username Now enter the wrong password. You will receive the standard warning “The username or password is invalid”
Now remove the password and enter the correct password. You will now receive another warning/error ‘A problem occurred on the server’ From now on the user will not be able to use the SLXMobile! All other users will be fine until you do the same. The user will still be able to access the LAN and WEB client fine.
The only way I have been able to resolve this so far is by completely removing the SLXMobile directory and redeploying v2.2 – Swiftpage UK have replicate this and are now in the process of escalating it to the US.
10-16-2013 08:46 AM
10-16-2013 09:04 AM
Thanks RJ - I thought the issue only occurred in v3.0.1 until I worked back through the versions
Mike has just created a temporary fix which we may use if this does not get resolved within the next 24hrs.
Temp Fix: Remove the Primary Key on the Userid column within the UserSecurity table and set the Userid to allow NULLs. Grab the ID from the Userinfo table to update the Usersecurity table where the Userid is NULL
10-16-2013 09:30 AM
3.0.0 and 3.0.1 are SO close to each other - the real diff has to do w/Custom Hash Tags showing not showing up in the lookup in 3.0.0.
Humm.. not comfortable w/ making the USERID allow nulls.... We really need a fix asap from the dev team (like today).
10-16-2013 02:20 PM
There is a very strong chance that this is a Web Core issue and not directly Mobile 3.0.1. We have logged a defect (13093076) with SData where if a failed attempt passes through SData that the user will be locked out. There are multiple scenarios around this but that is the general idea. The defect was logged for Web Core 04 and is slated to be fixed in Web Core 05. I don't see a post here where the exact version of SalesLogix Web was called out, but if you have Core 04 applied that is the likely culprit. Please contact SalesLogix Support for assistance.
13093076: In SData, if there is a failed login attempt an error displays
10-16-2013 04:35 PM
It certainly looks like the culprit is in SData where the attempted login fail logic is stepping on mobility.
Humm wonder if doing:
Update sysdba.USERSECURITY SET LOGINATTEMPTS = 0
would clear the problem?
Might have to "reset" the FAILEDATTEMPTDATE field as well (to NULL)
10-17-2013 02:34 AM
Check your inbox. Lets hope this interim fix from Swiftpage works for you too until WEB Core Update 05 is released for our customers.
10-17-2013 04:46 AM
10-17-2013 06:48 AM
Please note this is NOT an interium fix, it is purely a validation build of 2 files for Web 05.
This file is provided in confidence to BPs and should not be passed around the community.
It will only be released expressely from SalesLogix Support under guidenance from our colleagues the US Development and 3rd Line Support Teams.
These files are NOT SUPPORTED and anyone using them does so at their own risk.
10-17-2013 12:51 PM
This WILL clear up the problem and let you log in:
SET LOGINATTEMPTS = 0
where LOGINATTEMPTS is not null and LOGINATTEMPTS > 0
However, once you "fail it again".. you will have to run an update.
On our system I'm using a simple TaskCentre task to handle the problem.. you could create a scheduled WIndows Task to do it as well (if you know how to fire off a SQL statement via a "bat" file ;-)
Note this is NOT unique to mobility 3.0 or 3.0.1 - 2.2 can fail too .. it's an SData portal issue.