Wayne Thank you very much for files. I have inpected them and it all looks fine. Network path matches, config has current path to the folder, which is typically an indication that program detected this drive as connected. When it does not see it as connected, current path to the folder would be deleted from config.
Are you sure that when you captured those two files Tonfotos did not see this dirve as connected? Is this bug 100% reproduceable or it comes and goes with time? I assume it does, since at first you were able to index files, and only later drive was shown as disconnected.
Just a wild guess, this might have to do something with the fact that your server has two names: SPECTREX360 and MYCLOUDEX2ULTRA? In the out.txt that you have sent, its network path was indicated as\\MYCLOUDEX2ULTRA\Public, but could it be that at some point of time it gets indicated as \\SPECTREX360\Public? Again, this is just a wild guess, I have nothing to prove that this is what happens. However if it would be tha case, then it would explain why Tonfotos is not be able to identify it as the same network resource.
It is possible to ask you to do another experiment? Can you please turn on logging and wait for this bug to show up again, so logs would capture this moment? Also, during that moment, can you please make another ‘out.txt’ and send it wil logs to me for analysis?
