Error: The client has been disconnected from the server
Is this just our flaky infrastructure or has anyone else hit this error?
The workaround is just to run the migration again, it just picks up from where the failure first starts.
Best Answer
-
Tony_Collett Cireson Support Super IT Monkey ✭✭✭✭✭That kind of error can point to different issues.
Perhaps your network speed is not enough, so you may need to perform migration in chunks instead of all at once.
Or the server you are migrating from or to was disconnected briefly due to networking issues (or it simply got shutdown) causing the same interrupt.
You could try running the migration on a different server that has better performance, or unchecking the Multithreading option and only using Single Core (multithreading is very resource intensive)
5
Answers
Perhaps your network speed is not enough, so you may need to perform migration in chunks instead of all at once.
Or the server you are migrating from or to was disconnected briefly due to networking issues (or it simply got shutdown) causing the same interrupt.
You could try running the migration on a different server that has better performance, or unchecking the Multithreading option and only using Single Core (multithreading is very resource intensive)
Any news on advancing this as a workaround: https://community.cireson.com/discussion/2025/intermediate-stand-alone-machine-readable-migration-package