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

Background: 

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 s3.amazonaws.com 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)

Background: 

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: http://www.interactivebrokers.com/cgi-bin/conn_test.pl 

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.

 

When and how should I increase the memory allocation for TWS?

Overview: 
Java Virtual Machine memory allocation

The Trader Workstation is a Java-based application. As any other Java applications, it executes within a Java virtual machine (JVM) which manages the interactions between the program and the underlying Operating System (OS).

The memory (RAM) which is allocated by the operating system to the JVM constitutes the heap space. That is the area where all the class instances and arrays needed by the application are allocated. The heap space is created when the JVM is started and it is dynamically freed-up by the Garbage Collector (GC), the Java memory manager. When the need arises, the Garbage Collector is invoked to free up the heap space by unloading Java classes and other code structures no longer used by the application.

If the heap space is undersized, the Garbage Collector may not be able reclaim memory at the needed pace or may have to be called too often, draining the processor (CPU) resources. When this happens, the application may slow down, be unresponsive or even crash completely.

To ensure a smooth TWS run, it is therefore sometimes necessary to change the memory allocation, according to the layout complexity and the needs of the application itself.

Background: 
In which case I should change the TWS memory allocation?
If your TWS layout contains a considerable number of elements (Analytical/Trading Tools, Chart windows, News panels, Watchlists, Layout tabs...) and your platform is slow or poorly responsive, you may want to increase the memory allocation in order to achieve better performances. If your TWS freezes or crashes, we also recommend increasing the heap space as the first corrective action to attempt. 
 
How much memory should I allocate to TWS?
In general we recommend to start with a conservative memory allocation and test the TWS performances with that set up. If the performances improvement is less noticeable then expected or not yet satisfactory, you can switch gradually to higher values until you find the best fit for your platform.
Please consider the following:
  • The memory you allocate to the TWS has to be available on your system. For details, please see Note 1. Allocation values above 2048 are not supported by 32-bit OS. For details, please see Note 2. 
Considering the above, we suggest to initially reserve 1.5 GB of system RAM the TWS, as explained in the guide below.
This amount of free memory is usually available on any modern computer and should be a good fit for most of the cases. Should you still notice slowness, freezing or crashes during the TWS execution, you can raise the value to 1792.
In any case, we do not recommend to set the value above 2048 since this will produce an unnecessary overhead and may thus even decrease the overall performances of the application.

 

 
How can I change the memory allocation for the TWS?

Please follow one of the links below for the instructions, according to the Operating System and TWS release you are using

 
     Any Operating System
 
     B.1 Your Operating System is Windows      
     B.2 Your Operating System is Mac OS

 

 

 

A. TWS version 972 and higher

The steps below are valid for all Operating Systems
1) In the TWS, click on the top menu File (or Edit if you are using Classic TWS) and select Global Configuration...

2) On the left side menu of the Global Configuration panel, click on General

3) In the panel on the right side, in the Memory Allocation field, replace the existing value with 1536

4) Click on Apply and then on OK

5) Shut down the TWS

6) Launch the TWS with a double click on the Desktop shortcut Trader Workstation (Should you receive an error message, please see Note 3.
 

Back to top 

 

 

B. TWS versions previous to 972

B.1 Your Operating System is Windows

1) Close TWS in case it is running

2) On your keyboard, press WIN+R (the WIN key is the key with the windows flag located on the left side of tour keyboard,  between the keys CTRL and ALT) 
3) Type C:\Jts\tws.vmoptions and Click OK
4) Should the system ask you which program to use to open the file, select Notepad and click OK
5) Cut the line -Xmx768m and paste it below the line ### Keep on update
6) Change then the value of the parameter Xmx from 768 to 1536
7) Save the changes by clicking on the top menu File --> Save
8) Close the file clicking on the X icon on the right side of the toolbar
9) Launch the TWS with a double click on the Desktop shortcut Trader Workstation (Should you receive an error message, please see Note 3.
 
 

Back to top 

 

 

B.2 Your Operating System is Mac OS
 
1) Close the TWS if it is running
 
2) Use the Spotlight search (the magnifier glass on the top right of your Desktop) to find the file tws.vmoptions
Normally the file is located within the Jts folder (a subfolder of your home folder)

3) On the Spotlight results panel, click on tws.vmoptions to open it. Should the system ask you how to open this file, click Choose Application... select  a text editor (TextEdit, Smultron, TextWrangler...) of your choice and click Open
 
 
4) Locate the line -Xmx768m. Cut it and paste it below the line ### Keep on update
 
6) Modify the value 768 in to 1536
 
7) Save and close the file

