Skip to main content

Re-process sales invoices after an interrupted invoicing run

When a sales order invoicing run is interrupted by a PC crash, network drop, or session abort, temporary records can be left in the database that prevent subsequent invoicing attempts from running correctly. This article explains how to diagnose the issue

A
Written by Andrew McNeice

You may see one of the following error messages when trying to re-run the invoicing process:

  • 'Attempted to read or write protected memory'

  • 'Blocked by other user'

  • 'Exceptions have occurred'

Diagnose the issue

Work through these checks before raising a support case.

  1. Confirm no other user is currently running an invoicing session. If another run is active, wait for it to complete before retrying.

  2. Check whether the affected orders show '0' under the invoice number, or appear as 'Dispatched Not Invoiced' despite invoices existing.

  3. Wait a few minutes and retry the invoicing run. Temporary records occasionally clear automatically.

  4. If the problem persists after the above checks, raise a support case. The support team will need to clear the temporary records from the database via remote access. This cannot be completed by end users directly.

What to include in your support case

Include the following information to help the team resolve the issue:

  • The sales order numbers affected.

  • The date and approximate time the invoicing run was interrupted.

  • The exact error message displayed.

  • A count or list of the blocked orders.

Did this answer your question?