2.11 local asset migration

Hi,
Installed 2.11 this morning and the local workspace default was to an external hard drive location (not sure why), but in any case, when I attempt to relocate the path to my existing asset library location, I just get an error saying ‘migrate failed’ without any explanation. I have ensured that the external D drive is available just in case, but no change.

please advise, thanks

Hi @mcdermoa

Please generate a log file, and send it to support@d5tecs.com and have it titled ‘2.11 Clov-Forum 2.11 Local Asset Migration

Let me know if you have done it.

Log files have been sent

Hi @mcdermoa

This issue was addressed in the recent update last Friday. It was also evident on my end but I can now migrate the workspace successfully without the error prompt. Please try again.

Hello @Clov,

I updated as instructed, did full restart, but the problem persists. Please advise.
Can you give me a step by step of what you are doing to ensure I am duplicating your process to migrate my local library? It appears to be a straight forward step, just one really, but just in case.

thank you

also, I have already reexported a log file and sent along as well.

@Clov,

Unclear if this is related to the on-going issue, but I just opened a different file and I am getting this warning. Not enough space?

I cannot be certain yet, but it would appear where the workspace files are stored has insufficient memory space, which would make sense given the current path, which I cannot reroute, it not huge (not small, but apparently not big enough).

Hi @mcdermoa

Can you send me the D5 Launcher log files, too? Let me know if you’ve done so.

I was able to confirm that the issue was not file space, but the path. The external drive was not connected when the error occurred. Once reconnected, I was able to update all assets, but again, to this incorrect location. Log file sent.

Hi @mcdermoa

I’m trying to locate your email, can you share it to me via forum direct message so I can pick it up right away

Please download the latest version of the launcher from our official website. This new version has addressed this issue.

Please try and let me know.