Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. Dismiss Notice

Bug Checkin and Update Merge issues citing 'proper permissions' or license manager

Discussion in 'Unity Version Control' started by LilGames, Sep 5, 2023.

  1. LilGames

    LilGames

    Joined:
    Mar 30, 2015
    Posts:
    511
    Starting about a week or two ago I've been running into this error when trying to check in pending changes or Update Workspace.

    In Unity:
    upload_2023-9-5_15-8-51.png

    In Plastic client:
    upload_2023-9-5_15-8-38.png

    In the log, the only useful part seems to be this:
    2023-09-05 15:32:06,143 EVERY_USER_OR_GROUP Server:[REDACTED] FATAL LicenseManager - Limited by days evaluation licenses are not available anymore

    What does that mean? I pay for Unity. used to pay for Teams seats too but that got replaced with DevOps. There's nothing else in the logs that seems pertinent; nothing about file paths.
     
    Last edited: Sep 6, 2023
  2. LilGames

    LilGames

    Joined:
    Mar 30, 2015
    Posts:
    511
    ... And this doesn't happen with other project repos. Just one in particular.
     
    Last edited: Sep 6, 2023
  3. LilGames

    LilGames

    Joined:
    Mar 30, 2015
    Posts:
    511
    Steps taken:
    Uninstalling and reinstalling the Plastic Client did nothing.
    Inspecting and updating repo user and user group assignments and permissions did nothing.

    Here's how I worked around this:
    • I renamed my local project folder then checked out a fresh and complete download of the entire project from the repo.
    • Opened both versions of the project in separate instances of Unity
    • In the "old" version I viewed what files were in "Pending Changes" and then:
    • ... copied those files over manually to the "new" project (luckily less than 20 files, but still...)
    • Checked in changes in the "new" project and now this is where I will continue to work.
    This really seems like a local file problem that Plastic didn't know how to deal with and the logs didn't provide details about.
     
  4. carlosalba1985

    carlosalba1985

    Unity Technologies

    Joined:
    Jul 19, 2021
    Posts:
    799
    This error happened due to an old bug that was fixed a time ago. What was your Plastic SCM version the first time this issue happened?
    The error was not permissions releated but the workspace metadata was somehow "broken".

    The problem is once this error appeared, the only good solution was deleting the workspace and recreating it on the same path. This way, you won't be able to redownload the project but re-cache it on disk.
    Remember to backup the pending to checkin changes you may have.
     
  5. LilGames

    LilGames

    Joined:
    Mar 30, 2015
    Posts:
    511
    The package version was 1.17.x when the bug happened, installed via a git path since the official package lists 1.15.18 as most recent and recommended, for some reason. After the above steps to recover, I reverted to 1.15.18. Should I stick to this one or update to UVC 2.x ? I am using Unity 2021.3.5.
     
  6. carlosalba1985

    carlosalba1985

    Unity Technologies

    Joined:
    Jul 19, 2021
    Posts:
    799
    You should update to the very latest version. It should be compatible with your Unity version.
    If something similar happens again, please open a ticket with us at devops-vcs-support@unity3d.com.
    We may need to arrange a meeting with you or at least review your client logs in detail.

    Sorry for the inconvenience.
     
    LilGames likes this.