Create New User Error
I'm running 4.1 SP1, upgraded from 4.1, upgraded from 4.0. When I click on New User from the Administration --> Users page I receive this error. Can someone help me out?
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Telerik.Sitefinity.Fluent.DynamicData.DynamicTypeDescriptionFacade.LoadDynamicTypeDescription(Type dynamicType) +88
Telerik.Sitefinity.Modules.UserProfiles.UserProfilesHelper.GetUserProfileType(Type clrType, String metaDataProviderName) +173
Telerik.Sitefinity.Modules.UserProfiles.Web.UI.UserProfilesControl.InitializeControls(GenericContainer dialogContainer) +578
Telerik.Sitefinity.Web.UI.SimpleView.CreateChildControls() +81
System.Web.UI.Control.EnsureChildControls() +181
System.Web.UI.Control.PreRenderRecursiveInternal() +59
System.Web.UI.Control.PreRenderRecursiveInternal() +221
System.Web.UI.Control.PreRenderRecursiveInternal() +221
System.Web.UI.Control.PreRenderRecursiveInternal() +221
System.Web.UI.Control.PreRenderRecursiveInternal() +221
System.Web.UI.Control.PreRenderRecursiveInternal() +221
System.Web.UI.Control.PreRenderRecursiveInternal() +221
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4184
Hello Mark,
The error you get is probably caused by the upgrade process not doing its job properly.
Can you tell me if you have a record in sf_meta_type_descriptions that looks something like this:
id - 445278DC-F303-4BEC-8589-E2A7446C610C
app_name - //
meta_type_id - 638670CC-B540-4FD3-ADB0-101899D1630A
user_friendly_name - Basic profile
description - NULL
voa_version - 1
Also you need a record in sf_meta_types with id equal to the meta_type_id above. We have some clients reporting that doing a fresh upgrade the issue goes away.