Error 267 occurred at System Exec.vi.

[vgezer]

Hello, 

I am trying to use impact command line to program fpga using Labview.

When I use main.vi, it calls the program_fpga.vi subVi and installs the firmware, but when I create EXE file using Application Builder and try to do the same operation, I get the following error:

Error 267 occurred at System Exec.vi. Command was "C:\EDA\Xilinx\v13_3\ISE_DS\settings32.bat C:\EDA\Xilinx\v13_3\ISE_DS\ISE\bin\nt\impact.exe -batch impact2.txt"

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (267) or for its hexadecimal representation (0x0000010B).

I executed this command (C:\EDA\Xilinx\v13_3\ISE_DS\settings32.bat C:\EDA\Xilinx\v13_3\ISE_DS\ISE\bin\nt\impact.exe -batch impact2.txt) using CMD window without error. I am using Labview 2010.

How can I solve this problem?

Thank you for your responses.

[smercurio_fc]

Did you try a search?

http://forums.ni.com/t5/LabVIEW/What-is-Error-Code-267/td-p/23804

[vgezer]

Thank you for your response.

Yes, I saw that, but it is not a problem related to EXE file. I am using this function:

Current VI's Path Function

Owning Palette: File Constants

Requires: Base Package

Returns the path to the file of the current VI. If the VI never has been saved, this function returns <Not A Path>.

This function always returns the current location of the VI. If you move the VI, the value returned changes.

If you build the VI into an application, this function returns the path to the VI in the application file, and treats the application file as a VI library.

I could not understand the last sentence. Is the path relative to the dependencies (for example, %exe_file_directory%\tests\QATests\program_fpga.vi) or only the main exe directory (%exe_file_directory%)?

[Akiel]

after reading the article on error 267 i would look at where the command is wired into the system exec.vi, there are two inputs on the top left of the icon that will accept a string, one is the command the other is working directory. I would check these are correct. If they are could you post the vi please

hope it helps 

[vgezer]

Hello,

I solved the problem. Actually I removed Vi's path function (since this was the problem for EXE file) and unfortunately, I needed to add a absolute path (such as C:\file.txt). I don't know why Labview dont accept a file in its current folder without any path.