/
Sales order archiving errors 'There is already an object named AR_SO_History ....'

Sales order archiving errors 'There is already an object named AR_SO_History ....'

Problem

Running the archive utility for sales orders can error where a previous attempt to archive has failed or been interrupted.

Solution

SQL skills are required

A working knowledge of SQL Management Studio is required to complete this task.

The problem is caused by a failed/interrupted sales order archive run. What happens is that tables are created and used by the underlying stored procedure. If these tables do not get cleaned up by the stored procedure at the end (say, because it got interrupted or fell over for some reason), then next time it is run it won't be able to create it's tables (because they already exist).

The script is generic in that it will simply detect and delete any tables that are going to get in the way of the sales order archive.

DO NOT run this script while the archive process is happening.

Related articles







Related content

Archiving sales orders errors
Archiving sales orders errors
More like this
Archiving sales order data error - 'CREATE TABLE permission denied in database ...'
Archiving sales order data error - 'CREATE TABLE permission denied in database ...'
More like this
Creditor Transaction Archiving fix to "String or binary data would be truncated".
Creditor Transaction Archiving fix to "String or binary data would be truncated".
More like this
Debtor Child sales orders do not appear in the Parent / Head Office account - 7.00.175 SR10 and prior
Debtor Child sales orders do not appear in the Parent / Head Office account - 7.00.175 SR10 and prior
More like this
Archiving
Archiving
More like this
Yearly rollover hangs
Yearly rollover hangs
More like this