LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

file dialog error 43 happens for no apparent reason.

Solved!
Go to solution

I was running a program over and over again (dozens of times) with no problems and all of a sudden I got an error 43 from file dialog. When I get this error a box pops up saying the following:

 

"Error 1 occurred at Open/Create/Replace File in Write Spreadsheet String.vi->Write To Spreadsheet File (string).vi->20120816 multi Cycle IV trace with auto delay.vi


LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.

P:\R&D\Studies\Test Logs\log IV-S178-protoA5-2-H5-
GB-ARD-1-dark--201209071512.txt"

 

As far as I can tell I haven't changed the file path or put in characters that are not allowed. And every time I run the program now I get this error.

What should I do about this? I'm totally stumped.

 

Thanks for your help,

0 Kudos
Message 1 of 15
(5,874 Views)

Hi all,

 

My program is working again for no apparent reason.

I cleared all the fields and ran the program and it worked. Then I typed the exact same filepath that gave me the errors before and it worked.

 

That's labview for you, errors that pop in and out of existance for no apparent reason.

 

Thanks anyway though.

 

This forum is the only way to learn labview...

0 Kudos
Message 2 of 15
(5,871 Views)

edCubed wrote:

That's labview for you, errors that pop in and out of existance for no apparent reason..


LabVIEW is very deterministic in these scenarios. These observations are typically typically caused by PEBCAK errors.

 

Can you give us a little more information and maybe show us some code?

 

  • Are you entering the path in a path control or in a string control? (big difference!)
  • If it is a string control, is it set to "limit to single line"?
  • Is it set to "update while typing"?
  • What is your OS?
  • Does your program contain local variables of the path/string control?
  • Do you have parallel code sections, possibly causing race conditions?
  • ...

 

0 Kudos
Message 3 of 15
(5,853 Views)

Thanks for replying,

 

I'm actually having the same problem again and getting the same error, so it seems the problem may be more serious than I thought.

 

To answer some of your questions:

 

*The only input I have going into my file dialog VI is the "default name" input. This input is a string made of appended strings from front panel

controls.

* I don't have "limit to single line" or "update while typing" set. I didn't know these were options I can set. How do I set up these options?

* I'm running windows 7, and I don't think I'm using characters that are not allowed in file names.

* I'm not using any local variables in my program.

* There may be race conditions going on. But i'm not sure they would cause problems even if they exist.

 

I've attached a copy of my code to this post. The problem happens before anything in the for/while loops is executed. So you can ignore all that code.

 

 

0 Kudos
Message 4 of 15
(5,829 Views)

I just tried using "limit to single line", "update value while typing", and I tried disabling "enable wrapping". None of these worked.

 

0 Kudos
Message 5 of 15
(5,823 Views)

Error code 43 indicates that an action was canceled by the user.  Did you hit Cancel in the Open File Dialog?


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 6 of 15
(5,818 Views)

An error message appears as soon as I run the program. The following message is generated:

 

"Error 1 occurred at Open/Create/Replace File in Write Spreadsheet String.vi->Write To Spreadsheet File (string).vi->20120816 multi Cycle IV trace with auto delay.vi

 

Possible reason(s):

LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.

P:\R&D\Studies\Test Logs\log IV-S178-protoA5-2-H5-GI
-ARH-1-dark--201209100946.txt"

 

 

At this point I have the option to "stop" or "continue" running the program.

 

If I choose to continue I get another error message:

 

 

"Error 1430 occurred at Open/Create/Replace File in Write Spreadsheet String.vi->Write To Spreadsheet File (string).vi->20120816 multi Cycle IV trace with auto delay.vi

Possible reason(s):

LabVIEW:  The path is empty or relative. You must use an absolute path.

<Not A Path>.txt"

 

I then have the choice to "continue" or "stop" again. regardless of the choice I make here the program stops running.

 

 

 

I'm going to see if I can rearrange the code to remove any race conditions but I'd appreciate any help you can give me.

 

0 Kudos
Message 7 of 15
(5,814 Views)

To clarify: An error occurs when the file dialog vi is executed. I am not given the option to choose a file path, it just generates an error which is passed

to the write to spreadsheet vi giving me the error message I posted above. I don't know why the file dialog vi isn't working. maybe there is a setting

there which is incorrect or I wired insufficient information to it.

0 Kudos
Message 8 of 15
(5,808 Views)

That's labview for you, errors that pop in and out of existance for no apparent reason.

 


This is simply a refusal to admit that computers do exactly what you tell them to do. 😉

 

What goes in between the two dashes: "dark--201209100946.txt" - seems like something is missing?  Maybe something is wrong with the way you generate the pieces of the path.

 

I'd start by sticking probes on the wires on the controls that are used to concatenate the path.  Next, I'd probe the wires coming from the VI(s) that generate the path components.  Is P:/ a network drive with an OS that could possibly generate illegal characters in the file name?

 

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 9 of 15
(5,806 Views)

Hi ed,

 

maybe you could create a simple VI with just the file dialog VI to test it's behaviour?

 

- In the mean time you could also check, why you create a "standard name" for the FileDialog including a ".txt" suffix and then, after the FileDialog, you again append a ".txt" suffix to the filepath. You append that suffix without any error checking - is this intended?

- You should use "Build Path" instead of ConcatString whenever you're dealing with file path to minimize risk of errors...

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 10 of 15
(5,804 Views)