Several customers and MS engineers reported me recently some very long collect statements scenarios using version 10.15 and sometimes infinite ones.
1) Some bugs were indeed identified in some VBS queries which might create looping scenarios in some VBS query execution .These bugs were so fixed.
2) A long collect statement can occur also when .VBS queries (belonging mainly to the “Server Info” query category) are running too long time.
MBV 10.15 enumerates indeed in some .VBS queries some registry keys or registry values, and when targeting several remote servers of the BizTalk group it can be sometimes long.
I decided so to implement a timeout mecanism to stop a VBS, .BAT, or .CMD query after 30 secs by default.This timeout value can be changed of course in the MBV UI via the "VBS/BAT/CMD Query Timeout" Global Option.
3) When you have a long query situation or infinite one, please do the following :
- Note in the status bar of MBV UI the pending query (it will be also logged in the Status log file)
- Kill MBV (as stopping via the UI the collect statement during a query execution will NOT work, I don’t want to kill my query execution thread)
- Keep the generated status log file and send it to me later (it is precious for me to know what happened before MBV was killed)
- Restart MBV and then uncheck the queries which seem to run too long or infinite and then start a new collect statement (usually these queries should belong to the “Server Info” category) to exclude them from the collect statement
Current build 10.15.7777 available on this blog contain both the VBS queries fix and the VBS Query Timeout implementation.
Sorry for these introduced regressions and continue to send me your feedbacks or possible bugs found