Did this article resolve your question/issue?



Upgrade to Sitefinity 9.2 and above results in Initialization failed error during upgrade

« Go Back


TitleUpgrade to Sitefinity 9.2 and above results in Initialization failed error during upgrade
URL NameUpgrade-to-Sitefinity-9-2-results-in-Initialization-failed-error-during-upgrade
Article Number000178241
EnvironmentProduct: Sitefinity
Version: 9.2, 10.x, 11.x
OS: All supported OS versions
Database: All supported Microsoft SQL Server versions
Question/Problem Description
After upgrading from Sitefinity below 9.1 to Sitefinity above 9.1, eg. 9.2, there is an Initialization error - Object reference not set to an instance of an object. There is no error log generated for this error to track additional details on what is causing it.

User-added image

After going to Administration > Modules and Services, there is an error: "Activation/installation of some modules has failed. For more details see application error log". 
Steps to Reproduce
Clarifying Information
Error MessageObject reference not set to an instance of an object

Type : System.NullReferenceException, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : Object reference not set to an instance of an object.
Source : Telerik.Sitefinity
Help link :
Data : System.Collections.ListDictionaryInternal
TargetSite : Telerik.Sitefinity.Services.Web.Services.ViewModel.ModuleViewModel ExecuteStaticModuleOperation(Telerik.Sitefinity.Services.Web.Services.ViewModel.ModuleViewModel, Telerik.Sitefinity.Services.Web.Services.ModuleOperation)
HResult : -214746456
Stack Trace : at Telerik.Sitefinity.Services.Web.Services.ModulesService.ExecuteStaticModuleOperation(ModuleViewModel module, ModuleOperation operation)
at Telerik.Sitefinity.Services.Web.Services.ModulesService.Execute(ModuleViewModel module, ModuleOperation operation)
Requested URL :
Defect Number
Enhancement Number
The error "Object reference not set to an instance of an object." can be caused my any different reasons and in most cases, there will be Error.log generated in App_Data/Sitefinity/Logs folder or in Windows event logs.
In case there is no error log generated anywhere check if the Migration module is removed from the site configuration files.
The entry for Migration module is saved by default in App_Data/Sitefinity/Configuration/SystemConfig.config and the entry for it is (the version may differ):
​<add startupType="OnApplicationStart" version="8.1.5801.0" name="Migration" />
Note that if the site uses database storage for configuration files, check also the entry for SystemConfig.config in database table sf_xml_config_items.
Sitefinity documentation, Database storage of configurations

The other option is to disable the Module. In this case, the module record in the XML will be the following:
<add startupType="Disabled" name="Migration" />
If the resolution does not work, try commenting the whole line associated to the Migration module in the SystemConfig.config file. E.g:
<!--  ​<add startupType="Disabled" version="8.1.5801.0" name="Migration" />  -->

If the record for the module does not exist, try adding the following record in the system config:
<add startupType="Disabled" name="Migration" config:flags="1" />

This error has also been reported in a particular case where the MVC widgets (an folder) is located in a separate project within the solution and another MVC folder is kept in the SitefinityWebApp project. In that case proceed to delete the MVC folder from the SitefinityWebApp project if the intention is to have the MVC widgets in another assembly.

Last Modified Date1/30/2019 9:04 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.