When can Obtain Notifier return error 1?

[jdoyle]

I am getting an error 1 from the following invocation of Obtain Notifier:

Facts:

• THis is running in a built EXE.
• Instance Name is empty, so the Name input is just "QuitN".
• The notifier "QuitN" is known to exist.
• create if not found? is F in this case.
• The element data type is a varient constant.
• The failure has persisted for several days at a single installation.  Prior to this, there was no problem.  Other sites are not experiencing this problem

What conditions can lead to the error 1?

[jdoyle]

I should add that this is LabVIEW 8.6.1.

[A_Person]

From the LabVIEW 8.6 Help General Error Codes, an error 1 generally indicates an invalid parameter.  However, I was able to run that code as an executable without receiving the same error.

Can you provide any more details on anything that coincided with the program not working?  Did anything change on the customer's system when they started receiving the error?

[F._Schubert]

Are you really sure the notifier exists? The behaviour of sporadic occurance hint that there might be some sort of syncronization problems. Maybe something different goes wrong which in turn prohibits the first Obtain notifier or leads to a immediat release of the notifier, but this primary error is somehow overwritten by the error you're seeing.

[waldemar.hersacher]

Your error 1 may not come from Obtain Notifier.

In the case that error in (no error) has already an error it is passed through.

[A_Person]

Even if a notifier does not exist, that should return error 1100.  Waldemar's suggestion is probably the most likely.

[jdoyle]

Thanks to all those who have responded so far.The error is not on the incoming wire.  The error message (source) specifically says that the error occurred in Obtain Notifier.  And yes, we know the notifier exists.  Also, no, we can't repro it in-house; it normally works just fine.  The reason I posted the question was that, although error 1 is a documented possible error from Obtain Notifier, there is no explanation of how this error can be caused, since just about all inputs are valid, except the ones that specifically cause other errors, like 1100.