Hi, this is strange. We fixed this bug in NeoLoad 5.1 and checked that the Server replacement is done with the latest version. Can you confirm that you use a recent version?
If this is the case, can you contact the support and send your Project for more investigations?