This is a weird problem which we cannot reproduce locally while trying to upgrade old projects. Let me suggest a couple of possible problems and solutions for them, hopefully they will fix your problem:
Problem: locked dll files
in the bin directory while applying the patch. This can cause this reference issue.
Resolution: unlock dll files in the bin directory either by stopping IIS or using some tool to make sure no other process has locked them and then apply the patch once again.
Problem: some custom module of yours may be referencing the old Telerik.Blogs.dll
Resolution: rebuild all of your projects with the new assemblies from v3.2 if they are using any of the Sitefinity dlls.
Problem: Database not upgraded
Resolution: Actually this is a bit of a trick
. Here are the steps how to do it:
1. Open the web.config
file of your website and change
- <cms defaultProvider="Sitefinity" pageExtension=".aspx" disabled="true"
- <roleManager enabled="false"
2. Open up your website
and Sitefinity should redirect you to the screen where you choose your database for the project.
3. Choose the same database server and database name
that exists in your current site configuration and proceed.
This will force Sitefinity to try and upgrade the database
For another possible solution, you can refer to this online resource:
If these solutions are not successful
, we will need some more information to pinpoint the problem:
1. Which Sitefinity version
your old project was built with - 3.1, 3.1 SP1, 3.1 SP2, etc.?
2. What database do you use
- SQL Server 2005, SQL Express, etc.?
3. Which patch did you download
and apply - patch date, name, etc.?
Let us know how it goes.
the Telerik team