How to overcome the error message "Another user is running Tax Optimizer"?

• If you use Windows
• If you use Mac OS

If you use Windows

f. Once you have cleared your Java cache, log back into the Client Portal and try launching Tax Optimizer again. You should now be able to open the application. If you are still not able to launch the Tax Optimizer and you receive the same error as before (Another user is running Tax Optimizer), please perform the additional steps below:

g. Press the key combination Win(Windows Key) + E  and navigate to the directory: C:\Users\<your windows user>\ibto

 

h. Select all files in the ibto folder, right-click on the selection and choose Send to > Compressed (zipped) folder. The zipped file will be created in the same ibto directory

If you use Mac OS

e. Once you have cleared your Java cache, log back into the Client Portal and try launching Tax Optimizer again. You should now be able to open the application. If you are still not able to launch the Tax Optimizer and you receive the same error as before (Another user is running Tax Optimizer), please perform the additional steps below:

h. Compose a New Ticket in the Message Center, informing us of this issue. Please attach the Zip file you created at the previous step (g.) to your ticket

References:

• Tax Optimizer Users' Guide

1. Activate the IBKR Mobile Authentication (IB Key) as 2-Factor security device

In order to be independent of wireless/phone carrier-related issues and have a steady delivery of all IBKR messages we recommend to activate the IBKR Mobile Authentication (IB Key) on your smartphone.

The smartphone authentication with IB Key provided by our IBKR Mobile app serves as a 2-Factor security device, thereby eliminating the need to receive authentication codes via SMS when logging in to your IBKR account. 

Our IBKR Mobile app is currently supported on smartphones running either Android or iOS operating system. The installation, activation, and operating instructions can be found here:

Android: KB2277
iOS: KB2278

2. Restart your phone:

Power your device down completely and turn it back on. Usually this should be sufficient for text messages to start coming through. 

Please note that in some cases, such as roaming outside of your carrier's coverage (when abroad) you might not receive all messages.

3. Use Voice callback

If you do not receive your login authentication code after restarting your phone, you may select 'Voice' instead. You will then receive your login authentication code via an automated callback. Further instructions on how to use Voice callback can be found in IBKB 3396.

4. Check whether your phone carrier is blocking the SMS from IBKR

Some phone carriers automatically block IBKR text messages, as they are wrongly recognized as spam or undesirable content. According to your region, those are the services you can contact to check if a SMS filter is in place for your phone number:

In the US:

• All carriers: Federal Trade Commission Registry
• T-Mobile: Message Blocking settings are available on T-Mobile web site or directly on the T-Mobile app

In India:

• All carriers: Telecom Regulatory Authority of India

In China:

• Call your phone carrier directly to check whether they are blocking IBKR messages

References:

• How to login using SMS authentication
• Overview of Secure Login System
• Information and procedures related to Security Devices
• IBKR Mobile Authentication

Specs:

1: Standard Communication: TCP Port 80 | SSL Communication: TCP Port 443.

2: This IB Server host does not support ping request.

Important Note: If you are accessing Client Portal from a corporate network where the Internet access is provided through a load balancing equipment, you may receive error messages about expired/invalid session and/or missing web content upon or after the login phase. The load balancer cycles your outbound connections over two or more network interfaces to equalize the network workload. Because of this mechanism, your HTTP requests reach our systems from different IP addresses, invalidating your Client Portal session. In this scenario, as a solution, please ask your network administrator or IT group to configure your machine/device for bypassing the load balancer. This will allow your session to remain valid and alive.
 

3: Gateway dedicated to clients with accounts assigned to the Hong Kong server, but are physically connecting from Mainland China.

Background: 

 

TWS users may receive the following error message upon configuring TWS to use the eSignal data feed:

 

Issue A - You are not using the 32 bit version of TWS and/or eSignal:

Issue B - There is an incompatibility with the file C:\Jts\dbcapi.dll:

Instructions to resolve issue A

Installing 32-bit TWS

Please open the page http://www.ibkr.com in your browser and perform the steps below:

1) Click on the LOG IN button at the top right corner of the page.

2) Under the section TRADER WORKSTATION, click on TWS Latest.

4) Click on the item Windows 32-bit.

5) Make sure that the description under the DOWNLOAD button has changed to "Windows: 32 bit". Click now on DOWNLOAD.

6) Launch the downloaded file. The Trader Workstation installation will start. At this point you may see the warning message "Trader Workstation latest is already installed...". Ignore this warning and click on the button Next > to continue the installation.

7) Your "Trader Workstation" Desktop icon will be automatically updated. You can now launch the 32-bit Trader Workstation by a double click on that icon.

Instructions to resolve issue B

Replacing dbcapi.dll for compatibility between 32-bit TWS and 32-bit eSignal 12

To correct an incompatibility with the dbcapi.dll file, we will replace that file with another version of it taken from the eSignal installation folder. Please follow the steps below to perform the substitution:  

1) Navigate to C:\Jts and rename the file dbcapi.dll to dbcapi_old.dll

2) Navigate to the directory where 32-bit eSignal 12 is installed (most commonly C:\Program Files (x86)\Common Files\Interactive Data\DM)

3) Copy dbcapi_vc8.dll from that directory into the C:\Jts directory.

4) Move to the C:\Jts directory

5) Right click on the dbcapi_vc8.dll file (now in the C:\Jts directory) and select rename. Type dbcapi.dll as the new filename.

6) TWS is now ready to accept the eSignal data feed.