Client hangs on further searches after the first one

When I open the client (old or new) and press enter on the Search-field (without any content), it returns to me quite quickly a good list of objects. I can work with all objects, no problem there. But when I go back to Search-field and press enter the second time, the waiting-bar appears and the search just never ends, at least as long as I have patience to wait for it to finish. The only way to recover is to kill the client and restart it, then I am able to do one search again, but after that same thing...

Any ideas why this might happen and what could I do to debug and/or fix it? Same thing happens in my local laptop server (so no networking outside of my laptop) as well as separate windows server computer (which I access over VPN). These are quite new vaults so not that much data in them yet so data amount shouldn't be an issue. It becomes quite frustrating to try and do any development as I have to kill and restart the client constantly.

Regards,

- Petri

Parents Reply Children
  • There is a VAF application maintained by me running in the vault so I am sort of suspicious that it could be somehow caused by it, but I can't figure out why it would be participating in the search functionality at all as I don't think there is any event triggering which would run any of my code at that specific moment when the second search is executed.

  • Can you disable the VAF application, restart the vault, then try again?  That'd enable you to confirm your suspicions.  Anything in the Windows Event Log?

  • uhm, this is actually a very old phenomenon. If I remember correctly, even M-Files 9 had it. The solution is just go back to mainpage and do the search again.... Or when you cant, just right click the icon and open a new window and continue from there

  • Well, yesterday everything worked fine and fast! So I don't suspect my VAF anymore as I was testing and developing it several hours. My suspicion now is that when the hanging appeared, I did actually start few largish JSON-file mapping updates to some external objects (with HOT) so maybe that combined perhaps with indexing was the cause in jamming the search. It might be that it had finished all that yesterday and that's why it worked very smoothly.

    So this seems to be very random problem, but I have had it every now and then and it just might be related to some HOT-update stuff (or not). When the jam happened, I was able to continue my development just by using F5 to refresh the display as that didn't jam, just had to be careful not to execute full search at any moment.