Hi guys,
OttoFMS 4.14.0, OttoDeply 2.2.4, Windows Server 2019 Standard, dev and prod.
Like the title says, OttoDeploy fails before even starting. I mean… I click on the green button, the button title animated a bit, and then it immediately displays an error.
It took me a while to find out that the build zip with file prepared for deployment was becoming too big. While OttoFMS used to report this in the error log, it didn’t this time.
Maybe the underlying system to copy the build just does not report what the problem is.
Could you send a screenshot of the error? I don’t believe we’ve changed anything about that space check that would cause it to be an unknown error instead of a properly formatted one.
Morning Kyle,
No, since there is space enough now, I cannot reproduce this. Maybe the combination of copying a build on the dev server, and then using it as a source on the prod server, I think that mechanism is rather new. I used to make an extra web site on both servers pointing to the builds, but for some reason IIS stopped supporting http. I previously did have space errors when using a link to the build. But now I used the new mechanism which doesn’t require the url, the build is just there in the popup menu.
My 5 cents.