We have a DNN 3.2.2 site on a Web Farm system with a central file server. Before, on the test system with a single server we were not having any problems but now we have an extensive amount of “Failed to start monitoring changes” exceptions. These exceptions are invisible for the client but it makes hundred of entries in the logs for a single day! I’ve read all the documentation (“DotNetNuke Web Farm Support.pdf”) but all seems to be correctly configured. Here is the complete exception text; I’ll be very grateful if someone could help me.

InnerException: Failed to start monitoring changes to '\\172.16.2.100\arkema_CMS\Portals\_default\Cache\RG90TmV0TnVrZS5TZXJ2aWNlcy5TY2hlZHVsaW5nLlNjaGVkdWxlSGlzdG9yeUl0ZW0=.resources'.
Message: System.Web.HttpException: Failed to start monitoring changes to '\\172.16.2.100\arkema_CMS\Portals\_default\Cache\RG90TmV0TnVrZS5TZXJ2aWNlcy5TY2hlZHVsaW5nLlNjaGVkdWxlSGlzdG9yeUl0ZW0=.resources'. at System.Web.DirectoryMonitor.AddFileMonitor(String file) at System.Web.DirectoryMonitor.StartMonitoringFile(String file, FileChangeEventHandler callback, String alias) at System.Web.FileChangesMonitor.StartMonitoringPath(String alias, FileChangeEventHandler callback) at System.Web.Caching.CacheDependency.Init(Boolean isPublic, Boolean isSensitive, String[] filenamesArg, String[] cachekeysArg, CacheDependency dependency, DateTime utcStart) at System.Web.Caching.CacheDependency..ctor(String filename, DateTime start) at System.Web.Caching.CacheDependency..ctor(String filename) at DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider.Insert(String CacheKey, Object objObject, Boolean PersistAppRestart) at DotNetNuke.Common.Utilities.CBO.GetPropertyInfo(Type objType) at DotNetNuke.Common.Utilities.CBO.FillCollection(IDataReader dr, Type objType) at DotNetNuke.Services.Scheduling.DNNScheduling.SchedulingController.GetSchedule() at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.LoadQueueFromTimer() at DotNetNuke.Services.Scheduling.DNNScheduling.CoreScheduler.Start()
StackTrace:
Source:
Nom du serveur: CL2-NODE3