Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error after upgrading to DNN V 5.00 - Invalid JSON primitiveError after upgrading to DNN V 5.00 - Invalid JSON primitive
Previous
 
Next
New Post
1/31/2009 6:37 AM
 

Hi,

we recently upgraded from DNN 4.9 (?) to DNN 5.0.0 and have been getting the following error when a use logs into the database.

Some portals work ok, but other Portals throw either this error or "Failed to load view_state"

Any suggestions would be appreciated

Regards

Peter

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.ArgumentException: Invalid JSON primitive: .

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[ArgumentException: Invalid JSON primitive: .]
   System.Web.Script.Serialization.JavaScriptObjectDeserializer.DeserializePrimitiveObject() +541762
   System.Web.Script.Serialization.JavaScriptObjectDeserializer.DeserializeInternal(Int32 depth) +242
   System.Web.Script.Serialization.JavaScriptObjectDeserializer.BasicDeserialize(String input, Int32 depthLimit, JavaScriptSerializer serializer) +51
   System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit) +37
   System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(String input) +70

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +0
   System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) +71
   System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) +261
   System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +29
   DotNetNuke.UI.Utilities.Reflection.InvokeGenericMethod(Type Type, String MethodName, Object Target, Object[] Args) +247
   DotNetNuke.UI.Utilities.MSAJAX.Deserialize(String Data) +182
   DotNetNuke.UI.Utilities.ClientAPI.GetClientVariableList(Page objPage) +159
   DotNetNuke.UI.Utilities.ClientAPI.GetClientVariableNameValuePair(Page objPage, String strVar) +13
   DotNetNuke.UI.Utilities.ClientAPI.GetClientVariable(Page objPage, String strVar) +9
   DotNetNuke.UI.WebControls.DNNMenu.LoadPostedJSON() +76
   DotNetNuke.UI.WebControls.DNNMenu.OnInit(EventArgs e) +85
   System.Web.UI.Control.InitRecursive(Control namingContainer) +333
   System.Web.UI.Control.AddedControl(Control control, Int32 index) +198
   System.Web.UI.ControlCollection.Add(Control child) +80
   DotNetNuke.UI.Skins.NavObjectBase.InitializeNavControl(Control objParent, String strDefaultProvider) +140
   DotNetNuke.UI.Skins.Controls.Nav.OnInit(EventArgs e) +29
   System.Web.UI.Control.InitRecursive(Control namingContainer) +333
   System.Web.UI.Control.InitRecursive(Control namingContainer) +210
   System.Web.UI.Control.AddedControl(Control control, Int32 index) +198
   System.Web.UI.ControlCollection.Add(Control child) +80
   DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) +598
   System.Web.UI.Control.OnInit(EventArgs e) +99
   System.Web.UI.Page.OnInit(EventArgs e) +12
   DotNetNuke.Framework.PageBase.OnInit(EventArgs e) +268
   System.Web.UI.Control.InitRecursive(Control namingContainer) +333
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +378

[PageLoadException: Exception has been thrown by the target of an invocation.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +277
   DotNetNuke.Framework.PageBase.OnError(EventArgs e) +330
   System.Web.UI.Page.HandleError(Exception e) +84
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6776
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +242
   System.Web.UI.Page.ProcessRequest() +80
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Server Error in '/' Application.

Invalid JSON primitive: .

 


Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

 

 

 
New Post
1/31/2009 1:25 PM
 

Delete your browser cookies and cache, and make sure MS AJAX is installed on the server. Thanks...



Alex Shirley


 
New Post
2/1/2009 5:11 AM
Accepted Answer 

Hi,

thanks for the suggestion, I'll try it.

Can't see where AJAX is installed, i read somewhere that it is installed automatically as part of dotNet 3.5 SP1, which is already installed.

Have already cleaned the local and ISA network caches.

Will try again and see how it goes.

Regards Peter

 

 
New Post
2/1/2009 5:30 AM
 

Hi,

thanks for the suggestion, I'll try it.

Can't see where AJAX is installed, i read somewhere that it is installed automatically as part of dotNet 3.5 SP1, which is already installed.

Have already cleaned the local and ISA network caches.

Will try again and see how it goes.

Regards Peter

 
New Post
2/1/2009 7:00 AM
 

Hi Alex,

thanks for the suggestions, still no luck.

Might be due to permissions of mismatched source files.

Getting different problems with various portals.

Cheers Peter

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error after upgrading to DNN V 5.00 - Invalid JSON primitiveError after upgrading to DNN V 5.00 - Invalid JSON primitive


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out