This issue occurs if you have changed or deleted the transfer scope in NSX manager and vCloud Director database is not updated with the new value. When vCloud Director attempts to communicate with NSX to create the new network, it calls with a vdnscope that no longer exists.