strange errors when running???

[RLemo]

Hi ,

I am having a problem that is driving me nuts.

I made this small LabVIEW project that includes a series of vi's, and does some manipluation of a few Excel files.  The problem is that when I run the "main" vi, I get an error message that says:

An input parameter error message

[smercurio_fc]

Unfortunately, that's not much to go on. Do you have an exact error code? The "source" string should tell you which VI actually generated the error. If it doesn't, then you will need to do some debugging, such as running your code with highlight execution on, and watching the wire values until you see which VI is generating the error. Then you can look inside that VI to narrow it down further.

[RavensFan]

Not much info to go on there.

Please post a screenshot of the error message.  Also your code, if possible, so people can help debug it.

[RLemo]

Gentlemen,

Sorry for the incomplete post.  I accidentally hit the wrong key and submitted before I was done typing.

More to follow...

[RLemo]

Hi all,

Sorry for the confusion.  Let me start over.

Hi,

I am getting a LabVIEW error message that is driving me nuts.

History - I created a small project that includes a series of vi's that does some manipulation of a few Excel spreadsheets.

Problem - When running the "Main" vi, I get an error message that says: "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 @.  NI-488: Command requires GPIB Controller to be Controller-In-Charge."

Yes, I do have paths in my vi's, but they don't include any oddball characters, and NO, I'm not doing anything with GPIB.  There is no reference to it anywhere.  The vi's that give me errors are ones that run Excel Macros.

If I run through each vi individually, everything runs fine.

Any suggestions would be welcome.

Thank you.

[smercurio_fc]

Error codes in LabVIEW can sometimes mean multiple things, as the one you received shows. You got error code 1. In your case it simply means "An input parameter is invalid". The rest within that first part is giving you a possibility, though that may not apply in your case. The other part is there because the GPIB functions also generate that same error code. That doesn't mean LabVIEW thinks it's due to a GPIB call.

That said, since you said you can run the VIs on their own just fine, but not when you run them from "Main", this tells me that you are probably not feeding the right inputs to the VIs. Or, you've left an input unwired, and the default value isn't correct. For example, at what point are you creating the references to Excel and your workbooks? Are they being inadverdently closed, or perhaps not wired through in subVIs so the next one in the chain receives a null reference? You should run the code in highligh execution mode and look to see what values are fed to each Excel subVI. Better yet, have each subVI open so that you can run them on their own after you stop Main.vi once you get the error.

[RLemo]

OK.  I'll look at that.  Actually, I am using a new fresh reference that gets opened and closed in each vi.  Would I be better off just using one in the beginning, and following through all of the vi's using the same reference and closing it at the end?

[smercurio_fc]

Absolutely. It's pointless to open and close Excel with each VI.

[RLemo]

OK.  That sounds reasonable.  I'll do a bit of restructuring.  The more I think about it, the more I feel that both LabVIEW and Excel are kind of choking because I'm doing an open and close excel multiple times within a few seconds.

If I have any major issues, I'll post again here. 

Thank you for your time and help,

Bob