Error 2

[mrbean]

I'm using LabVIEW 2009, and I've modified the Calling System Exec.vi (found in the \examples\comm).  I added a tab and in that tab I call various openssl command-line calls.  I was able to perform the "openssl dgst -sha1 file.txt" just fine, then it stopped working.  Instead, now I get the dreaded Error 2 with possible reasons of (1) LabVIEW: Memory is full, or (2) NI-488: No Listeners on the GPIB.

Every so often, the call will work, but I have no explanation.  These are some of the files.  One is from the Tools:Profile:Performance and memory.  The other is the VI and the error png.  Any help would be appreciated.

[Broken_Arrow]

Are you acessing your LAN in order to perform any of these operations? I have had that error when our LAN is overloaded (at least the Memory Full, not sure about the "2").

[mrbean]

I'm connected to our network, but I think all the VIs, etc that I'm referencing are on my d-drive.  I do see the calls work every so often, but today it's failing more often than not.  The LAN theory makes sense (sort of).

[Broken_Arrow]

To troubleshoot, try to host an OpenSSL session on your D:.

[mrbean]

As I'm struggling with nearly every aspect of this, can you provide any guidance on how I would "host an OpenSSL session"?  I have an openSSL.exe (created by a different developer on a different project) that I'm calling via command line.

[richjoh]

I too getting error code 2 now and don't have a way to fix this, LV2010. In my case, a file is FTPed from an instrument to the working PC, then sysexec gzip command is issued to unzip the file. Unziping fails and the indicator error cluster reports error 2. Below is a paste. I am using Windows XP also Vista. I worked fine in the paste now is consistent reporting error 2. Does anyone know how to work around this?

"

Error 2 occurred at System Exec.vi. Command was "gzip\gzip.exe -vdf data.ps.gz"

Possible reason(s):

LabVIEW:  Memory is full.
=========================
NI-488:  No Listeners on the GPIB.

"

[richjoh]

OK I fix the problem myself. the sysexec commands needs the full path (not relative path) when issuing the command. It needs c:\gzip\gzip.exe... not gzip\gzip.exe...