This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
I have generated a Customized Standalone Command Line Package.
I can execute the default command from my local drive but not from the network drive.
On the network drive, something with the path is wrong.
This is the error I get:
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
C:\Windows\user_files\configs\f28027.ccxml
I use the windows power shell to call the bat file.
.\dslite.bat
Hello,
The issue is that the dslite.bat file to execute the standalone package has calls to CMD which does not support UNC paths.
Hence there are two options.
The first (and recommended) one is to simply map your network drive to a drive letter. The open powershell to the directory using a drive letter instead of an UNC path.
The second is to modify the bat file so that the command is run from powershell instead of cmd.
Thanks
ki