How to overcome the "Downloading settings from server failed" error


Store settings on server allows clients the ability to store their Trader Workstation (TWS) settings/configuration on the cloud and retrieve them at anytime from another computer. This feature allows you to use the layout of a specific user on two or more machines.

In some specific circumstances, the operation which stores/downloads the settings to/from the cloud may fail and the following error message may appear shortly after the TWS has loaded on the screen:



 How to overcome this error message?

 The underlying causes of this message are usually the following:

  • ACCESS TO THE LOCAL MACHINE IS BLOCKED: A security setup, such as a firewall or antivirus, prevents the access of this computer to the cloud storage. This prevents TWS from accessing the remote server, thus disallowing the settings file upload or download. Recommended workaround: set up an exception on the firewall or antivirus in order to exclude the TWS executable file (c:\Jts\tws.exe) or the entire TWS folder (C:\Jts) from the real time security scan. The procedure to set an exclusion may vary, according to the software you are using, therefore we recommend consulting the user guide or the on-line documentation of your specific security program.
  • ACCESS TO THE REMOTE SERVER IS BLOCKED: A firewall or proxy service blocks the communication with the cloud storage through the network on which this computer is. In this scenario, you (or your IT / Networking departments, in case you do not have the rights for such an operation) can modify the firewall or proxy settings to allow the computer to communicate with the cloud server on the TCP port 443. For additional details about the hosts/ports which needs to be allowed for the proper TWS operation, please see as well the section "DESKTOP TWS" of KB2816. Please refer to the documentation of your specific software in order to create specific rules for your firewall or proxy system.


See KB2323 for instructions on how to restore TWS settings from external storage
See KB2320 for instructions on transferring settings from one user to another


How to check and solve connectivity issues affecting the Trader Workstation (TWS)


The Trader Workstation (TWS) software needs to connect to our gateways and market data servers in order to work properly. Connectivity issues affecting your local network or your Internet Service Provider network may negatively affect the TWS functionality. In this article we will indicate how to test your connectivity using an automated connectivity test web page.


How to test the connectivity using the automated "IB Connectivity Test" web page?

1) Click on this link: 

2) Please wait until all the tests have been completed and results have been displayed. If you see "Success" as outcome for all tests, your connectivity to IB Servers is reliable at the present moment. No additional connectivity troubleshooting or configuration should be needed.

3) If you see "Fail" as outcome for one or more test/s, please click on the link "Fail" itself in order to display the "IB Network Troubleshooting Guide". That section will help you conduct some manual tests to identify the cause of the failure.

Note for Corporative environments and Proxy server users: the automated "Connectivity Test" page may return misleading results in case your machine is accessing the Internet through a Proxy server. This usually happens if you are connected to a company network. If this is your case, we kindly ask you to contact your Network Administrator or your IT Team and ask them to perform a manual connectivity tests towards the destination servers indicated in the table on the top of the IB automated "Connectivity Test" web page itself. The manual connectivity test should be conducted using destination TCP ports 4000 and 4001. Should they prefer to have the server list in another format or should they need to set up the firewall / IP Management rules, you can forward them this page.


How to Reset the IB Key app


This procedure can be used to fix different issues, one of them being the display of "Update" message on the IB Key home screen after an app upgrade. This solution has proved to work as well in case of "generic_error" message being displayed during the IB Key activation process.



The procedure is independent from the operating system and model of your smartphone.

1. Launch IB Key

2. Tap on the icon "Settings" on the bottom toolbar

3. Tap on the button "About"

4. Tap rapidly 5 times on the version number. Please notice that the version number on your screen does NOT have necessarily to correspond to the one in the screenshot below.


5. If the action at point 4. has worked as expected, some technical detail lines will be displayed within the lower part of the screen.


6. Tap on the icon "Settings" on the bottom toolbar

7. Tap on the button "Debug Mode"


8. Tap on the button "Reset Application"


9. Tap on the button "Reset"


10. A confirmation message will be displayed.Now you can tap on the button "Back to Start"


11. You can now reactivate the IB Key using the "Enable User" button. If the IB Key was in an activated status prior to the cache cleaning, you would need to call the IB Customer Service in order to obtain a Temporary Code to be used during the "Enable User" procedure.


Instalación de Java 8 para MAC OS X Yosemite


