Forum Discussion
MicrosoftAnnoucement: Updated Network Assessment Tool released on 12/8 - added network connectivity checks
The current version of this tool appears to be very broken; after changing the number of iterations to the desired amount (2000 in the below example), only about one quarter of the results are processed with the results analyser - the rest are skipped.
Looking at the source results file, it's clear that only tests with around 850 packets sent / received are processed, and that any tests with around 280 packets sent / received are skipped;
I've tested this thoroughly and can see no logic as to why it utilises 250ish packets sometimes, and 850ish others. This isn't a configurable variable.
Any chance of getting this fixed?
Kind regards
Ben
I have noticed the same issue with tests being run with either 250-ish or 850-ish packets in a 3:1-ish ratio. I was thinking this was potentially an indication of an issue with my ISP but now seeing this reported by someone else I too wonder if it's an issue with the tool.
+1 to issues with the new version. Several attempts on multiple machines results in 283 packets sent/received. When trying to use resultsanalyzer, it claims:
"Error: No data in input file. Please check that at least one record exists."
This is despite the fact that the TSV file has 10 rows of data.
For attempts that result in 800+ packets (851 seems to be the magic number for perfect), resultsanalyzer will skip rows with 283 packets sent/received. I've tried modifying the relay IP to several different ones (13.107.8.2, 13.107.65.5, 104.44.195.1, and 52.114.188.1) and results don't improve.
Is this a tool issue? Or a relay issue? Seems to be the former...
hello rovert506 William Looney - What was the fix for the "ERROR: No data in input file. Please check that at least one record exists." I've tried with one and multiple iterations only to encounter the same error. Uninstalled and reinstalled tool didn't help. I never encountered this error on the initial release of this tool, only on the updated versions included the latest as of this post.
- I had the error on the initial release. I had it initially on the 1.1 release until I uninstalled all previous versions. After that no error. http://lynciverse.blogspot.com/2017/12/hands-on-with-updated-skype-for.html?m=1
