editing pages, paragraphs in backend

Frederik Gadegaard

Posted on 12/01/2021 15:52:37

Hi,

I am getting this error page whenever I click on any of my pages in backend, or right-click -> click properties:
This happens on every page across languages andwebsites, and also right-click-> properties on folders produces error.
Also it seems like I am able to create new pages and delete them only being the edit part that seems to fail.
Editing websitesettings also works without any problems.
And the thing is that I see the pages in the frontend without any issues and I can navigate the content tree and see all the content.

F12 network expection:
(the Page with ID 39 I triple checked is in the database Page table).

This only started to happen when I was finished creating my content tree locally and then wanted to move to my clients test server.
I deployed my custom code to a newly created IIS application and restored the sql database that I had been working on. I could browse to the /admin page, start a new trial license, browse the site(s) and also go the backend which also seemed to work except the above problem.

OBS: one thing to note is that locally my sql database version was 2019 and when I tried to back it up and restore it on the server, I found the server using a sql v. 2016 which I then couldnt restore the newer backup on -> therefore I needed to back it up using a generated script (including both sceme and data, and specifying version of sql server to the target version, 2016) which In my view is just a different way of restoring the data. And script ran fine and looking through the tables it all seems to be there.

Additional information:
DW version is 9.9.3
.NET framework 4.7.2
sql server 2016
using a trial license (shouldnt mean anything)
tried in edge, chrome (and chrome inkognito)
using https (but with an invalid certificate)

I would appreciate all help or even just a way to try to debug this "paragraphList.aspx" which seems to be the one that fails. Like how to you usually go about debugging that?

Kind regards

Frederik

PS. I have attached an example of a row of a page that fails to load/being edited as an excel document

PageId39_cannotBeShown.xlsx

Replies

Imar Spaanjaars

Posted on 12/01/2021 16:33:29

>> I needed to back it up using a generated script (including both sceme and data, and specifying version of sql server to the target version, 2016) which In my view is just a different way of restoring the data. And script ran fine and looking through the tables it all seems to be there.

Most likely this is where your error is. Recreating the database is definitely not the same as restoring a backup.

I would use a tool like Red Gate's SQLCompare or SQL Data Compare to compare the two databases. It seems likely that you find missing data in the database that's hroken (nulls, where non-nulls are expecrted).

Cheers,

Imar

Frederik Gadegaard

Posted on 13/01/2021 11:48:12

Hello again,

It doesnt seem to be differencies in database tables that is creating this issue. (used Red Gate SQLCompare to look for differences and didnt find anything worring me)

And also I found out that it is not only editing of pages. Also editing of a user (finding a user and clicking on the user to see details / edit details):

And also going to Settings -> System -> Solution Report also generates an error:

And still having the issue of editing a page (right-click on page -> properties):

And I cant seem to find a common thing of these errors - accept it involves editing in a way. I can however edit websitesettings for example.

Is there a way to debug these .aspx files? Like PageEdit.aspx?

I can also give access to the backend of someone would like to have a look.

Kind Regards
Frederik

Nicolai Pedersen

Posted on 13/01/2021 12:03:15

Hi Frederik

I am affraid your database is 'damaged' somehow - not sure we can do a lot for you. I would recommend that you make a new copy. It can anything from primary keys, identities etc.

Try this guide: https://www.mssqltips.com/sqlservertip/2810/how-to-migrate-a-sql-server-database-to-a-lower-version/

Frederik Gadegaard

Posted on 13/01/2021 16:16:43

I managed to fix the issues. It was not database related afterall.

But I am not 100% what exactly fixed it, but I made some changed to the web.config:

I had this:

<httpRuntime
executionTimeout="600"
maxRequestLength="512000"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100"
enableVersionHeader="false"
requestValidationMode="4.5" ----> OBS: changed this back to 2.0 (less validation than 4.5)
targetFramework="4.7.2"
requestPathInvalidCharacters="<,>,*,%,:,\,?"
maxUrlLength="2000"
relaxedUrlToFileSystemMapping="true"
/>
</system.web>

And I removed the below section completely

<system.web>

<httpRuntime

targetFramework="4.7.2"

executionTimeout="600"

maxRequestLength="512000"

useFullyQualifiedRedirectUrl="false"

minFreeThreads="8"

minLocalRequestFreeThreads="4"

appRequestQueueLimit="100"

enableVersionHeader="false"

requestValidationMode="2.0"

requestPathInvalidCharacters="<,>,*,%,:,\,?"

maxUrlLength="2000"

relaxedUrlToFileSystemMapping="true"

</system.web>

</location>

The idea of this path specific configuration was to add more validation generally to browsed pages but skipping validation in admin related paths.

Im unsure why this caused the error since we have had the same settings in the old solution setup (dw8 and .net framework 4.6.2) but it seems to consitently remove / introduce the error when I removed and added this setting to the config.

I dont know if this is the full answer but I am not pursuing this issue anymore for now.

You must be logged in to post in the forum

Developer forum

editing pages, paragraphs in backend

Replies