This usually occurs when the user has typed an invalid login id
...
or password in the login screen.
The user should verify that they are using the correct credentials,
...
check case sensitivity and ask their network/CRM Admin to verify their login details.
In this situation, we have passed the users details to the data source and it is the data source that is preventing the login, that issue must be resolved at the data source. It is not the Swift MEAP™ application that is rejecting the login, it is when we validate the details that it is coming back as invalid.
| Info | ||
|---|---|---|
| ||
Capture the client logs, please see Enabling client logs Check that the user is entering correct details and that when typed on the device, they are entering details exactly as they would in your data source. Confirm that the user is able to login to the data source directly (not via the Swift MEAP™ application) to confirm that the account is not locked / had a password change. If you have confirmed that the user has entered the correct details, please submit client logs, server logs (service in split port server) and a description of the issue, including dates/times and user details so that the transaction can be identified in the logs. |