Hi all,

I'm attempting to move a DNN 4.3.4 installation from a shared hosting server to a machine here where I work. The previous database server was SQL Server 2000 and the new box has SQL Express 2005 installed (web server and sql server are both on the same box). I did successfully move the database. I've gone through a lot of documentation and forums, etc and have struggle to do this. No matter what I try I get the following error when I open the homepage:

 

---

Could not load file or assembly 'DotNetNuke.Caching.BroadcastPollingCachingProvider.SQLDataPr' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

I think the trouble lies in my connection string. Here is that portion of my web.config:

  </configSections>
   <connectionStrings>
 <add name="SiteSqlServer" connectionString="Server=HTC50132\SQLEXPRESS;Database=dbxxx;uid=xxx;pwd=xxx;" providerName="System.Data.SqlClient"/>
   </connectionStrings>
  <appSettings>
    <add key="SiteSqlServer" value="Server=HTC50132\SQLEXPRESS;Database=dbxxx;uid=dxxx;pwd=xxx;"/>

I'm using this connection string per this post. I've tried every kind of connection string and no dice. Is there something I'm missing when it comes to moving to SQL Express 2005 from SQL 2000? Does anyone have experience moving a DNN site from one box to another? Do I need to do something with the machinekey setting since I moved the site from one box to another?

Thanks for any help

 

 

I re-unpacked DNN 4.3.4 over my installation and copied the web.config back. Still the same result. What I dont understand is this line in the web.config:

<add name="BroadcastPollingCachingProvider" type="DotNetNuke.Services.Cache.BroadcastPollingCachingProvider.BPCachingProvider, DotNetNuke.Caching.BroadcastPollingCachingProvider" providerPath="~\Providers\CachingProviders\BroadcastPollingCachingProvider\" />

There is no ~\Providers\CachingProviders directory in the site. I downloaded 4.3.4 and unzipped it and that directory does not exist there either.

Found the issue. Extra DLL's in the bin folder. I just deleted the entire contents of the bin folder and copied all the 4.3.4 dll's from the install package back into it and it worked.