Issue: 'Telerik.Sitefinity.Security.UserIdentity' in assembly 'Telerik.Sitefinity, Version=5.4.4010.0 is not marked as serializable
I have upgraded Sitefinity from 5.2 to 5.4 version and getting this error which stops me from any development. It happens first thing after I start debugging website. My current fix is Clean solution. What can be cause? Could be that upgrade did not go well?
Server Error in '/' Application.Type 'Telerik.Sitefinity.Security.UserIdentity' in assembly 'Telerik.Sitefinity, Version=5.4.4010.0, Culture=neutral, PublicKeyToken=b28c218413bdf563' is not marked as serializable.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.Runtime.Serialization.SerializationException: Type 'Telerik.Sitefinity.Security.UserIdentity' in assembly 'Telerik.Sitefinity, Version=5.4.4010.0, Culture=neutral, PublicKeyToken=b28c218413bdf563' is not marked as serializable.
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.
Any help or advice would be appreciated.
Thank you
Hi Ganna,
From the error message the UserIdentity type is not meant to be serializable. The exception is related to the environment or network setup from where the code for authentication is executed. If you are running the code trough proxy of network infrastructure that limits access in certain way try executing it outside of this environment or check what restrictions are applied in regard to IP addresses in the network.
Kind regards,
Hi Jen,
We have a similar error and once the user logs in, we redirect the user to the home page which displays the error. The login page is located at: /homePage/login and the home page URL is /homePage.
Can this lead to the issue?
The environment that we are working is localhost with administrative permission and we do not have any proxy installed on our servers.
What might be the cause of this?
Your prompt response is appreciated. Please help ASAP.
Hello Siddesh,
Based on our experience, such issue could be caused if the project is run on Visual Studio Development server (Cassini)?
You could try to run it on IIS, following that article.
Regards,
Svetoslav Manchev
Telerik