Hi Matthias,

To change from .NET 3.5 to 4.5 requires that your host has installed .NET 4.5 and then in your web control panel you would have to change the configuration from .NET 3 to 4. If the wrong version of the framework is selected in control panel the site will fail to load. See related items 9 and 10 in our FAQ. For a major error like that even app_offline will not work.

For any error the first step is to find out the error details as discussed in Basic Troubleshooting.

There is no reason to delete file before uploading.

If your host has .NET 4/4.5 installed and you want to use the .NET 4 package of mojoPortal then it is best to work through the error until it is resolved, don't re-upload the old version, just find out the error details and we will try to help resolve it.

Usually a problem like the menu as you described would be caused by either an error in the layout.master file or in theme.skin, in which case there should be a corresponding error in the log.

Best,

Joe

Hi Matthias,

I think to change from .NET 3.5 to 4 will result in some down time unless you make a copy of the site at a different hostname and then change the dns of the main hostname after the site is working.

500 is the status code of all web requests that result in an error, need to know the detail of the error to resolve it.

When changing like this errors are going to happen because the .NET 4 package files will cause an error if the application pool is 3.5 and the 3.5 package of mojoPortal will also result in an error if the application pool is for 4. There are incompatible difference in Web.config between the different frameworks. It is technically possible to run the mojo 3.5 package under .NET 4 with web.config modifications because older .NET assemblies can run in the newer framework but the mojo package for .NET 4 will never load under .NET 3.5 and the first problem will be web.config. These web.config errors are discussed in the 9th and 10th items in our faq.

Web.config errors means it fails to load the web.config so no settings from web.config are applied since it failed to load and the site will not load. In this case the error may not be in the mojoportal log but the detail will be in the windows application log in event viewer on the server.

To change to .NET 4 you would prepare the files on your local machine, transfer machinekey from old web.config to new one, upload all the files and of course errors will happen until all the files are uploaded and the application pool is changed to 4.

Once that is done if you still get an error we still need the detail of the error one way or another, either form the mojoportal log or from the windows application log in event viewer which your host could access for you. Once the error detail is known the solution will be clear. Probably some file failed to upload or something.

Note also that if you have any add on products you will need to update to .NET 4 version of those too as part of preparing the package on your local machine before uploading is the ideal time to update those files.

Hope that helps,

Joe