Copied to clipboard

Flag this post as spam?

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


  • Harrison Fleetwood 26 posts 191 karma points
    Oct 11, 2019 @ 16:31
    Harrison Fleetwood
    0

    uSync import "Failed" message

    Hi,

    We have uSync v8.2.3.0 installed on an Umbraco 8.1.5 installation.

    uSync works fine on our staging environment, any changes made on dev can be imported in to staging, but on the production server when we click the "Import" button, we just get a Failed message.

    There's no errors logged in the Log Viewer, and looking in dev tools it's just a generic:

    500 - Internal Server Error There is a problem with the resource you are looking for, and it cannot be displayed.

    We don't have any special setup with this, it's the same way we've installed uSync on all our projects and never had any problem.

    Is there a way to get more verbose logging for uSync errors in v8? Not sure how to enable debug messages like we could in v7.

  • Kevin Jump 1534 posts 9805 karma points MVP 3x c-trib
    Oct 14, 2019 @ 08:45
    Kevin Jump
    0

    Hi,

    it sounds like you might have an issue with missing dlls or files as the error is fairly generic - might be best to just confirm the production server has the uSync8 dll files that are in your staging environment.

    I think all errors are logged by Umbraco as a minimum so there should be something in the log for the 500 error even if there aren't any uSync ones?

    I haven't truly gotten to grips with how the logging config in v8 works at the moment but i think adding

    <add key="serilog:minimum-level:override:uSync8" value="Debug"/>
    

    to the serilog.config file will turn on the debugging logging for uSync.

  • Harrison Fleetwood 26 posts 191 karma points
    Oct 14, 2019 @ 10:30
    Harrison Fleetwood
    0

    I've double checked that the uSync DLLs have gone up correctly, and everything looks identical to Staging. Weridly the reporting functionality works fine on Production, and it reports the changes correctly that are awaiting import.

    I enable the debug logs, and that doesn't shine any more light on. I can see uSync starting up fine on app restart, and the report method logs everything fine, but absolutely nothing is logged in regards to the failed Import.

    If I set debug to true in web.config on production, I get a little more insight in to the error. Checking dev tools, the error is:

    PUT https://nualtra.thetestingsites.co.uk/umbraco/backoffice/uSync/uSyncDashboardApi/import 500   - angular.js
    

    With xhr.send(isUndefined(post) ? null : post); being the offending line.

  • Kevin Jump 1534 posts 9805 karma points MVP 3x c-trib
    Oct 14, 2019 @ 10:35
    Kevin Jump
    0

    Hi

    is there anything in the network tab of chrome dev tools, the 500 should be coming from the server and is probably passing a bit more info that hopefully would show up in the network tab

  • Harrison Fleetwood 26 posts 191 karma points
    Oct 14, 2019 @ 11:02
    Harrison Fleetwood
    0

    The only thing that comes from the network tab is the generic 500 error

    500 - Internal Server Error There is a problem with the resource you are looking for, and it cannot be displayed.

  • Harrison Fleetwood 26 posts 191 karma points
    20 days ago
    Harrison Fleetwood
    0

    We managed to get a little further in to the error, but still unsure as to the issue.

    HTTP Error 500.21 - Internal Server Error Handler "WebDAV" has a bad module "WebDAVModule" in its module list

    We tried removing the WebDAV module in the web.config, but then that leads to another 500.21 error:

    Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagePipelineHandler" in its module list

    The server is the clients own hosting. We've checked and the modules are installed on the server. Just wondering if there's anything obvious we're missing?

    This is on Windows Server 2019.

  • Harrison Fleetwood 26 posts 191 karma points
    20 days ago
    Harrison Fleetwood
    0

    Resolved this this morning.

    In the IIS Configuration Manager I went through the WebDAV settings, in particular the authoring section, and the enabled flag was set to True. I set it to False, and it fixed the issue.

Please Sign in or register to post replies

Write your reply to:

Draft