0 Replies Latest reply: May 18, 2017 5:01 PM by Vamsi Vandavasi RSS

    Qlik proxy Shared persistance DMZ issues

    Vamsi Vandavasi

      Hi

       

      we recently upgraded from 3.1.1 to 3.2.3 to Shared persistance model. we have one central node and one proxy node. Proxy node is in DMZ server. Accessing QMC and Hub from central node is working fine. Accessing Hub from Proxy Node is haveing problems. we are seeing constantly loading button screen but nothing is diaplyed. when we checked firewall we are seeing tcp resets. we are engaging network team to ses if network is detecting any span and terminating connection.

       

      I would like toknow if any of you having issues like this from 3.2.3 version shared persistance if this is a bug or something. bwlow is the log message we are seeing constantly in provy dmz server log.

       

       

      17720170518T132052.855-0700WARNQDTCQPROXY01System.Proxy.Qlik.Sense.Communication.Communication.Tcp.StreamFactory29847d5d0c-7b3b-4ecf-9104-0b052466cbc1Domainname\qlikadminaccountError during stream authentication as serverAn existing connection was forcibly closed by the remote host↵↓Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.   at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)↵↓   at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)↵↓   at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)↵↓   at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)↵↓   at Qlik.Sense.Communication.Communication.Tcp.StreamFactory.<>c__DisplayClass8_1.<Negotiate>b__2(IAsyncResult result)847d5d0c-7b3b-4ecf-9104-0b052466cbc1
      17820170518T132052.855-0700WARNQDTCQPROXY01System.Proxy.Qlik.Sense.Communication.Communication.Tcp.StreamFactory29e37cce94-4b30-4e18-ad57-56a8cf0acc5bDomainname\qlikadminaccountAbove happened because:An existing connection was forcibly closed by the remote host   at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)↵↓   at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)e37cce94-4b30-4e18-ad57-56a8cf0acc5b