Este artículo describe cómo instalar el entorno Java necesario para ejecutar la versión independiente de Trader Workstation X de IB para el Mac OS X 10.10 Yosemite. Tenga en cuenta que los usuarios de la versión basada en navegador de la Trader Workstation de IB no requieren pasos adicionales para operar la aplicación.

Para utilizar la aplicación independiente de la Trader Workstation X en una computadora Apple Macintosh, es necesario que el sistema tenga una instalación de conjunto de desarrollo Java (JDK). Si, tras la actualización a la versión más reciente de OS X, su sistema operativo ya no reconoce el JDK instalado anteriormente, por favor, siga los pasos siguientes:

  1. Vaya a la página de descargas de Oracle JDK.
  2. Acepte el acuerdo de licencia.
  3. Descargue el JDK más reciente para Mac (indicado en la tabla como Mac OS X x64)

Una vez se haya completado la instalación, Trader Workstation X debería lanzarse sin problemas.


TWS Standalone does not launch in Win 7 / Java 8 - MS Security Updates

This article is intended to instruct clients on how to regain usage of the Desktop/Start Menu icons.


After a recent round of Microsoft Security Updates, Windows 7 users who have installed Java 8, can no longer launch the TWS application from the TWS Standalone icons located on their desktops.

The icons do not respond when activated (double-clicked). This behavior is seen after the user has installed the recent Microsoft Security Updates.
When attempting to launch TWS, clients will see no visual response and there will be no process running in the Task Manager. Java 8 is significant because of the use of symlinks to specify the location(s) of the java executable; e.g. 'C:\ProgramData\Oracle\Java\javapath' contains a shortcut to the java executables, which themselves are located in a 'C:\Program Files (x86)\Java\jre1.8.0_XX'.


How will we fix this?
We are currently investigating the best method to fix the problem.  Please find the most ideal workaround for restoring functionality to the TWS desktop icon below.

***Interactive Brokers does not recommend that any client uninstall his/her Microsoft Security Updates. ***

The Security Updates are in place for a reason and distributed by Microsoft to resolve issues that have been found relative to the operating system and it's components.


Workaround for launching TWS

There is a simple way to regain usage of the TWS 4.0 icons by following the steps below.

1.) Determine your Java version

     Open a Windows Command Prompt (Dos window)

     Type "java -version" then press Enter; do not include the quotes

 In this example, I am running java version "1.7.0_71". My update number is '71'.

2. )Highlight path for your Java installation below, then right-click and select 'Copy' so that it is placed into the 'clipboard'. Do not include any extra spaces after 'C:\Jts'. If the result in Step #1 includes 64-bit, you will copy the first command below, otherwise you will copy the second.

          "C:\Program Files\Java\jre1.8.0_XX\bin\javaw.exe" -cp jts.jar;total.2012.jar -Dsun.java2d.noddraw=true -Dswing.boldMetal=false -Dsun.locale.formatasdefault=true -Xmx768M -XX:MaxPermSize=192M jclient/LoginFrame C:\Jts


          "C:\Program Files (x86)\Java\jre1.8.0_XX\bin\javaw.exe" -cp jts.jar;total.2012.jar -Dsun.java2d.noddraw=true -Dswing.boldMetal=false -Dsun.locale.formatasdefault=true -Xmx768M -XX:MaxPermSize=192M jclient/LoginFrame C:\Jts


3.) Right-click the TWS icon and select 'Properties'


Note that the Target command-field is highlighted by default

4.) You will now replace the command by right-clicking the highlighted target field and selecting 'Paste'. Where 'XX' is replaced by your update number, as shown in Step 1.


5.) Click Apply, then click OK

At this point you may be presented with a User Access Control (UAC) message.

Select 'Continue'. You should now be able to use your TWS icon.


Java 8 Installation on Windows


This article describes how to install the Java environment necessary to run the standalone version of IB's Trader Workstation on Windows. Please note that users of the browser based version of IB's Trader Workstation require no additional steps to operate the application.


In the latest release of the Java 8 runtime environment (JRE) for Windows, changes have been made to manner in which Java interacts with the operating system. If you encounter one of the following error messages after upgrading to Java 8, please follow the instructions below.


