Copied to clipboard

Flag this post as spam?

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

  • Joseph 32 posts 146 karma points
    Sep 11, 2019 @ 12:41

    Vanishing License - Umbraco v7.14.0 / Translation Manager v2.4.0

    Hello, We are currently noticing that the license details are intermittently vanishing from our pre-live environment on a site being developed.

    At first it was thought this may be related to deploys, but it also seems to spontaneously vanish overnight when no deploys would have taken place.

    Site in question is running Umbraco v7.14.0, and Translation Manager v2.4.0.

    Are there any known issues or previous experiences where things like this have occurred? As far as we can tell the license is not a physical file and is stored within the DB / CMS... so shouldn't need to be included in any build process, etc.

    The pre-live environment does have authentication / IP restrictions / redirect rules in place, so not sure if that could potentially be a factor. The environment is using flexible load balancing with a defined master server. Translation Manager health checks all pass. We cannot detect anything in the Umbraco logs for this as well - but if there is some configuration amends available to increase the level of information then we are happy to include it if pointed int he right direction...

    Any insight welcome...

  • Kevin Jump 1753 posts 11262 karma points MVP 4x c-trib
    Sep 11, 2019 @ 12:46
    Kevin Jump


    the licence is stored in a physical file. There should be a translationManager.licence.config file in the config folder of the site.

    just to be sure you should add this file to deployments so it's always there.

    there are no restrictions other than domains, so that shouldn't be an issue.

    you can if you need to increase logging levels for translation manager by adding the following to the log4net.config file

      <logger name="Jumoo.TranslationManager">
        <level value="DEBUG" />
  • Joseph 32 posts 146 karma points
    Sep 11, 2019 @ 12:56

    Many thanks for the response Kevin.

    Not sure how we overlooked that file, but spotted it now and gotten it included in the deployments / build. Added in the logging configuration as well so we can monitor this prior to launch.

Please Sign in or register to post replies

Write your reply to: