2 Replies Latest reply: Jun 30, 2011 9:42 AM by Paul Kelly RSS

    IE Explorer Hanging

    Paul Kelly

      Our users now access their QliKView reports via 64 bit terminal servers (Windows Server 2008 R2).


      This is a recent change as we have just moved to Active Directory.


      We have the 32 bit IE Plugin installed and are having to force via a VB Script the loading of the report via 32 bit Internet Explorer.


      I am doing this via the following script...



      Option Explicit
      Sub Main()
            Dim ie : Set ie = CreateObject("InternetExplorer.Application")
            ie.Navigate "qvp://"

      ie.visible = true

      ie.Left = 0
      ie.Top = 0
      ie.width = 1024
      ie.height = 768
      End Sub
      Sub Force32bit()
        If InStr(UCase(WScript.FullName), "SYSTEM32") > 0 Then
               Dim objShell : Set objShell = CreateObject("WScript.Shell")
                objShell.CurrentDirectory = "C:\Windows\SysWOW64"
                objShell.Run "wscript.exe " & WScript.ScriptFullName, 1, False
            End If
      End Sub



      The issue we have is that IE is regularly hanging and my feeling is that it may be something to do with this script.


      I am sure that there are other users out there who have 64 bit servers who have to use IE 32 bit.


      How do you guys access your reports?

        • IE Explorer Hanging
          Patrick Laredo



          our servers are 64 bit, users PCS 32 bit xp with qv plug-in installed locally. All access is via the plug-in directly from PC (laptops or workstations) to server using the qvp protocol. All the machines are in the AD which uses trusted domains. We don't access via terminal servers - we used that as a workaound during the migration to the AD for users whose machines were still outside the domain as we use NT authentification. But is was only temporary.

          We're on v8.5

          • IE Explorer Hanging
            Paul Kelly



            We upgraded our server installation to QlikView 10 64 bit and utilised the ODBC CONNECT32 command (We only have 32 bit drivers for our database)...


            This has solved the problem and users no longer hang - looks like it was a server issue.