jmundl 0 Report post Posted June 6, 2019 Hi all, I reinstalled WAPT Pro with new build May 28, 2019. After re-installation I can't communicate with performance counters via SNMP protocol. Best Regards, Jiri Quote Share this post Link to post Share on other sites
sergei 0 Report post Posted June 10, 2019 Hi Jiri, What counters do you use? Do you import the counters from an old scenario or create the new from scratch? Quote Share this post Link to post Share on other sites
jmundl 0 Report post Posted June 10, 2019 Hi Sergei, this scenario was prepared and used in previous build of the WAPT Pro. All performance counters worked correct. Then I reinstalled WAPT Pro, and result Performance, table Performance counters was empty for SNMP counters. I tried test this counter with button "Test server connection ...", but I became error message "SNMP initialization failed. The request timed out. [0xA0041001]" The same result for new created counter. Best Regard, Jiri Quote Share this post Link to post Share on other sites
sergei 0 Report post Posted June 11, 2019 It seems a little bit strange. I have double checked and for me it works good. Could you give me your scenario? Quote Share this post Link to post Share on other sites
jmundl 0 Report post Posted June 11, 2019 Hi Sergei, I send scenario with SNMP problem. Best Regards, Jiri TestB1.wpsx Quote Share this post Link to post Share on other sites
jmundl 0 Report post Posted June 11, 2019 Hi Sergei, I tried test performance counters (SNMP) in previous version WAPT Pro (4.7) on the same PC - there is connection OK. For WAPT Pro 5.0 test ends with described error. I tried install WAPT Pro (last version) on different PCs (as demo version), by all these installations occur SNMP connection failed. These demo installation were after tests uninstalled. Is there any possibility to check, what process can have any reason to this problem(log file, for example)? Now I tried previous version WAPT Pro 4.7 - without any problem. Best Regards, Jiri Quote Share this post Link to post Share on other sites
jmundl 0 Report post Posted June 13, 2019 Hi Sergei, problem was solved. The problem was caused with the connection of the network cable to a second network card with another IP. Sergei and Ivan, thank you very much for your cooperation. Best Regards, Jiri Quote Share this post Link to post Share on other sites