The filename, directory name, or volume label syntax is incorrect power automate

I have a program that accepts command line arguments.

Show

The scheme I've adopted is that every command line argument is shaped like this:

-x::argument

where x is a letter that stands for a switch ( like a mode of operation, and argument is an argument that goes along with that switch ).

:: is my separator.

I ran into a problem with the following command line:

If I run the following directly from Windows command line:

"C:\Test\Program.exe" "-c::C:\Documents and Settings\maciej\Desktop\Measurement and Automation\test\current.cfg" -m::a 

All works fine.

If I try to use the System Exec.VI:

And pass the following string to it

cmd /c "C:\Test\Program.exe" "-c::C:\Documents and Settings\maciej\Desktop\Measurement and Automation\test\current.cfg" -m::a 

I get the error as in the title of the post.

Does anyone have any ideas how to make it work from System Exec?

It seems that system exec parses the:

"-c::C:\Documents and Settings\maciej\Desktop\Measurement and Automation\test\current.cfg"

part ... figures that this is not a file name ... I don't want it do to that I know it isn't but it is still a valid cmd argument for me.

Maciej

The filename, directory name, or volume label syntax is incorrect power automate

Part Number: MSP-EXP430G2
Other Parts Discussed in Thread: ENERGIA, MSP430G2553, , MSP-EXP430FR5994

I ran the blink example on my board a couple days ago with no problem but today no code (not even blink) will upload to the microcontroller giving me this error message

Energia: 1.8.11E23 (Windows 10), Board: "MSP-EXP430G2 w/ MSP430G2553"

C:\Users\USERNAME\Documents\energia-1.8.10E23-windows\energia-1.8.10E23\hardware\energia\msp430\cores\msp430\atof.c: In function 'atof':

C:\Users\USERNAME\Documents\energia-1.8.10E23-windows\energia-1.8.10E23\hardware\energia\msp430\cores\msp430\atof.c:71:9: warning: floating constant exceeds range of 'double' [-Woverflow]

Sketch uses 810 bytes (4%) of program storage space. Maximum is 16384 bytes.
Global variables use 20 bytes (3%) of dynamic memory, leaving 492 bytes for local variables. Maximum is 512 bytes.
MSPDebug version 0.24 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2016 Daniel Beer <>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
----------------- NOTE ------------------
Modified version of mspdebug for Energia
Do not use standalone
-----------------------------------------
Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc.

Using new (SLAC460L+) API
MSP430_GetNumberOfUsbIfs
MSP430_GetNameOfUsbIf
Found FET: HID0023:COM5
MSP430_Initialize: HID0023:COM5
Firmware version is 20409001
MSP430_VCC: 3000 mV
MSP430_OpenDevice
MSP430_GetFoundDevice
Device: MSP430G2xx3 (id = 0x00de)
2 breakpoints available
MSP430_EEM_Init
Chip ID data:
ver_id: 5325
ver_sub_id: 0000
revision: 00
fab: 60
self: 0000
config: 00
Device: MSP430G2xx3
MSP430_Run
prog: 'C:\Users\USERNAME\AppData\Local\Temp\arduino_build_179844/Blink.ino.hex': The filename, directory name, or volume label syntax is incorrect.
MSP430_Close
An error occurred while uploading the sketch

I've already tired updating the drivers and that didn't solve the problem.

    Problem description

    NAS backup fails with the filename, directory name, or volume label syntax is incorrect error.  You might encounter this error at the initial stage of the Windows NAS backups.

    You get the following errors:

    • message="Failed to ping node server :" RPCcallattemptedonclosedRPCclient="unsupported value type"

    • Unable to do OpenDir" Path=\\?\A:\

    • message="Error processing TLog entry"

    • "CreateFile \\\\?\\A:\\Marketing\\Internal\\00_Contracts\\Druva On Site\\Contract Renewals-Pricing\\~$Druva On-site Renewal Analysis 2021.xlsx: The device is not ready.

    • "Backup Failed" error="open \\\\?\\A:\\: The filename, directory name, or volume label syntax is incorrect."

    Cause

    You might get many errors if the Share is not accessible from the NAS proxy. 

    Resolution

    1. Access the following share path from the Nas proxy:
      Start > Run > Path (\\<ServerIP>\Sharename)
    2. Map the share on NAS proxy by selecting the same account (username and password) which is mentioned for backups in the credential store.