Error: "Concurrency Exception: X:XX:XX XM - Lodgement is busy"
This support note applies to:
- AO Corporate Compliance (AU)
- AE Corporate Compliance (AU)
When attempting to lodge in Corporate Compliance, you may receive the error: "Concurrency Exception: 2:04:09PM - Lodgement is busy. You can try again later."
As only one user can send and/or receive files at a time in Corporate Compliance, if you're also trying to send or receive at the same time as another user, this error will appear in the session dialog.
Alternatively, if Corporate Compliance crashes when connecting to ASIC, Corporate Compliance won't be able to complete the lodgement session. When you next attempt to lodge, this error may appear as the previous session was not completed.
This error is caused by the presence of session lock files (.lok) in the DOCQUEUE, INQUEUE and OUTQUEUE folders, which appear when a lodgement session is in progress.
To resolve this error, delete the .lok files in the DOCQUEUE, INQUEUE and OUTQUEUE folders. These folders are located in your Corporate Compliance ELS folder.