Incomplete 'move' operation

Unity Services
,
1

I have been getting the following error message for all the files in the repository. It has happened before. It was solved by switching to legacy mode, updating there and switching back. Legacy mode was removed in some of the recent updates.

...\Plugins\ElectronicNodes\ConfigError: This item is loaded twice at
...\Plugins\ElectronicNodes\Config and ...\Plugins\LowEntryExtStdLib\Source\...\LowEntryLatentActionNone.cpp.
This can be the result of an incomplete 'move' operation.
Please remove one of the two instances.

Neither ‘Retry update’ nor ‘Update forced’ work, the problem still persist. Deleting and downloading the workspace again does not solve it either.

Any suggestions would be appreciated.

-Gabor

2

Hi,

I’m afraid I can’t fully read the error message. Could you include it completely?

Can you somehow reproduce it? Could you open a ticket at devops-vcs-support@unity3d.com so we can debug it? We may need to arrange a meeting with you.

Not sure if you tried to update the workspace via CLI. I’m guessing if it could a workaround.

Regards,
Carlos.

3

Thanks Carlos. The forum engine seems to have cut the error message above. I edited the post to make it visible.

I downgraded the app to the latest version with the legacy gui. Unfortunately using legacy mode didn’t help. I removed the workspace, deleted the config files and downloaded the workspace again. Now it seems to be working. I cannot reproduce it, but if it happens again I try CLI and open a ticket.

I’m not sure what caused this. My coworkers use old Plastic clients, while I usually update to the latest frequently. We are using Unreal Engine 5.1 with the default Plastic plugin.

-Gabor

4

Do you have any guesses about the previous steps you followed to get to this error? Could it be an incomplete ‘move’ operation? If it happens again, please open a ticket with us and we will try to arrange a meeting to debug it.

5

I didn’t move any files. Although the repo in the cloud was accidentally deleted and recreated again with the same name. I deleted the workspace and downloaded it again, but as soon as there was a change the error above happened.

6

I think somehow the fact that you deleted and recreated the same repo name was affecting you. But not sure why if you deleted and created a clean new workspace.