Loading...
Loading...
The Windows operating system provides C:\Windows\System32\recovere.exe. The Windows PATH includes C:Windows\System32 C:\Windows\System32>set | findstr PathPath=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\TShell\TShell\PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\C:\Windows\System32> When the recover.exe is not located in the current working directory, the Windows Operating System relies on the Path to retrieve the executable from. This results in the command failng with C:\Windows\System32>.\recover -vvv -d C:\Test -S <ssid> -I -Invalid parameter - -d
The Windows Path environmental variable lacks the path to the NetWorker binaries or is not ordered correctly with C:\Windows\System32 ahead of the path to the NetWorker binaries.
As directed in the NetWorker Administration Guide. For Windows hosts only, to ensure that you use the NetWorker recover.execommand and not the Windows OS recover command, perform one of the followingtasks: Ensure that NetWorker_install_path\bin appears before %SystemRoot%\System32 in the $PATH environment variable. When you start the recover command include the path to the binary. Forexample: NetWorker_install_path\bin\recover.exe
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.