You can upgrade to 9.11.0 when you have Telerik dependencies - but you must not remove Telerik in this case. I have one (not publicly available) site that still has dependencies (DNN.Events module, I have not found a free replacement for this) and it runs under DNN 9.11.0.

Happy DNNing!
Michael

I've tried this about 4 times now and getting nowhere... Each time from a full restore of database/files.

The original error persists (see first post in this thread), despite following all the advice in this thread.

The site looks partially upgraded, but none of the menus appear, and errors when trying to access admin functionality.

When I check the extensions, I can see all of the providers that failed in the initial install log, ready to install. When I click the "Install" button on the "Available Extensions" tab, it greys-out and say there is an error and check the Admin event logs, which I can't do, because this is functionality that is dead after the failed upgrade. The URL of the event logs indicates a failed NewtonSoft component.

https://www.h-----.com/De...x80131040)&content=0

When I try to manually install the this component (or any other) from the install extension, it starts loading it, and then gets this.

UPLOAD EXTENSION PACKAGE
To begin installation, upload the package by dragging the file into the field below.

An unknown error has occured. Please check your installation zip file and try again.
Common issues with bad installation files:
Zip file size is too large, check your IIS settings for max upload file size.
Missing resources in the zip file.
Invalid files in the package.
File extension is not .zip.
Check that you are logged in

Any ideas? It seems I need to resolve the initial failure, because trying to fix it from a half-upgraded site just seems like it's not going to work.

Is there a way to manually install the components that failed?

Besides the options already mentioned, it might be worthwhile to verify the versions of Newtonsoft and DependencyInjection in the web.config. It might be that the version in the bin folder is different than the one mentioned in the web.config. If there are differences, you can update the version number in the web.config to the correct ones and restart IIS.

Posted By Tycho de Waard (SU) on 1/17/2023 12:20 AM

Besides the options already mentioned, it might be worthwhile to verify the versions of Newtonsoft and DependencyInjection in the web.config. It might be that the version in the bin folder is different than the one mentioned in the web.config. If there are differences, you can update the version number in the web.config to the correct ones and restart IIS.

As Tycho suggests, these manual steps might be necessary to get you upgraded this time. 

This isn't normally necessary, but it does become necessary when certain bad practices are implemented by any selected third-party extension, or if any installation/upgrade was manually done in the past. 

If you follow best practices now and manage to get yourself through this (partially manual) upgrade, you should have a much better experience next time.