Error trying to use Web Config Managment after upgrading from 5.1 to 5.1.1

The error is 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 neabled

<!DOCTYPE html P'.

I have tired to repair the website I get a Error while executing script. There is already an object named 'GetViewList' in the database.

Cheers

Find more posts tagged with

could_not_be_parsed

ncm_5.1.1

Accepted answers

All comments

chris.lapoint

Please open a support ticket. We'll want to try to reproduce this in house.

EducQldAust

Problem solved but couldn't find any upgrade documents to that mention to tick all options after upgrade on the configuration wizard. Myself found that skipping the database repair causes the error GetViewList when trying to repair the website only.

Also has solved the issue on the Sys.WebForms.PageRequestManagerParserErrorException. I'm awaiting for the case number / ticket number 85624. I need to create a default templete for the website, and how to reset the personalized settings back to default so any users exsperiencing this problem I can fix it for them without having to recreate there whole domain account?

EducQldAust

Does anyone have any idea how to reset the web settings template for idividual users? Now all my domain users get a no access to information service.

chris.lapoint

Can you elaborate on what you mean by reset the web settings template?

MTorok

In re to your 4:32am post: You are absolutely correct. I am updating the Release Notes to include this information. The update will be posted this evening.

Thank you.

Michael

EducQldAust

Hi Chris

Is there a way of not allowing users to customize or personalize pages and use a default template for current and new users so the graphs and custom HTML code is the same for all users?

To solve the original issue with the Config Managment page comming up with that error I had to delete all domain users out of NCM and add them back in. Is there any future features that alows to use Domain Groups?