Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Tim 15 posts 75 karma points
    Feb 15, 2016 @ 16:54
    Tim
    0

    Clicking dashboard icons returns error

    If we click the "Settings", "Developer", "Users", or "Members" icons on the dashboard we get an error.

    We are running ver. 7.3.7.

    The Exception Details displayed is "System.ArgumentNullException: Array cannot be null. Parameter name: bytes".

    Looking at the UmbracoTraceLog.{server}.txt file, we see the following sequence of entries: a) "The current identity cannot be converted to Umbraco.Core.Security.UmbracoBackOfficeIdentity..." (twice, one immediately following the other); b) "Login attempt succeeded for username {name} from IP address..."; c) "Starting resolution types of Umbraco.Web.Trees.TreeController"; and finally d) "Completed resolution of types of Umbraco.Web.Trees.TreeController, found 0 (took 0ms)".

    The database for the site was moved from a different SQL Server. If we just run our site, not the Umbraco back office, the site works as expected. Furthermore, one can click on the "Content" and "Media" icons and work normally.

    The exact same site and database on a different server works 100%, back office included.

    Any ideas? We are our of them ourselves.

  • Tim 15 posts 75 karma points
    Feb 15, 2016 @ 19:22
    Tim
    0

    MORE INFO:

    this AJAX call to Umbraco is failing:

    https://{server_address}/BGModern/umbraco/backoffice/UmbracoTrees/ApplicationTree/GetApplicationTrees?application=settings&tree&isDialog=false HTTP/1.1

    It is a 500 error. Here is the first line of the returned error:

    "Message":"An error has occurred.","ExceptionMessage":"Array cannot be null.\r\nParameter name: bytes"

    Thoughts anyone?

  • Tim 15 posts 75 karma points
    Feb 16, 2016 @ 02:44
    Tim
    0

    I figured out what was causing the problem. Our client's architecture is a parent/child site. The parent's web.config has used the encoderType attribute of the httpRuntime element set to use Microsoft's AntiXSS library. If I remove that attribute, the problem goes away. However, our client wants the AntiXss library to be the default encoder, so that library needs to somehow be "in the pipeline".

    Can anyone think of why having that AnitXss library would be causing that problem?

Please Sign in or register to post replies

Write your reply to:

Draft