To address the errors messages above, please perform the following steps:

  1. Go to the Windows Control Panel and uninstall ALL versions of Java
  2. Restart your computer to ensure any remaining files are removed following the uninstall process
  3. After restarting, inspect C:\Windows\System32 and C:\Windows\SysWOW64 (if you are using a 64 bit computer), and ensure there are no copies of java, javaw, or javaws.  If you find any copies of these files in those directories, delete them.
  4. Reinstall the correct version of the Java 8 runtime environment for your version of Windows (64 or 32 bit) from the Oracle download page.
  5. Delete the Trader Workstation 4.0 shortcut from the desktop, and unpin any copies from the taskbar.
  6. Reinstall the standalone Trader Workstation from the IB download page.

This will create a new, functional Trader Workstation 4.0 icon on the desktop.  Please also see KB2129 and KB2115 for instructions on installing Java and TWS, respectively.

Java 8 Installation on Mac OS X Yosemite and later


This article describes how to install the Java environment necessary to run the standalone version of IB's Trader Workstation X on Mac OS X 10.10 Yosemite. Please note that users of the browser based version of IB's Trader Workstation require no additional steps to operate the application.

In order to use the standalone Trader Workstation X application on an Apple Macintosh computer, a valid Java development kit (JDK) installation must be present on the system.  If, after upgrading to the latest version of OS X, your operating system no longer recognizes the previously installed JDK, please follow the steps below:

  1. Go to the Oracle JDK download page
  2. Agree to the license agreement
  3. Download the latest JDK for Mac (listed in the table as Mac OS X x64)

Once the installation is complete, Trader Workstation X should launch without issue.


How to configure Java Virtual Machine memory Parameters in TWS


General notes on the Java virtual machine and memory parameters

Trader Workstation is a Java-based application. Programs which are compiled using Java execute within a Java virtual machine (JVM) process which manages the interactions between the program, and the operating system and hardware. The Java virtual machine dynamically manages the memory usage for the program running in it. There are many technical aspects to how the memory is managed, but there are two primary spaces or blocks of memory which are of concern for running the TWS: the heap space, and the permanent generation (permgen) space.

The heap is the area in memory where all class instances and arrays are allocated. The heap is created when the JVM is started, and space is periodically reclaimed by the garbage collector (GC), the Java Virtual Machine's automatic storage management system. There is also non-heap space, known as the permanent generation space, utilized by the Java Virtual Machine to hold code which typically has a longer life in memory, or a specific usage. If either of these spaces are not sized correctly, errors can occur when the process runs out of memory in these spaces. If this occurs, the program will appear to be frozen or may crash completely, and the log files in the program directory for TWS (in C:\Jts, by default on Windows OS) will likely include one of the following errors:

  • java.lang.OutOfMemoryError: Java heap space
  • java.lang.OutOfMemoryError: PermGen space

When launching a Java program, it is possible to pass certain parameters to the Java virtual machine to adjust how much memory the process will use to run the program. The Xmx flag controls the maximum amount of memory to be used for the heap space, and the XX:MaxPermSize flag controls the maximum amount of memory to be used for the permanent generation space.

As we have released newer versions of TWS which contain more features, the memory required for the Java virtual machine to effectively run TWS has increased.

  • For users running TWS with a 32 bit version of Java, the MINIMUM memory for the heap size is 256 MB, and for the permanent generation space is 128 MB.
  • For users running TWS with a 64 bit version of Java, the MINIMUM memory for the heap size is 384 MB, and for the permanent generation space is 192 MB.

The above are the bare minimums necessary to run the program for most customers. Usage of many of the features in TWS will require higher memory allotments.

Some users may have old shortcuts or use custom scripts to launch TWS. It is crucial that these are updated accordingly to use at least the minimum memory parameters mentioned above. Some users who have extensive portfolios or execute large amount of orders may need to adjust the parameters to improve performance. The heap size can be increased if there is an OutOfMemoryError pertaining to the heap space.  Note, in our experience the memory should typically not need to be increased above 1024M in the heap and 256M in the permgen.

If at any time following adjusting the memory parameters, you receive an error that the system could not create the Java Virtual Machine, this indicates the memory increase was too aggressive, and you need to scale back the parameters.

**Please note the following:  Starting with Java 8, the XX:MaxPermSize parameter has been deprecated. When running TWS with Java 8, the XX:MaxPermSize parameter will be ignored at runtime if present; this parameter could be simply omitted from the start-up script.

