thanks for confirming it bane

admin this must be a vshare bug then as this doesn't happen when done manually from command line, will this be fixed for vshare 2.6 as it will greatly reduce the time taken to convert and server resources used.