Don't miss out Virtual Happy Hour this Friday (April 26).
Try our conversational search powered by Generative AI!
AI OnAI Off
Intermittent Issues with Image Vault
I recommend creating a support request. I think it's the normal https://support.episerver.com you go through.
Apr 18, 2018 22:02
This kind of issues could happen in a load balanced setup if the synchronization between the instances is not configured correctly. Otherwise please do follow Johan's recommendation and create a support ticket.
/Johan Magnusson
Apr 19, 2018 15:32
Hi Johan M,
Thanks for responding, it is load balanced environment. Can you please eloborate,"the synchronization between the instanes is not configured correctly"? Or any recommendation that we could suggest to the client.
Thanks,
Rams
Apr 19, 2018 15:50
Check documentation for loadbalancing configuration for ImageVault 4
Edited,
Apr 19, 2018 16:03
Hi!
I would recommend upgrading to ImageVault 5 or later as it is much easier to manage this in newer versions. Then you will also get access to a lot of new features, including improvements for GDPR, available in ImageVault 5.7.
If you want to continue running ImageVault 4.x you can find the documentation regarding load balancing here http://imagevault.se/en/documentation/api-documentation/?v=v4.9&page=configuration/load-balancing-configuration.html
BR /Johan
Apr 19, 2018 16:04
Hi,
We have Image Vault version 4.x with Episerver, our client are getting intermittent issues with contents/categories of the Image Vault not refreshing when newly created. Worst scenario is, it is not getting reflected even after a day some times. We can't see anything on the logs that says why the image vault is not showing the contents.
The scenario is like, admins add the contents/categories in the Image Vault and these categories will be given permission based on the user needs, then contents are added to these categories. Most of the time it works, but some times it fails, and it causes the client a huge frustration, and make the system unusable for the need. I presume this is something to do with client cache.
So the next step we did was to diable the client cache in Image Vault and it caused severe impact on the episerver that almost brought the system down. So, we have to revert back.
My query now, is there any advice or any one faced such problems with Image Vault?
Thanks,
Rams