After 4.2 SP1 upgrade website forbidden

Hello all!

I upgraded my website from 4.2 to 4.2 SP1 on the following way:

1.    With the projectmanager I upgraded the website
2.    Because I got loaderexceptions I removed all the dll's from the bin map (also all references from my project) and re-added the "Empty Project" dll's and re-referenced these in my project.

The website is running, but my website seems to be forbidden for some reason. On all pages I get the error:
 

Hello Peter,

What kind of errors did you receive when you upgraded your project using the project manager? There should be a log file in ~/App_Data/Sitefinity/Logs/UpgradeTrace.log. Also, what "loaderexceptions" did you receive after you upgraded with the project manager? The upgrade clearly failed at some point since the eCommerce modules weren't upgraded properly.

You could eventually send us you non-upgraded project so we could try upgrade it here and see what are the problems.

Hello Lubomir,

First, excuse me for editting this post again, but I made a litte bit of progress (no loaderexceptions after upgrade).

I just tried to upgrade my 4.2.1650 version (backup ;)) with the project manager. This is the result:

1. First I removed the tempDirectory rule from "<compilation debug="true" targetFramework="4.0" tempDirectory="F:\cache\">" (tip from Finding the turbo switch with Sitefinity development). Then I removed the following rule from the systemconfig.config (a quickfix from your site):

Hi Lubomir,

Reason that the lowest 3 options were not updated was a licence issue. This is fixed.
The website is still forbidden and the backend is not reachable though.

Regards,
Peter

Hi,

Well, I 've got the 4.2 SP1 version working now :). When I do not use your project manager, but copy and replace the
EmptyProject dll's into my project and then run my website, it works. How is that possible?

Best regards,
Peter

Hi Peter,

I'm not quite sure. When you load a project from your project manager you use the internal Casini server to serve the pages. When you copy the files from the _EmptyProject folder, do you create an application in IIS? That might be a difference, but I'm not sure about that.

Hi Lubomir,

I'm using the ASP.NET Development server from Visual Studio. I copied/replaced the dll's and run the website from visual studio.

Best regards,
Peter

Hello Peter,

I'm sorry to hear baout the problems you've had upgrading your project. When you upgrade it through the project manager (which is the officially recommended practice) what it does is upgrade the assemblies in the bin folder with the ones from the new version. The actual upgrade happens when you start the application afterwards - the database upgrades itself, and the application modules will also be initialized with the new version. In that line of reasoning, unless there have been some problems while upgrading that particular module
all modules in SystemConfig.config should point to the new Sitefinity version. The upgrade process (through the project manager) also creates an upgrade log file, located in ~/App_Data/Sitefinity/Logs, can you please check if there have been any exceptions recorded?
As per the forbidden pages issue, can you please let us know whether the problem occurs only when browsing the frontend, or is also valid when logged in as Sitefinity user/ administrator in the backend. This behavior might be due to improperly upgraded database/configuration files, which has resulted in mismatch between the default role IDs and the permissions for your content/pages. Can you please check if the role IDs in your upgraded SecurityConfig.config match the ones from the pre-upgrade project SecurityConfig.config and the ones for column principal_id in the sf_permissions table in the database.

Best wishes,
Boyan Barnev
the Telerik team

Hello Boyan,

thank you for your reaction. As mentioned before, my update succeeded when I manually replaced the emptyproject dll's into my own project.

The only problem when I updated through the project manager (all modules were indeed updated, that was my mistake) were the forbidden pages on the frontend (only) and no access when I logged in at the backend (invalid username / password).

I can't see any related errors in my logfiles. The role IDs in my upgraded SecurityConfig.config are identical with the pre-upgrade config. What can I check in the sf_permissions table? The principal_id's are the same as the config files, but when I check for example the owner principal_id (with the latest last_modified date) before and after the update, there are 15 records before and 9 records after. So maybe this is something?

In my opinion it certainly is something like an invalid or unfinished database upgrade, so it could indeed be your sf_permissions table suggestion.

Best regards,
Peter

Hello Peter,

I'm sorry to hear that the problems persist, indeed that's a very strange issue. Would it be possible for you to provide us with your Sitefinity 4.2 Project files and database backup, so we can upgrade them locally and inspect the problematic behavior ourselves? Thanks in advance.

Kind regards,
Boyan Barnev
the Telerik team