Quest launcher process uses random ports even though it has been sent to call.tunnel on Middleware and Monitord host machine, why?
Call.tunnel has been set so that the Middleware and Monitored host talk to each other just on port 3566 through the firewall between the machines, howebver from time to time the quest launcher process is using a random port which is not allowed within the environment that PA is running.
This is a known issue and has been raised a defect.
The issue is to be fixed in a future release of Performance Analysis for SQL Server, but as yet there is no extimated time when this version will be available.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center