title: Landsbankinn Troubleshooting audience: end-user, admin, support keywords: landsbankinn, troubleshooting, request log, start date, statement import, password, certificate, payment batch, job queue, bank reconciliation
locale: en-us
Landsbankinn Troubleshooting
Landsbankinn request fails with "invalid username or password"
| Possible cause | How to check | Fix |
| Company password missing | Open Cloud Events Setup and review Company Password Stored. | Run Set Company Password and store the current password. |
| Per-user password missing or outdated | Open CE User Setup Editor and review User Password Stored. | Run Set My Landsbankinn Password for the current user. |
| Username mismatch | Compare Lbi Username on Cloud Events Setup and CE User Setup Editor. | Use one valid username for the intended sign-in method. |
Certificate upload action fails or signing errors appear
| Possible cause | How to check | Fix |
| Invalid PFX file | Upload fails immediately with parsing error. | Export the certificate again as PFX and retry upload. |
| Certificate password mismatch | Upload prompts complete but signing later fails. | Re-run Set Certificate with the correct password. |
| Certificate removed accidentally | Certificate Stored shows false. | Re-upload certificate using Set Certificate. |
Statement import asks for start date and stops
| Possible cause | How to check | Fix |
| No prior posted statement exists for the bank account | Start date dialog opens before import. | Enter a valid date earlier than today and continue. |
| Future date entered | Dialog rejects the value. | Enter a date before today. |
Imported statement balances look wrong
| Possible cause | How to check | Fix |
| Statement range is too broad | Check Date From and Date To on the latest request log entry. | Retry import with a narrower date range. |
| Account mismatch | Compare Account No. in request log and bank account used for reconciliation. | Run import on the correct bank account. |
| Bank-side corrections pending | Repeated imports differ by recently posted transactions. | Wait until all expected transactions are posted, then import again. |
Payment batch stays in non-final status
| Possible cause | How to check | Fix |
| Bank has not finalized processing | Inspect Landsbankinn.Payment.Result or ResultBatch response status. | Continue polling until a terminal status is returned. |
| Batch requires external approval | Result status remains pending for long periods. | Confirm approval workflow in the online bank and poll again. |
Job Queue entry fails for Landsbankinn tasks
| Possible cause | How to check | Fix |
| Missing permissions for user running the queue | Review Job Queue user permissions and extension permission sets. | Assign required permission sets and rerun the entry. |
| Temporary bank endpoint issue | Multiple requests fail with similar transport errors. | Retry later and compare request log HTTP statuses. |
Request log does not show expected details
| Possible cause | How to check | Fix |
| Debug mode disabled | Lbi Debug Mode is false on Cloud Events Setup. | Enable Lbi Debug Mode briefly for troubleshooting, then disable it again. |
| Looking at wrong company data | Account No. and user do not match expected context. | Switch to the correct company and open the latest entries again. |
For field and term definitions used in this guide, see Glossary.
© Origo – Cloud Events Base Extension