Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice
  2. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  3. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Starting Unity 2019.3.0a12 (64-bit): No Valid Unity Editor license found.

Discussion in '2019.3 Beta' started by dgoyette, Aug 19, 2019.

  1. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    4,193
    I just installed 2019.3.0a12 to test something, but I get this dialog every time I try to open it:

    No Valid Unity Editor license found. Please contact your Administrator.

    I searched and didn't find anything on this. Has anyone else encountered this, or know how to resolve it?

    The following is from the Editor log file when trying to start up, if it helps:

    [Licensing::Module] Successfully connected to LicensingClient on channel: LicenseClient-Dan
    Entitlement-based licensing initiated
    [LicensingClient] Licenses Updated successfully in LicensingClient
    LICENSE SYSTEM [2019819 11:33:35] Next license update check is after 2019-08-20T15:38:53


    LICENSE SYSTEM [2019819 11:33:35] 00325-95800-00000-AAOEM != 00325-96173-11796-AAOEM

    Built from 'trunk' branch; Version is '2019.3.0a12 (b073d123dd5d) revision 11563985'; Using compiler version '191627012'
    OS: 'Windows 10 (10.0.0) 64bit' Language: 'en' Physical Memory: 16253 MB
    BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 0
    Exiting without the bug reporter. Application will terminate with return code 0
     
    Isfean likes this.
  2. Deleted User

    Deleted User

    Guest

    It's a known problem; I think the Hub devs are working on it.

    In the meantime, delete "Unity_lic.ulf" that is in "C:\ProgramData\Unity", quit the Hub entirely from the tray, restart it and re enter you licence data.
     
    dgoyette likes this.
  3. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,589
  4. dgoyette

    dgoyette

    Joined:
    Jul 1, 2016
    Posts:
    4,193
    Thanks, all.
     
    Peter77 likes this.
  5. st33d

    st33d

    Joined:
    Jan 22, 2014
    Posts:
    28
    The solution described does not work for me. It still comes up with the same error.
     
  6. MadeFromPolygons

    MadeFromPolygons

    Joined:
    Oct 5, 2013
    Posts:
    3,967
    Same here. Stopped using that version and went back to a11 for now.
     
  7. charlesb_rm

    charlesb_rm

    Joined:
    Jan 18, 2017
    Posts:
    485
    2019.3 beta 1 contains a fix for the license issues. Please let us know if that solved your problem or not.
     
    Matin- and MadeFromPolygons like this.
  8. MadeFromPolygons

    MadeFromPolygons

    Joined:
    Oct 5, 2013
    Posts:
    3,967
    It did for me! Many thanks to any team members who got that fix out!
     
    charlesb_rm likes this.
  9. Deleted User

    Deleted User

    Guest

    Sorry for grabbing your arm like that! What about 2019.4 alpha? :)
     
  10. charlesb_rm

    charlesb_rm

    Joined:
    Jan 18, 2017
    Posts:
    485
    Next TECH release is 2020.1 and the alpha will start soon.
    2019.4 will be the LTS version for 2019 and will not contain any new feature.
    See this blog post for more details about TECH and LTS releases.
     
    Deleted User likes this.
  11. Deleted User

    Deleted User

    Guest

    Ah, okay, thank you. :)

    So ,no new alpha before January 2020? :(
     
  12. charlesb_rm

    charlesb_rm

    Joined:
    Jan 18, 2017
    Posts:
    485
    we already have some alpha builds but they are meaningless as they don't contain any new feature yet
    as soon as we have something of value and stable enough to play with, we are going to release it (before January!)
     
    optimise and Deleted User like this.
  13. Deleted User

    Deleted User

    Guest

    :D