Server Error in '/' Application.

---

OK - I have rolled this back to 4.9.5 a few more times and tried again going to 5.6.1. I have also tried going to 5.3. I am consistently getting this error now. Please disregard previous error above.

thanks for your help!

Server Error in '/' Application.
--------------------------------------------------------------------------------

Could not load provider DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider, DotNetNuke.Caching.FileBasedCachingProvider
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Configuration.Configurati sException: Could not load provider DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider, DotNetNuke.Caching.FileBasedCachingProvider

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.  

Stack Trace:


[Configurati sException: Could not load provider DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider, DotNetNuke.Caching.FileBasedCachingProvider]
   DotNetNuke.ComponentModel.ProviderInstaller.InstallProvider(IContainer container, Provider provider) +391
   DotNetNuke.ComponentModel.ProviderInstaller.InstallComponents(IContainer container) +106
   DotNetNuke.ComponentModel.ComponentFactory.InstallComponents(IComponentInstaller[] installers) +44
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +271

While the dnn installer can theoretically make the jump from 4.9.5 to 5.6.1 in a single leap - there are a huge number of possible scenarios where different modules and settings can possibly conflict with things is such a complex ecosystem. I would suggest you walk this upgrade up in smaller steps. DNN 5.2 introduced a lot of changes including the move to minimum base requirements of asp.net 3.5 sp1 and ms sql 2005 So maybe try doing 4.9.5 to 5.2.0 as your first jump. And also make sure you update ALL your modules at this jump as well - the updater DOES NOT automatically upgrade modules. Then 5.4.4 as the next watershed mark - more major changes here. Again make sure you update ALL your modules at this jump as well - the updater DOES NOT automatically upgrade modules. Then 5.5.1 -- and update modules Then 5.6.0 -- and update modules Then 5.6.1 -- and update modules If at the end of all this you still get the telerik error - there are ways to manually patch this one - it has to do with the system not being able to update to the latest telerik dll because of a lock. Westa