Skip to main content
Solved

Customization Error: Cannot access the uploaded file. Failed to get the latest revision.


jhouser
Captain II
Forum|alt.badge.img+3

I published customization in a production tenant, assuming it would add the new screens to the test tenant also. It did not, so attempted to publish in test tenant. I got the error below:

I then unpublished in the first tenant, then tried publishing in test. Same error. 

I found this: acumatica - Error when attempting to Publish Customizations (Cannot access the uploaded file) - Stack Overflow

I located the missing file within the customization, but I don’t understand what the above post means by “remove file link reference”. Nothing I’ve tried works. I tried deleting the file itself and re-uploading, but it says invalid file type. 

Then I found this: How to resolve the 'Cannot access the uploaded file' error on publishing a customization project | Community (acumatica.com)

Tried and didn’t work. I’m sure the missing file I found is the problem, but I can’t figure out how to fix it. Anyone know?

Best answer by jhouser

Problem solved: The tenant I was using was from a snapshot excluding attachments. So the error was from the existing packages that were brought over without their attachments. Had nothing to do with new package. A file link within it that said file couldn’t be found threw me off track. 

 

Restoring a snapshot with attachments allowed me to publish the new package successfully. 

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

4 replies

Mike Gifford
Jr Varsity III
Forum|alt.badge.img
  • Jr Varsity III
  • 25 replies
  • March 15, 2024

How are file attachments configured in this environment?  This sounds like maybe they are stored external to the DB and the reference to that file is broken - remember that customizations have a footprint in the file storage as well.

If this is the case, be careful how you resolve this as you could end up having duplicate references if things are not kept straight.


jhouser
Captain II
Forum|alt.badge.img+3
  • Author
  • Captain II
  • 108 replies
  • Answer
  • March 20, 2024

Problem solved: The tenant I was using was from a snapshot excluding attachments. So the error was from the existing packages that were brought over without their attachments. Had nothing to do with new package. A file link within it that said file couldn’t be found threw me off track. 

 

Restoring a snapshot with attachments allowed me to publish the new package successfully. 


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • 2759 replies
  • March 20, 2024

Thank you for sharing your solution with the community @jhouser!


NickCerri4
Jr Varsity II
Forum|alt.badge.img
  • Jr Varsity II
  • 17 replies
  • April 11, 2024

Good day, team - I’m running into this issue as well.  However, the snapshot I’ve received shows the Export Mode as “Full” so the attachments should be included.  Is there any other reason this error would be surfacing?  Thank you!


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