*System.Configuration.ConfigurationErrorsException: The cache folder C:\Websites\CMS\App_Data\cache does not exist
at ImageProcessor.Web.Caching.DiskCache.GetValidatedCachePathsImpl(String originalPath, Func`2 mapPath, Func`2 getDirectoryInfo, String& virtualCachePath)
at ImageProcessor.Web.Caching.DiskCache.<>c__DisplayClass15_0.<GetValidatedAbsolutePath>b__0()
at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
at ImageProcessor.Web.Caching.DiskCache.GetValidatedAbsolutePath(String originalPath, String& virtualPath)
at ImageProcessor.Web.Caching.DiskCache..ctor(String requestPath, String fullPath, String querystring)
at lambda_method(Closure , String , String , String )
at ImageProcessor.Web.HttpModules.ImageProcessingModule.<ProcessImageAsync>d__34.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
at System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)*
If would appear that this is my problem: "System.Configuration.ConfigurationErrorsException: The cache folder C:\Websites\CMS\App_Data\cache does not exist"
However I cannot find a setting to change this pathname and as my site is not running on a c: drive, I don't know how to fix this.
Note however that by default this is a virtual path which would be on the same drive as the website. The documentation states that from version 4.7.0 of ImageProcessor.Web onwards you can specify a path outside the application (e.g. on another drive).
Check that you Application Pool has Maximum Worker Processes set to 1. Umbraco does some in memory caching before it dumps it out to the XML cache. If your back office is running across multiple processes it gets very confused which is exhibited by showing different versions of pages when you refresh your page, similar to a load balanced web farm with servers that aren't synchronized properly.
Caching error
Total Newbie alert :-)
In my logs I am seeing repeated errors:
If would appear that this is my problem: "System.Configuration.ConfigurationErrorsException: The cache folder C:\Websites\CMS\App_Data\cache does not exist"
However I cannot find a setting to change this pathname and as my site is not running on a c: drive, I don't know how to fix this.
Any help would be greatly appreciated.
I have just created a cache folder in C:\Websites\CMS\App_Data\cache on my webservers and it has stopped the errors.
However I would like to be able to configure this in the future as I don't have a large c: drive and would like the cache on another drive.
It's possible you were getting those errors because of a permissions issue - does your website IIS user have Modify access to the App_Data folder?
Your site will need that to be able to write temporary files and folders for a wide range of Umbraco-related tasks.
In terms of setting where the cache lives, you can configure this in /config/imageprocessor/cache.config, e.g.
Note however that by default this is a virtual path which would be on the same drive as the website. The documentation states that from version 4.7.0 of ImageProcessor.Web onwards you can specify a path outside the application (e.g. on another drive).
More info here: https://imageprocessor.org/imageprocessor-web/configuration/#cacheconfig
Hope that helps!
Chris
Check that you Application Pool has Maximum Worker Processes set to 1. Umbraco does some in memory caching before it dumps it out to the XML cache. If your back office is running across multiple processes it gets very confused which is exhibited by showing different versions of pages when you refresh your page, similar to a load balanced web farm with servers that aren't synchronized properly.
is working on a reply...