May 12, 2009
(1 votes)

ImageVault and EPiServer page provider does not work together

I have an an EPiServer CMS 5 R2 installation with ImageVault installed. Yesterday I tried to add a custom page provider to the project. I used the XML page provider found here:

You will get the error:


EPiServer.BaseLibrary.ClassFactoryException: ClassFactory not initialized


[TypeInitializationException: The type initializer for 'EPiServer.DataFactory' threw an exception.]

EPiServer made some changes to the startup events of the application in R1 SP3. ImageVault does not implement the startup in this new way. If you look deeper in the stack trace you will see:

[Exception: Error initializing CreatedPageEvent in PluginStartup] ImageStoreNET.PluginStartup.get_CreatedPageEvent() +126

ImageVault hookes up the CreatedPageEvent to early and therefore the DataFactory.Instance isn’t instantiated.

Get the web site running

The problem is with the handler <add name="ImageVault" type="ImageStoreNET.PluginStartup, ImageVault.EPiServer5" />. Just comment this line and the application will start. I don't' know what this handler does but probably ImageVault will come up with a solution soon.

May 12, 2009


Helen Hopkinson
Helen Hopkinson Sep 21, 2010 10:32 AM

Please note that ImageVault 3.3 is not officially supported for EPiServer CMS 5 R2 SP1 according to the version matrix on Sep 21, 2010 10:32 AM

Strange... ImageVault 3.2.2 is supported for EPiServer CMS 5 R2 SP1 according to your matrix. Then should also 3.3 be supported?

Per Hemmingson
Per Hemmingson Sep 21, 2010 10:32 AM

Great Post!
Yes according to the matrix it should. We'll have to look into it.

However, we (episerver world) had similar problems with the introduced change in startup events in the CMS, but with EPiServer Community's handler. This is a different problem but the temporary solution to it might work; Since community is not depended on CMS we moved the Community registration before CMS initialization handler in web.config. I'm not familiar with what imageVaults handler does but its worth a try.

Sep 21, 2010 10:32 AM


We will look into this and make an updated version available as soon as possible.
Please note that there might be some side effects to the suggested workaround since it will prevent ImageVault from hooking on to certain events that is required for mirroring, keeping track of used images and so on.

/Johan Magnusson, Product Manager, Meridium Sep 21, 2010 10:32 AM

The workaround ph mentioned does not work in this case. I Think it's because ImageVault is dependent of CMS in the startup.

Sep 21, 2010 10:32 AM

Just a comment on the version matrix referred to and the supported version of ImageVault. The version matrix refers to the EPiServer Create+ package with all the included modules, and so far the latest version of Create+ is 1.1 (for EPiServer CMS 5 R2 SP1), supporting ImageVault 3.2.2. The next upgrade of Create+ will include ImageVault 3.3, but this version has not yet been officially released.

You can find the version matrix here:

Please login to comment.
Latest blogs
Vulnerability in EPiServer.GoogleAnalytics v3 and v4

Introduction A potential security vulnerability was detected for Optimizely Google Analytics addon (including EPiServer.GoogleAnalytics and...

Bien Nguyen | Sep 20, 2023

Overriding Optimizely’s Content Recommendations Block to Implement Custom Recommendations

Introduction The Content Recommendations add-on for Optimizely CMS dynamically recommends content from your site tailored to the interests of each...

abritt | Sep 13, 2023 | Syndicated blog

Developer contest! Install the AI Assistant and Win Bose QC45 Headphones!

We are thrilled to announce a developer contest where you have the chance to win a pair of Bose Headphones. The goal is to be the first developer t...

Luc Gosso (MVP) | Sep 7, 2023 | Syndicated blog

Send Optimizely notifications with SendGrid API, not SMTP

If your Optimizely site already sends transaction emails through an email platform API, why not do the same with Optimizely notification emails?

Stefan Holm Olsen | Sep 6, 2023 | Syndicated blog