Skip to main content
Solved

Snapshot error - The operation has been aborted

  • November 3, 2022
  • 3 replies
  • 544 views

we have upgraded from 2020R2 to 2022R1.  Ever since, in both our SaaS Acumatica and our AWS sandbox, I have not been able to get a snapshot to export.  The snapshot will complete as long as I do not ask to prepare for export.  But then when I tell it to prepare for XML export, I get the following error after about 10 minutes

The operation has been aborted.

I have plenty of space, and have actually deleted all the old snapshots.  Also I have ran the optimize database after each delete and failed attempt.  I have also restarted application after database optimization and nothing seems to help.

 

Any ideas would be greatly appreciated.

Best answer by pallikasharma11

The error usually occurs when an individual table is more than 2GB, the system is unable to zip the tables into a snapshot and aborts the process. You can check the same by navigating to Space Usage form > Snapshots tab > tables, sort them in descending order.

Note: This limitation has been fixed in 2022R116, 2022R206 and later versions.

Based on the snapshot requirements and usage-

Hope this helps!

View original
Did this topic help you find an answer to your question?

3 replies

Forum|alt.badge.img+2
  • Acumatica Employee
  • 52 replies
  • Answer
  • February 22, 2023

The error usually occurs when an individual table is more than 2GB, the system is unable to zip the tables into a snapshot and aborts the process. You can check the same by navigating to Space Usage form > Snapshots tab > tables, sort them in descending order.

Note: This limitation has been fixed in 2022R116, 2022R206 and later versions.

Based on the snapshot requirements and usage-

Hope this helps!


asix02
Freshman I
  • Freshman I
  • 5 replies
  • April 14, 2023
mmedley wrote:

we have upgraded from 2020R2 to 2022R1.  Ever since, in both our SaaS Acumatica and our AWS sandbox, I have not been able to get a snapshot to export.  The snapshot will complete as long as I do not ask to prepare for export.  But then when I tell it to prepare for XML export, I get the following error after about 10 minutes

The operation has been aborted.

I have plenty of space, and have actually deleted all the old snapshots.  Also I have ran the optimize database after each delete and failed attempt.  I have also restarted application after database optimization and nothing seems to help.

 

Any ideas would be greatly appreciated.

pallikasharma11 wrote:

The error usually occurs when an individual table is more than 2GB, the system is unable to zip the tables into a snapshot and aborts the process. You can check the same by navigating to Space Usage form > Snapshots tab > tables, sort them in descending order.

Note: This limitation has been fixed in 2022R116, 2022R206 and later versions.

Based on the snapshot requirements and usage-

Hope this helps!

Sharma:

Thanks a lot. This is also my problem. Funny enough, in my case the UploadFileRevision file is 36GB although I have deleted all old snapshots before I created the new one. Any idea on how to reduce the file in size? Thanks. Toon Six (toonsix@intercs.com) 


Forum|alt.badge.img+2

The UploadFileRevision table consists of any file seen in "Search in files" screen, and only if they are being stored in the database.

Depending on your snapshot requirement if, attachments are not required I suggest to opt for Snapshot Mode Full except attachments.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings