List Folder VI does not match patterns correctly on a network drive

[ACIDIX]

I try to filter a file list on a network drive by pattern using the List Folder VI. This worked fine in LV7.1.1.

Upgrading to LV8.5 or higher the pattern matching does not work any more.

The code I use is:

Example:

Y: is a network drive mapped with "net use" command on a windows XP machine.

DOS dir command of test folder "temp":

 Verzeichnis von Y:\temp

27.04.2013  12:33    <DIR>          .
27.04.2013  12:33    <DIR>          ..
27.04.2013  12:05                 0 Test1.dat
27.04.2013  12:05                 0 Test1.txt
27.04.2013  12:05                 0 Test2.dat
27.04.2013  12:05                 0 Test2.txt
               6 Datei(en)              0 Bytes
               2 Verzeichnis(se),  6.550.585.344 Bytes frei

With an empty pattern in LV7.1.1 the file names array contains all files:

Test1.dat
Test1.txt
Test2.dat
Test2.txt
Test3.dat
Test3.txt
 

Filtering for *.dat files (pattern = "*.dat") works as exspected, file names array contains:

Test1.dat
Test2.dat
 

All good with LV7.1.1 ! (don't worry about the file size of 0, I just created some demo files - same with other files).

The same code used in LV8.5, 8.6, 2010 works also if pattern is empty. But the file names array is empty when using the same pattern *.dat as before.

It works if a local drive or an USB attached drive is used, but not on a network share.

I found something similar in the posts about problems when using some more or less special characters in filenames on a network drive, but here no special chars have been used. I consider this to be a LV problem, as it worked in LV7.1.1.

[Adilo]

Is it possible to attache your VI or at least a screenshot of your VI to your next post?

This would be very useful!

[ACIDIX]

Sorry, I added a picture below the "The code I use is:" line but the board deleted it. (Now I know that one has to use the insert image function instead of copy & paste ).

The code is quite simple, just the list folder VI from the palette and minimum controls..

I'll attach a zip with the demo test files, the VIs and some screenshots.

Thanks.

[Adilo]

Both VI seem to work pefectly with LabVIEW 2012 and 2011.

I really can't tell you why this problem appears.

The only difference I could find in your sceenshots was the fact that you were using capital and smaller letters in the path control. But this shouldn not be the problem

Honestly, I don't think that it is a bug due to the fact that it won't work in LabVIEW 2010 either.

I will install LabVIEW 8.5 to see if I can trigger your problem there.

[Adilo]

Works perfectly fine with LabVIEW 8.5!

Your LabVIEW insallation may be corrupt.

I'm going to send you a pm with a clean reinstall tutorial.

[rolfk]

The possibly most important information about this is not there. What server filesystem is the mapping from? If it is a Windows server, which version of Windows and which fileformat on the server and if it is a Unix server, what Samba version (or other network file sharing software) is used and what filesystem?

[Adilo]

Did my advise work for you?

I'm looking forward to your feedback.

Regads, Adilo

[ACIDIX]

Thank you for dealing with my problem.

I'm a little bit stunned at the moment because today it works with all LV versions (7.11, 8.5., 8.6, 2010) on my machine; but I'm not connected to my home network this week.

I would not like to do a complete clean re-install at the moment because that may take at least 1 day to complete (multiple LV versions, different DAQ-MX and traditional drivers and some extra packages).

I'll test again next week if it's an issue related to my home network and reply again.

rolfk asked about what server:

The first time I recognized the problem was with a network connection to an ICY-Box external disk (Samba).

Then I tried to repeat the problem with a mapped drive on a WIN7 machine in the same network. Same problem.

Also same problem with a VPN connection to a windows server2003 share.

Today I checked in an other office with a WIN7 machine and also with the windows server 2003 connection -it works.

So I have to check again when I'm back at home.

Thank you so far, I'll give an update next week.