8) Launch the TWS with a double click on the Desktop shortcut Trader Workstation (Should you receive an error message, please see Note 3.
 

 Back to top 

 

 

Notes

 

1. Available system RAM
In order to check the amount of available system RAM on your computer, you can:
 - on Windows: use the key combination CTRL+SHIFT+ESC to start the Task Manager, click on the tab Performance and look for the "Available" Physical Memory. This will tell you the amount of unoccupied RAM in MB (1024 MB = 1GB)
 
 
- on Mac OS: Open Finder, go to Application --> Utilities and open Terminal. In the terminal type the command:
sudo purge
and press Enter. The system may ask you to enter your Mac user password. Enter the password. Once the command has completed, type the following command:
top -l 1| grep PhysMem
The "unused" value will tell you the amount of unoccupied RAM in MB (1024M = 1GB)

 

 

 2. Limitations of 32-bit Operating Systems
Please notice that 32-bit Operating Systems can normally only address a maximum of 2 GB of RAM per process (see table below for details). Because of this OS architecture limitation, if you have a 32-bit OS, the maximum memory allocation for the TWS must not exceed 2048 Mb.

 

3. Error: "Could not create the Java Virtual Machine"
This error may be displayed upon TWS startup if you set the memory allocation to a value higher than the available RAM of your system or if you set it higher than 2048 on a 32-bit Opertaing System. To overcome the error, you would need to decrease the memory allocation to a lower value using this procedure
 

Back to top 

 

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

QUEL EST LE PROBLEME? QU’EST-CE QU’«HEARTBLEED»?

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.

QU’EST-CE QU’SSL?

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

IB EST-IL AFFECTE PAR «HEARTBLEED»?

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 SYSTEME D’ACCES SECURISE CONSTITUE-T-IL UNE SECURITE SUPPLEMENTAIRE DANS CE GENRE DE CAS?

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.

DEVRAIS-JE CHANGER MON MOT DE PASSE?

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")

В ЧЕМ СУТЬ ПРОБЛЕМЫ? ЧТО ТАКОЕ "HEARTBLEED"?

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

ЧТО ЗНАЧИТ SSL?

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

МОЖЕТ ЛИ IB БЫТЬ ПОДВЕРГНУТА "HEARTBLEED"?

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

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

ЗАЩИЩАЕТ ЛИ УСТРОЙСТВО БЕЗОПАСНОСТИ В ПОХОЖИХ СИТУАЦИЯХ?

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

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

ДОЛЖЕН ЛИ Я СМЕНИТЬ ПАРОЛЬ?

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

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

Vulnerabilidad en SSL ("Heartbleed Bug") - Preguntas Frecuentes

CUÁL ES EL PROBLEMA? QUÉ ES «HEARTBLEED»?

Una vulnerabilidad en la implementación del código abierto de los protocolos SSL y TLS permite a una persona no autorizada leer las contraseñas y llaves de encripción en la memoria del servidor.

QUÉ ES SSL?

Es un protocolo que sirve para instruir máquinas en cómo encriptar y decriptar intercambios da datos entre redes.

HA AFECTADO  «HEARTBLEED» a IB?

No se espera ningún impacto.

Los pocos servidores de IB que usaban la versión afectada de OpenSSL han sido actualizados y corregidos tan pronto como la vulnerabilidad fue detectada y el parche distribuido.

PROTEGE MEJOR EL SLS EN ESTA SITUACIÓN O SIMILARES?

El sistema de ingreso seguro (SLS) añade una protección extra al acceso con sus credenciales (usuario y contraseña). El usuario y la contraseña no son la única línea de defensa contra accesos no autorizados.

Usando su SLS al acceder le asegura que es usted la única persona que puede acceder a la cuenta.

DEBO CAMBIAR MI CONTRASEÑA?

Al haber tomado IB todas las medidas de seguridad, no es necesario, su contraseña no ha sido afectada por esta vulnerabilidad.

Aunque cambiar la contraseña regularmente es una buena medida de seguridad, no tiene que hacerlo ahora a causa de lo informado sobre «Heartbleed».

SSL の脆弱性 ("Heartbleed Bug") に関するFAQ

どういった問題ですか? «HEARTBLEED»とは何ですか?

オープンソースのSSL/TLSプロトコルの実装において指摘された脆弱性は、サーバーのメモリ上にあるパスワードや暗号化キーを読み取られてしまう可能性があるという極めて重大なものです。

SSLとは何ですか?
 

SSLとは、パソコンに対して、ネットワーク上で通信されるデータの暗号化、復号化を指示するプロトコルです。

IBで«HEARTBLEED»の影響はありますか?

現時点では確認されておりません。

脆弱性が確認されたOpenSSLのバージョンを使ってるIBサーバーはごく僅かで、弊社では脆弱性が指摘され、パッチがリリースされてからすぐに対応策を講じています。

セキュアログインシステム(SLS)を使用することで、こういった場合でもセキュリティ強化になりますか?

主なログイン時の主な認証(ユーザー名、パスワードの入力)に加え、セキュアログイン・システム(SLS)をご利用いただくことで更に高いセキュリティを確保することができます。

また、セキュアログイン・ディバイス(SLS)をご利用いただくことで、他の人が口座へアクセスできないよう対処することができます。

パスワード変更をした方が良いですか?

弊社にて講じた追加のセキュリティ対策により、パスワードはこの脆弱性の影響は受けておりません。

パスワードを定期的に更新することは、セキュリティ上良いことですが、«Heartbleed»対策としてすぐにパスワードを変更する必要はございません。

SSL Schwachstelle ("Heartbleed Bug") Fragen und Antworten

WAS IST DAS PROBLEM? WAS IST "HEARTBLEED"?

Die aufgezeigte Schwachstelle der Open Source Version der SSL und der TLS Protokolle erlaubt einer unautorisierten Person das Lesen von Passwörter und Kodierungsschlüssel im Speicher des Servers.

WAS IST SSL?

Dies ist ein in der Netzwerkommunikation angewendetes Protokoll, welches dem Rechner die Instruktionen gibt wie Daten Ver- und Entschlüsselt werden.

IST IB VON "HEARTBLEED" BETROFFEN?

Es werden keine Auswirkungen erwartet.

Die wenigen IB Servers, welche die betroffene Version von OpenSSL hatten, wurden sofort mit einem Sicherheitsupdate geschützt als die Schwachstelle identifiziert wurde.

IST ES SICHERER SLS IN DIESER SITUATION ZU BENUTZEN?

Das Sicherheits Login System fügt Ihren Zugangsdaten eine zusätzliche Sicherheitsebene hinzu. Der Benutzername und das Passwort sind so nicht mehr die einzige Gefahrenabwehr gegen einen unauthorisierten Zugang.

Das benutzen des Sicherheitsgeräts für die Einwahl zu Ihrem Konto garantiert, dass Sie die einzige Person sind welche Zugang zu Ihrem Konto hat.

SOLL ICH MEIN PASSWORT ÄNDERN?

Durch die zusätzlichen Sicherheitsvorkehrungen welche Interactive Brokers getroffen hat ist Ihr Password von dieser aufgezeigten Schwachstelle nicht betroffen.

Das regelmässige Ändern Ihres Passwortes ist grundsätzlich eine gute Sicherheitsmassnahme, Sie müssen diese aber aufgrund der gegenwärtigen Ereinisse nicht unbedingt anwenden. 

SSL 漏洞 ("Heartbleed 漏洞") 常見問題解答

這是一個什麼問題? “HEARTBLEED”是指什麼?

HEARTBLEED漏洞是指開源應用項目SSL(保安接層加密技術)和TLS(安全傳輸協議)協議的安全漏洞,它能讓攻擊者從服務器內存中讀取密碼和密鑰。

什麼是SSL?

SSL(保安接層加密技術)是一種安全協議,用於指令機器對網絡通信中的數據進行加密和解密。

盈透是否受到“HEARTBLEED”漏洞的影響?

盈透未受該漏洞的影響。在發現漏洞並有補丁發布之時,我們已經更新並修復了少數幾個使用受影響的OpenSSL的盈透服務器。

出現這種問題及相似問題時,SLS是否可以更好的保護賬戶?

安全登錄系統(SLS)為您在通過主要的登錄憑證(用戶名和密碼)訪問賬戶之外增添了另一層保護。用戶名和密碼並不是阻止未經授權而訪問賬戶的唯一防線。使用SLS設備可確保只有您才能訪問您的賬戶。

我是否需要更改密碼?

盈透採取了其他安全措施,因此您的密碼不會受到此漏洞的影響。
定期更換密碼是防止賬戶被他人攻擊的好方法,但是您不必在看到有關Heartbleed的報導時專門去更改密碼。
 

SSL 漏洞 ("Heartbleed 漏洞") 常见问题解答

这是一个什么问题? “HEARTBLEED”是指什么?

HEARTBLEED漏洞是指开源应用项目SSL(保安接层加密技术)和TLS(安全传输协议)协议的安全漏洞,它能让攻击者从服务器内存中读取密码和密钥。

什么是SSL?

SSL(保安接层加密技术)是一种安全协议,用于指令机器对网络通信中的数据进行加密和解密。

盈透是否受到“HEARTBLEED”漏洞的影响?

盈透未受该漏洞的影响。
在发现漏洞并有补丁发布之时,我们已经更新并修复了少数几个使用受影响的OpenSSL的盈透服务器。

出现这种问题及相似问题时,SLS是否可以更好的保护账户?

安全登录系统(SLS)为您在通过主要的登录凭证(用户名和密码)访问账户之外增添了另一层保护。
用户名和密码并不是阻止未经授权而访问账户的唯一防线。
使用SLS设备可确保只有您才能访问您的账户。

我是否需要更改密码?

盈透采取了其他安全措施,因此您的密码不会受到此漏洞的影响。
定期更换密码是防止账户被他人攻击的好方法,但是您不必在看到有关Heartbleed的报道时专门去更改密码。
 

Syndicate content