I got this error after deploying a site and running uSync. I have not found any way to fix this 🤷‍♂️

@OleAndreasMyhreOlsen I have uSync on mine too. Interesting. Taking a shot here @KevinJump you have any insight on what might be causing this result?

@OleAndreasMyhreOlsen I just spun up a minimal v14.2 site without uSync and this error still exists. It's an Umbraco issue, not a uSync issue.

Thanks for testing without uSync.

I wonder why uSync manages to create document types and content while I cannot do it as administrator?

Hi everyone,

I ran into the same problem and was able to fix it by disabling the WebDAV module for this specific web app.

<system.webServer>
   <modules>
      <remove name="WebDAVModule"/>
   </modules>
</system.webServer>

Maybe this fix will work for you as well. :)

What version are you refering to, Sebastian? Looks like web.config

I managed to reproduce the error on local machine by messing up the Id in appsettings.json

  "Umbraco": {
    "CMS": {
      "DeliveryApi": {
        "Enabled": true
      },
      "Global": {
        "UseHttps": true,
        "Id": "",
        "SanitizeTinyMce": true
        }
      },
    }
  }
}

It's the web.config file that IIS automatically generates when creating a web application. It is located in the web root directory.

I cleaned the db and deployed again, and that worked for about 2 minutes. Then the error came back.

I'm deploying to a loadbalanced environment, does that have anything to do with it?

@OleAndreasMyhreOlsen you would need to make sure that the web.config on all servers have the new web.config change proposed by @SebastianMüller

I'd love to test this as it looks like a simple fix, but just yesterday after messing with this for 2 weeks I bailed on v14 and spun this site up as v13.

@SebastianMüller what does that webdav config do in the context of Umbraco, do you know? Is it needed or does turning it off create a security vulnerability?

I have just run into this issue on a V14 website deployed on IIS. The web.config change immediately fixed the issue. Thanks Folks

is working on a reply...