Browser-based TWS (Java WebStart version)
IB uses a script on our website to dynamically serve a JNLP file with different memory parameters based on the URL request from the browser. When launching TWS from our website, you can add the Xmx and Xmps parameters to the URL to configure the heap size and and permanent generation space size, respectively for the Java virtual machine process which will run TWS. For example:

will result in a JNLP file with the max heap size set to 768 mb and the max permanent generation space size set to 128MB.

If you encountered a resource allocation message when launching a previously saved copy of the JNLP file, and were directed to this webpage, please download a new version of the JNLP file from here.  The file you are using is likely out-of-date, and does not contain the correct resource allocation parameters for your operating system.

Standalone TWS on Windows
To adjust the memory parameters used when launching TWS from the desktop or start menu shortcut:

  •   Right-click the shortcut and select Properties
  •   On the shortcut dialog window, find the Xmx and XX:MaxPermSize flags in the target field
  •   Adjust the values following the flags to the desired size

Standalone TWS on Mac
To adjust the memory parameters used when launching TWS using the icon:

  •     Hold Control and click (or right-click if you have a two-button mouse) on the application icon
  •     Choose "Show package contents" from the menu
  •     Open Contents > MacOS
  •     Open the JavaAppLauncher shell script file
  •     Find the Xmx and XX:MaxPermSize flags, and adjust the values following the flags to the desired size

Standalone TWS on UNIX (or Mac) via terminal command
When executing the command to start TWS from the terminal, adjust the values following the Xmx and XX:MaxPermSize flags to the desired size. For example, if you would normally launch using:

java -cp jts.jar:total.2013.jar -Xmx512M -XX:MaxPermSize=128M jclient.LoginFrame

but need to increase due to errors or freezing due to running out of memory, you can instead run:

java -cp jts.jar:total.2013.jar -Xmx768M -XX:MaxPermSize=256M jclient.LoginFrame

Questions et Réponses au sujet de la vulnérabilité du protocole SSL "Heartbleed Bug"


Une faille concernant l’implémentation open source des protocoles SSL et TLS permet à une tierce personne de lire des mots de passe et des clés de cryptage dans la mémoire du serveur.


Il s’agit d’un protocole qui contient les instructions de cryptage et décryptage de données transmises à travers des réseaux informatiques.


Nous ne nous attendons à aucune conséquence.
Le nombre très restreint de serveurs qui utilisait la version d’OpenSSL affectée a été mis à jour sitôt la faille identifiée et le patch disponible.


Le Système d’Accès Sécurisé constitue une couche de sécurité complémentaire à votre nom d’utilisateur et mot de passe. Ces derniers ne sont pas la seule défense contre un accès non autorisé.

L’utilisation d’un Système d’Accès Sécurisé garantit que vous seul pourrez accéder à votre compte.


Grâce aux mesures de sécurité additionnelles prises par IB, votre mot de passe n’est pas affecté par cette faille de sécurité.

Le changement fréquent de votre mot de passe est une pratique de sécurité conseillée, mais il n’est pas impératif de le faire maintenant.

FAQ об уязвимости SSL (т.н. баг "Heartbleed")


Уязвимость открытой реализации SSL протокола и TLS протокола позволяет посторонним лицам взламывать пароли и ключи шифрования в памяти сервера.


Это протокол, который служит для того, чтобы давать команду компьютеру для выполнения шифрования/дешифрования данных, которыми обмениваются в сети.


Никакого воздействия не ожидается.

Несколько IB серверов, которые использовали уязвимую версию OpenSSL были обновлены с внесением требуемых исправлений, как только уязвимость была выявлена и был выпущен патч.


Система безопасного входа гарантирует более высокий уровень защиты, чем при входе исключительно с логином и паролем. Логин и пароль не являются крайними мерами защиты против несанкционированного доступа к вашей учетной записи.

Используя систему безопасного входа, вы можете быть уверены, что никто кроме вас не имеет доступа к вашему счету.


Благодаря дополнительным мерам защиты, предпринятым IB, ваш пароль не подвержен опасности.

Хотя периодическая смена пароля является полезной профилактической мерой безопасности, вам совсем не обязательно менять его именно сейчас в связи с новостями о "Heartbleed".

Syndicate content