Error: Another Session is Accessing the FIFO

[J3liam]

Hello,

 I have been working on a LabVIEW project that works most of the time; however, when I remove power to my cRIO and turn it back on I receive an error.  The error code is -63082, the error text reads: “Possible reason(s): The operation could not complete because another session is accessing the FIFO.  Close the other session and retry.”  However, this is the only VI I am running and the issue goes away eventually and the program operates properly but I don’t know why.  Have you ever seen this error before and do you have any suggestions on how I could seek to fix it?  What confuses me the most is that the program runs properly for reasons I do not know.  Any help would be greatly appreciated.

[billko]

---

@J3liam wrote:

Hello,

 I have been working on a LabVIEW project that works most of the time; however, when I remove power to my cRIO and turn it back on I receive an error.  The error code is -63082, the error text reads: “Possible reason(s): The operation could not complete because another session is accessing the FIFO.  Close the other session and retry.”  However, this is the only VI I am running and the issue goes away eventually and the program operates properly but I don’t know why.  Have you ever seen this error before and do you have any suggestions on how I could seek to fix it?  What confuses me the most is that the program runs properly for reasons I do not know.  Any help would be greatly appreciated.

---

When you shut off the cRIO, you "lose the connection" and you have to make another one.  Create code to sense when this happens, close the old session and open a new one.  In other words, handle the error.

[J3liam]

Does this need to be done even if I shutdown LabVIEW and/or restart the computer?  Are there any example codes I could reference to close the old session and open a new session?

[aeastet]

You should always handle your errors.

If you shut down LabVIEW and restart everything then it should clear the problem. This is not the way to fix your problem however. It would be a very annoying band-aid at best.

I certainly hope you take the time to figure out how to close the last session and restart a new session when something like this occurs.

[J3liam]

I agree; however, the error persists even after rebooting LabVIEW or my computer.  So I’m confused how that can still occur when there is no other connection.  I will look into handling the error and establishing a new connection in the code.