ReferenceError: oid is not definedYYYY-MM-DDTHH:MM:SS - info: installerLogFile: C:\Users\<user name>\AppData\Local\Temp\vcsaUiInstaller\installer-yyyymmdd-hhmmss.logYYYY-MM-DDTHH:MM:SS - info: networkLogFile: C:\Users\<user name>\AppData\Local\Temp\vcsaUiInstaller\network-yyyymmdd-hhmmss.logYYYY-MM-DDTHH:MM:SS - info: [AppComponent] Locale initialised: EnglishYYYY-MM-DDTHH:MM:SS - info: [AppComponent] Product: vcsaYYYY-MM-DDTHH:MM:SS - info: [AppService] Using cached ovfOptionsYYYY-MM-DDTHH:MM:SS - info: [AppComponent] version.js buildnumber: 24185845YYYY-MM-DDTHH:MM:SS - info: [AppComponent] App runtime buildnumber: 24185845YYYY-MM-DDTHH:MM:SS - info: [AppComponent] Build numbers matchedYYYY-MM-DDTHH:MM:SS - info: [AppComponent] Found ovftool with correct version from the discovered pathYYYY-MM-DDTHH:MM:SS - debug: The file does not exist: E:\vcsa\gateway_type.jsonYYYY-MM-DDTHH:MM:SS - info: [AppComponent] Saved OVA folder path: E:\vcsaYYYY-MM-DDTHH:MM:SS - info: [AppComponent] Saved ovftool path: E:\vcsa\ovftool\win32\ovftool.exeYYYY-MM-DDTHH:MM:SS - debug: wizardTitle: Restore - Stage 1: Deploy vCenter ServerYYYY-MM-DDTHH:MM:SS - debug: ovaFileNameRe: /.*_OVF10.ova$/YYYY-MM-DDTHH:MM:SS - debug: files in E:\vcsa: VMware-vCenter-Server-Appliance-8.0.3.00400-24322831_OVF10.ova,ovftool,version.txtYYYY-MM-DDTHH:MM:SS - info: ovaFile: E:\vcsa\VMware-vCenter-Server-Appliance-8.0.3.00400-24322831_OVF10.ovaYYYY-MM-DDTHH:MM:SS - debug: path:sftp://<backup server IP/FQDN>:<port>/<backup directory>/vCenter/sn_<vCenter Server FQDN>YYYY-MM-DDTHH:MM:SS - info: backup location:<backup server IP/FQDN>:<port>/<backup directory>/vCenter/sn_<vCenter Server FQDN>YYYY-MM-DDTHH:MM:SS - error: ReferenceError: oid is not definedYYYY-MM-DDTHH:MM:SS - debug: ReferenceError: oid is not definedThis issue is caused by the key exchange algorithms used by the remote SFTP server hosting the backups. Due to ssh2 packages part of vCenter Server Installer being version 0.8.9, it is not able to work with these key exchange algorithms
This issue is resolved with vCenter Server 8.0 Update 3e Build 24674346. Refer to VMware vCenter Server 8.0 Update 3e Release Notes
As a workaround, implement the steps below: