Issue with REST API after reload of LabView

[MKBNIS]

Hello all, I am having a curious issue with a VI I wrote awhile back, it is attached. It uses the JKI HTTP REST client v2.1.0.34, and this particular simple VI has worked fine for months. Recently the hard drive crashed on my computer, and I had to reload everything (including LabView). I also reloaded the JKI REST client tools. When I try to execute the vi now, I get the following error:

-------------------------------------------------------------------------------------------------------------------

"Error 2 occurred at lib_NI_Advanced HTTP Client.lvlib:Session.lvclass:Open Session.vi:7490001

Possible reason(s):

LabVIEW: (Hex 0x2) Memory is full.
=========================
No Listeners on the GPIB.

Complete call chain:
lib_NI_Advanced HTTP Client.lvlib:Session.lvclass:Open Session.vi:7490001
REST Client.lvlib:REST Client.lvclass:New Client Handle.vi
REST Client.lvlib:REST Client.lvclass:Create REST Client.vi
API call query R0.vi"

-------------------------------------------------------------------------------------------------------------

The GPIB issue stumped me as I have no GPIB calls in this VI. I even tried plugging in a NI GPIB-USB-HS cablem and verified it worked with MAX, and that did not help. There are no other hardware devices installed on this computer at this time. I can enter the API call over a Chrome browser, and the device responds correctly with the needed information.

I am using LabView 64 bit 2025 Q1 25.1.2f2, downloaded and installed yesterday.

Since the issue seems to be related to the new software load, can anyone please point me to other things to check? The VI loads correctly, as does the other projects with the VI, but all have the same error. I am not a trained user of LabView (have used it for about a year now however), but my other engineering duties keep my LabView time at a minimum.  Thanks for your help.

[Kyle97330]

I can't speak to the reason for the error with JKI after a hard drive crash, but I can address the "GPIB" mystery.

In the olden days of LabVIEW, pre-2000, they developed the current error system but didn't quite think it all the way through.  So when they started making error codes, they just started counting up from 1 every time they needed a new one.  Problem is, they weren't the only people to do this.  So any very low-numbered error code can have multiple meanings.

In an effort to be "helpful", if any code generates an error number, LabVIEW will look it up in its table and give you what it sees there, which can be misleading for lower numbers.

Error 2 can mean:

Memory full: Out of RAM

Memory full: Not out of RAM, but out of something else related to memory handling

Nobody home on a GPIB bus

Any one of thousands of DLLs or user-created code has put error 2 on the error chain

So, it's showing you the "Memory" error as well as the "GPIB" error, but it's really the last one in the list.

[MKBNIS · Accepted solution]

Thanks for the post, much appreciated.  I think I found a solution, but it is short term.  The LabView version I used prior to the hard drive crash was 2024Q1, and on the new hard drive I installed 2025Q1.  Today I installed 2024Q1 on the new hard drive, installed the JKI HTTP REST client, and the VI works fine in 2024Q1.

So apparently the JKI HTTP REST client does not play well with 2025Q1, but does work fine with 2024Q1.  I have no idea why.  Will fire this finding over to the JKI folks.

[MKBNIS]

Well, it gets stranger...  I have 64 bit 2025Q1, 32 bit 2025Q1, and 64 bit 2024Q1 on this computer.  All were installed in the last week on the new hard drive.  The VI would not run on 64 bit 2025Q1 and 32 bit 2025Q1 until today.  I loaded 64 bit 2024Q1 on the computer today, and it would run the VI.

This afternoon I tried running the VI again on 32 bit 2025Q1, and it ran this time.  It then run correctly in 64 bit 2025Q1.  So, installing 64 bit 2024Q1 fixed the other two installs.  Very weird....

[aeastet]

Make sure you update to LabVIEW 2024 Q3. there are some issue with LabVIEW crashing if you use the icon editor or menu file. Q1 is very unstable and crashed so much that we almost went back to 2020.