LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error -124201 using WEBDAV Delete

The LabView 2016 WebDav delete gives me an unknown error -124201.  This only happens after the 1st time I call it after re-running my main VI.  In LV2015, this was working reliably.

 

Once the error is thrown, the path I'm trying to delete on my PXIe RT controller still exists.

 

This post appears to be related or the same issue and was referenced as a known issue CAR#517393, but no workaround or resolution was indicated.  Does anyone know of a workaround?  This issue hamstrings my design in a big way (Previously verified and long released code).

 

I need to reliably delete a path and all of its files on an RT controller.  I use WebDav because it has better authentication and because there's no FTP equivilant funciton for recursive and rapid deletion of a path.

 

Thanks,

 

XL600

0 Kudos
Message 1 of 3
(3,775 Views)

Some more troubleshooting has revealed this may not be related to the WebDAV CAR.  I switched to an FTP based deletion and found that I cannot delete the same files that were giving the WebDAV Delete VI trouble.

 

This appears to be happening on all my TDMS files.  Even though I call TDMS close, neither my RT controller, WebDAV, nor FTP can delete the files until the RT VI has terminated.  It's as if the TDMS close VI isn't working, when in LV2015, this process was well established and working for months.

0 Kudos
Message 2 of 3
(3,726 Views)

Update: A full day of troubleshooting and it turns out to be a dumb mistake.  A VI was being used (A TDMS indexing VI designed to scour TDMS files and generate a lookup table of channel names and start/stop sample numbers for rapid random access across spanned TDMS files) which was not closing all references.  The WebDAV and FTP errors were so cryptic there was no way to know that the files were simply still open.  There's also no tool on the RT side to show which files are open and by what (Unless someone knows of such a tool?).  Regardless, problem solved.

Message 3 of 3
(3,711 Views)