PAM Servers are upgraded to v3.1.1
PAM Client/Browser is launched on Windows Server 2012 R2.
At the Access Page, all access methods are not launched and no exception is displayed on screen.
PAM Client on Windows Server 2012 R2
Windows Server 2012 R2 had Remote Access Service enabled which listens on TCP 3389 port (to be more specific, TCP/0.0.0.0:3389).
PAM Client also listen on the same port (to be more specific, TCP/127.0.0.100:3389) and would conflict with Remote Access Service port.
Due to this port conflict, PAM Client's Access Methods did not initialize correctly impacting all Access Methods(RDP/SSH/VNC...)
Port conflict need to be resolved.
As a workaround, Windows Server's Remote Access Service port can be changed.