Jump to content

Issue: There has been an unexpected error "The item should be found on the server tree. Child [x]. Parent [y]".


Recommended Posts


I've run into an issue that I can't seem to resolve. I've attached some screenshots of the relevant error messages. I'm trying to checkin my changes but I keep getting this message (see: Title). I've tried:

  • creating a backup of my changes and undoing all of them via Plastic (fails and prompts a popup message: The revision to reload was not found)
  • shelving the changes (fails and prompts a popup message: There has been an unexpected error "Can't find 'x' in the server. The checkin must be cancelled. This only happens if your workspace is corrupt. This is what you can do to fix it: backup your changed files, undo your workspace changes, then run an update, and finally reapply the changes manually and retry the checkin operation. If it still fails, please contact support@plasticscm.com". For more information check the server log.
    • I have attempted this fix but it has not worked for me
    • I cannot find the server log in the localappdata/plastic4/logs folder
  • checking in my changes to a different branch (fails and prompts the original issue message)
  • reimporting all assets in Unity

The only solution so far has been to checkin a few files at a time but even with that there are (unfortunately) a large number of changes, moves, deletes, and additions and this does not work or seem feasible for all of them.

As it stands I'm pretty much stuck with these changes without being able to checkin or undo. Does anyone have a workaround for this?


My current version for Unity is 2020.3.41f1 and for Plastic it's




Link to comment
Share on other sites

  • 4 weeks later...


Given the solutions you have already tried and knowing that you already backup the changes lets try to run the following command in a cmd or terminal windows pointing to the root of your workspace:

cm unco --all

Keep in mind that this will discard the changes, after this please go to the branch explorer and select one previous changeset and click "Switch workspace to this changeset" then select the latest changeset and do the same ("Switch workspace to this changeset" ). This will recreate the config files of the workspace in order to recover from the possible corruption.

If this is not helpful I would like to follow up with a ticket, please create it with an email referencing this forum post to support@codicesoftware.com.



Unity Plastic SCM Support
Virtualize your Workspace. Make it dynamic.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...