Hi All,

I have a site that I recently upgraded from DNN 2.1.2 to DNN 4.8.2 (in a development environment).

Everything seems to be working nicely, but I had some of our users try to login to the newly upgraded development version, and one of them is getting the following exception message when he attempts to login:

Exception information:
    Exception type: XmlException
    Exception message: Data at the root level is invalid. Line 1, position 1.
 
Request information:
    Request URL: http://d-www.generationjoshua.org/dnn/Default.aspx
    Request path: /dnn/Default.aspx
    User host address: 172.17.11.230
    User: grewejd
    Is authenticated: True
    Authentication Type: forms
    Thread account name: NT AUTHORITY\NETWORK SERVICE
 
Thread information:
    Thread ID: 16
    Thread account name: NT AUTHORITY\NETWORK SERVICE
    Is impersonating: False
    Stack trace:    at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
   at System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.LoadXml(String xml)
   at DotNetNuke.Common.Utilities.XmlUtils.DeSerializeHashtable(String xmlSource, String rootname)
   at DotNetNuke.Services.Personalization.PersonalizationController.LoadProfile(Int32 UserId, Int32 PortalId)
   at DotNetNuke.Services.Personalization.PersonalizationController.LoadProfile(HttpContext objHTTPContext, Int32 UserId, Int32 PortalId)
   at DotNetNuke.HttpModules.Membership.MembershipModule.OnAuthenticateRequest(Object s, EventArgs e)
   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
 
If you look through the stack trace, you'll see that it's failing when it attempts to load the user's profile, and translate some XML values into a Hashtable.

So, it looks like perhaps the user's profile information has gotten corrupt?  How do I fix it, and how do I determine if any other users have corrupt profile information?

  -Josh

Narendra P wrote hi there, i guess there is one way which can work , but i am not sure about it. If you have the backup of pervious database which you have used earlier, then copy a table with the name asp_user. which is having all the user login information in the encrypted format, just copy that table and it will work fine. try this once.

I didn't quite follow what you said.  "just copy that table and it will work fine".  asp_user?  I don't see any table by that name.

Regardless, the problem appears to be because at some point between DNN 2.1.2 and DNN 4.8.2, the profiles were switched from a base64 encoded binary bytestream, and an XML document.  However, none of the profiles were transitioned from one format to the other.

I took the sledgehammer approach, and simply wiped out all the base64 encoded profiles.  That fixed the problem, but people lost their profile information.

  -Josh