IBM Support

QRadar: Troubleshooting IMM Remote Viewer (Virtual KVM) issues



When connected to the Integrated Management Module (IMM), the user cannot connect to a remote viewer session by using the IMM Remote Control.


As you attempt to access the Integrated Management Module (IMM), you may see:
  • Errors when trying to connect to the IMM.
  • Failure to launch the IMM application.
  • The remote viewer application window opens and closes with an error message.

Resolving The Problem

For the following issues, perform these steps on the machine you are using to connect to the IMM.

ActiveX Client Issues:

If you are unable to connect the IMM through the Microsoft® IE ActiveX:

  1. Download Active X Cab file.
    1. Type the following address into a Firefox browser's address bar: 
      https://[IMM IP address]/designs/imm/aessrp/
    2. After the page loads, right click in the page and choose the option: "Save Page As..."
    3. You should be prompted to save the page as "", click Save.
      Note: This does not work in Chrome or IE.
  2. Extract files from the file to a temporary folder.
    1. In Windows 10, you may be able to right click and open with Windows Explorer.
    2. Alternatively use a 3rd party tool like 7Zip to extract the files.
  3. Open the Command Prompt in Administrator mode.
  4. If there are existing IMM cab files in C:\Windows\Downloaded Program Files\, move those files to a temporary folder:
    md c:\temp\IMMCabFiles\
    cd C:\Windows\Downloaded Program Files\
    move IMM* c:\temp\IMMCabFiles\
    move RP_*_DLL32.dll c:\temp\IMMCabFiles\
    move RPClient* c:\temp\IMMCabFiles\
    move tbb.dll c:\temp\IMMCabFiles\
  5. Copy the previously extracted files to C:\Windows\Downloaded Program Files\
    cd C:\Windows\Downloaded Program Files\
    copy C:\[path_to_extracted_files]\* C:\Windows\Downloaded Program Files\
  6. Run the following command: regsvr32 /s IMMViewerClient32.ocx


Java® Client Issues

If the IMM is unable to load:

NOTE: Server returned HTTP response code: 405 - - For Java®  8 update levels greater than 192, the error is seen on any subsequent attempt to start the Remote Viewer without first clearing Java temporary files.  The workaround is to delete the temporary Java files. The next attempt to connect to the remote viewer should be successful.  The fix involves uninstalling the higher Java application and install no later than Java® SE Runtime Environment 8 Update 192.

For example, jre-8u192-windows-x64.exe (find the version that matches the OS you are browsing from)

  1. Open the Java Control Panel (Configure Java).
  2. From the general tab, open Settings, then click Delete Files to remove all temporary files.
  3. Click to check Installed Application and Applets as well at Cached Application and Applets, then click OK.
  4. Startup new Java Client Remote Control session from the IMM.

If the IMM Java Client window opens & closes immediately with no errors:

  1. Open the Java Control Panel (Configure Java).
  2. From the general tab, open Settings, then click Delete Files to remove all temporary files.
  3. If still failing:
    1. Delete temporary Java files again.
    2. Uninstall all Java applications from Windows Installed Apps, then reinstall Java 8 Update 192 (or lower).


If the IMM Java Client displays an error, Duplicate Exists:

This occurs when there is a jp2launcher already running. Open task manager, find the process jp2launcher.exe, and kill this process. After the process is killed, launch the IMM again.

If there is a Java Security Restriction:

To resolve this, open the Java Control Panel (Configure Java) then Security, add the IMM URL to the exceptions list: https://[IMM IP Addr].


The Java Viewer has terminated

This error shows up after the Java applet downloads and after the windows shows "Connecting to KVM Server". This is typically the result of ports 3900 and 5900 being blocked, while port 443 is accessible.

  IMM Remote Control - Connecting to KVM Server  -->   IMM Remote Control - Connection Error
  1. Test the connection of the port from the Windows host that is being used to open the browser to connect to the IMM.
  2. Use Test-NetConnection in Windows Powershell to test the connection to the https port.
    Test-NetConnection [IMM-IP] -port 443
  3. Testing port 443 should be successful as the browser is already connecting to the IMM. Once this shows success, test the ports for KVM, Storage, and Remote  Control:
    Test-NetConnection [IMM-IP] -port 3900
    Test-NetConnection [IMM-IP] -port 5900
  4. If any of these port connection tests fail, the ports need to be opened between the IMM and the remote host being used to open the Web browser to the IMM.

Note: Port 3389 is used for Ethernet over USB support and may need to be open for firmware updates when booting to the QRadar firmware update ISO.

Reference: QRadar xSeries Appliances: Integrated Management Module (IMM) Common Ports

Document Location


Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
05 May 2021