Image deleted from Media Library after using update button

Alexandre Zuppo asked on January 13, 2026 18:23

Symptom: When using the update button to update an existing file inside a folder in Media Library (on Kentico Admin), that file is deleted from Media Library (deleted from Azure Blob Storage folder), but the record on database is kept.

There´s no error message (Kentico popup alerts). The Kentico Event Log shows a "Information" type entry, code "UPDATEOBJ", description "Update Media file 'my img file name'" (it looks like success). No "Local Tasks" pending on Smart Search, No web farm tasks pending.

Environment: Kentico 13 (13.0.190) + Azure Blob Storage. Individual Azure webapplications to host the Admin and the MVC sites. The webFarm shows 2 servers: 'Admin' and 'MVC', both 'Healthy'. I am doing that with my user account which is Global Admin. On Media Library Security tab we use "Authorized roles" for all actions (create file, create folder, etc), then in the bottom panel, the "CMS Global Administrator (global)" role has checked in all actions (create file, create folder, etc). That specific folder (inside Media Library) has no other file and just few sub-folders, I mean no folder with more than 100 items in any level of that Media Library.

Any thoughts, ideas, suggestions? Thanks in advance!

Correct Answer

Juraj Ondrus answered on January 14, 2026 05:21

Is the Azure storage shared for the admin and front end app? If yes, did you disabled the sync of media files? If not, then this is the cause. What the update does is that it deletes the file and replaces it with the one selected for the update. If the storage is shared, then one app deletes the file and updates it. While the second one deletes the already update file again.
For a shared storage, you should also use the shared storage configuration. E.g. as described in the auto-scaling documentation. If you are sharing just the media files storage, then you can select what should be synchronized in Settings. You can access these settings in the Settings application under the Versioning & Synchronization -> Web farm category. And then in the Allow synchronization for section, deselect e.g. the media files. (and other files, which are shared across the apps). It makes no sense to sync one and the same file. It will be better also for performance.

1 votesVote for this answer Unmark Correct answer

Recent Answers

Brenden Kehren answered on January 14, 2026 18:39 (last edited on January 14, 2026 18:40)

Alexandre,

I've had this on multiple sites even prior to version 13. If the file name is different, it will cause problems. If there are connection issues, it will cause problems. But mostly it never worked for us or any of our clients when we used blob storage.

I know I reported this issue, but can't remember if it was in v12 or v13.

The fix to help with orphaned database records is to manually copy a file with the same name and extension to the proper file location. Very manual and sucks, but it helps to get things working again.

0 votesVote for this answer Mark as a Correct answer

Alexandre Zuppo answered on January 14, 2026 22:10

Guys, thank you for the answers.

Brenden, I forgot to mention that I am trying to update the existing file with another one with same name. In my case was the opposite. If I update the existing file by another one with different name, it worked. At least in some tests I did. But I believe that what was happening in my case was the situation Juraj explained. Curious thing, it would fit for updates by file with different names also.

Juraj, your explanation make sense. Yes we share the Azure Storage with Admin and FE app. I unchecked the 'media file' as you suggested and it worked.

Thanks a lot guys! Have a great one!

0 votesVote for this answer Mark as a Correct answer