We are running 3 models on PA (Server Engine 11.0.00204) on Windows Server 2016.
After a full restart of the server machine we are occasionally facing startup problems of one instance.
Investigations are showing that one random component of PA (other instance, PA Agent) is already blocking the port of one other random instance and prohibiting a proper startup.
Workaround: Stopping the component that is causing the port block. Restarting causing and affected component with some time in-between.
Configs of all Instances are defining individual unique ports.
The affected port is setup by the following tm1s.cfg parameter
PortNumber=500XX
Searching in the CMD-Shell what is using the affected port it is showing that the ProcessID of a different PA component has established a connection to the defined PortNumber & Httpportnumber of the affected instance. Connection type "ESTABLISHED" but not "LISTENING".
Is this a know problem? Any advice on further investigations or setup changes to avoid this situation?
We can not figure out why other components of PA are blocking the port of a different instance in the first place.
help appreciated.
br, Bernhard