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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Host Portal Editing Error in 5.6.2Host Portal Editing Error in 5.6.2
Previous
 
Next
New Post
3/30/2011 8:18 PM
 
Hi Sebastian,
Thanks, I think your response is about the general compression problem.
But because of that I stopped using compression a couple of months ago.
This error in editing portals looks to be located in one stored procedure.
DotNetNuke.Modules.Admin.Portals.SiteSettings.cmdUpdate_Click(
The number of parameter values do not match with the number of parameters in the list.
I am going to try and debug this and see if I can see what is wrong there.
Regards,
Fred
 
New Post
7/22/2011 4:55 AM
 
I'm getting the same error in 5.6.3 when trying to search for users.

uncaught exception: [Exception... "'Sys.WebForms.PageRequestManagerParserErrorException: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled. Details: Error parsing near '<!DOCTYPE html PUBLI'.' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x8057001c (NS_ERROR_XPC_JS_THREW_JS_OBJECT)" location: "JS frame :: chrome://firebug/content/spy.js :: callPageHandler :: line 744" data: no]
 
New Post
7/22/2011 7:17 PM
 
John Cant wrote:
I'm getting the same error in 5.6.3 when trying to search for users.

uncaught exception: [Exception... "'Sys.WebForms.PageRequestManagerParserErrorException: Sys.WebForms.PageRequestManagerParserErrorException: The message received from the server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled. Details: Error parsing near '

 John;
Please log this in Gemini - http://support.dotnetnuke.com - list your DotNetNuke Edition and the Version, steps you take to get this error  message and the error message itself.

Thank you;


Ken Grierson
DotNetNuke Corporation
Test Lead
 
New Post
7/25/2011 8:29 AM
 
My installation suffers from the same bug. I upgraded to 5.6.3 much too fast, i.e. with too little checking. I had to have a version with an editor without issues, because I'm training the staff of the Khmer news website in data-entry and the rad editor in 5.6.3 had most of its issues fixed.

I've been installing my new module multiple times on multiple pages. When editing the settings, I might get this when trying to enter the settings or after I've saved the settings. Only after recycling the application pool, will the application function again. Since most modules I installed in the new demo site were newsdesk modules, I thought my development was the cause. Only after I noticed the same error with other modules and other portals, did I realize my module may not be the cause of this. This thread puts me at ease.

... at ease? I mean that the problem is not my doing. But at the same time, this occurrence is very worrying. I do realize the resources that a version 5.6.4 will require, but 5.6.3 is worse than 5.6.2 and no version to conclude DNN 5 series with. I did not testrun 6.0.0 yet, far too busy with the NewsDesk development, but from what I read in this forum, 6.0.0 has enough issues to justify waiting for 6.0.1.
BTW, when entering module settings, I also encounter this error:

DotNetNuke.Services.Exceptions.ModuleLoadException: The stored procedure 'dbo.RemoveTermsFromContent' doesn't exist. ---> System.InvalidOperationException: The stored procedure 'dbo.RemoveTermsFromContent' doesn't exist. at System.Data.SqlClient.SqlCommand.DeriveParameters() at System.Data.SqlClient.SqlCommandBuilder.DeriveParameters(SqlCommand command) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.DiscoverSpParameterSet(SqlConnection connection, String spName, Boolean includeReturnValueParameter, Object[] parameterValues) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSetInternal(SqlConnection connection, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelperParameterCache.GetSpParameterSet(String connectionString, String spName, Boolean includeReturnValueParameter) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.ExecuteNonQuery(String ProcedureName, Object[] commandParameters) at DotNetNuke.Entities.Content.Data.DataService.RemoveTermsFromContent(ContentItem contentItem) at DotNetNuke.Entities.Content.Taxonomy.TermController.RemoveTermsFromContent(ContentItem contentItem) at DotNetNuke.Entities.Modules.ModuleController.UpdateModule(ModuleInfo objModule) at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.cmdUpdate_Click(Object Sender, EventArgs e) --- End of inner exception stack trace ---


____________________________________
The one-eyed in the land of the blind.
 
New Post
7/25/2011 12:41 PM
 
Marc,
Which NewsDesk module are you using?

Ken Grierson
DotNetNuke Corporation
Test Lead
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Host Portal Editing Error in 5.6.2Host Portal Editing Error in 5.6.2


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