IBKRSafety1100
Connectivity between IBKR and TWS has been lost
Typical symptoms
- Connectivity lost message appears
- Market data or order status updates stop
- The session may reconnect later
Likely causes
- Network interruption
- IBKR system reset window
- Local workstation sleep or unstable connection
Checks
- Record the timestamp and surrounding 1101 or 1102 messages
- Confirm whether data subscriptions were restored
- Avoid assuming orders or account state are current
Resolution path
- Pause automation until connectivity is restored and state is reconciled
- After reconnect, refresh account, positions, open orders, and active subscriptions
Related terms: 1101, 1102, network, reconnect, system reset
IBKRSetup502
Couldn't connect to TWS or IB Gateway
Typical symptoms
- IBKR API reports that it cannot connect
- Client code times out or disconnects during startup
Likely causes
- Wrong host or port
- Trusted IP restrictions block the connection
- The desktop API listener is disabled
Checks
- Check the socket port and paper/live environment
- Review trusted IP settings
- Inspect the TWS or Gateway API log for rejected clients
Resolution path
- Use a local, read-only verification script first
- Keep trusted IPs narrow and explicitly allow the workstation that runs the script
Related terms: could not connect, TWS, Gateway, trusted IP, paper, live
IBKRData162
Historical market data service returned an error
Typical symptoms
- Historical data request fails
- The message mentions pacing, permissions, HMDS, or no data
- Large batches fail intermittently
Likely causes
- Pacing limits
- No data for the requested instrument or duration
- Missing permissions or unsupported bar size
Checks
- Reduce batch size
- Record durationStr, barSizeSetting, whatToShow, RTH flag, and endDateTime
- Retry one contract manually before scaling
Resolution path
- Throttle historical requests and cache successful results
- Make requests explicit and small enough to diagnose
Related terms: HMDS, pacing, historical, barSizeSetting, durationStr, reqHistoricalData
IBKRData10197
No market data during competing live session
Typical symptoms
- Market data works in one session but not another
- The message mentions a competing live session
Likely causes
- Another TWS, Gateway, mobile, or web session is consuming live data
- The paper session is sharing live data permissions with a live login
Checks
- Review every active IBKR login
- Decide which session should own live data
- Test delayed data to separate entitlement from session contention
Resolution path
- Close competing sessions or route data requests through the intended active session
- Design research tools to tolerate delayed or unavailable live data
Related terms: competing live session, market data, paper, live, entitlement
IBKRData200
No security definition has been found for the request
Typical symptoms
- Contract lookup fails
- Historical or market data request returns no contract
- The symbol is ambiguous
Likely causes
- Missing exchange, currency, primary exchange, expiry, strike, or multiplier
- The symbol maps to multiple instruments
- The contract is expired or unavailable
Checks
- Qualify the contract before requesting data
- Add primaryExchange for stocks when needed
- Verify futures/options expiry and multiplier
Resolution path
- Build a fully specified contract and inspect the qualified conId
- Log contract fields with the request so future failures are reproducible
Related terms: contract, conId, qualifyContracts, primaryExchange, ambiguous
IBKRData354
Requested market data is not subscribed
Typical symptoms
- Live market data request is rejected
- Ticker values are delayed, frozen, or missing
- Permissions differ between paper and live sessions
Likely causes
- The account lacks the required market data subscription
- The request uses live data where delayed data is expected
- Paper account entitlement differs from live account entitlement
Checks
- Confirm subscriptions in Account Management
- Test delayed data type where appropriate
- Document whether paper or live data is being requested
Resolution path
- Subscribe to the required data or explicitly request delayed data for educational workflows
- Do not treat missing data as a trading signal
Related terms: market data, subscription, delayed, entitlement, reqMktData
IBKRRuntime1300
TWS socket port was reset
Typical symptoms
- The API reports a socket port reset
- Existing clients disconnect
- New connections require a different port
Likely causes
- The API socket port changed in TWS settings
- TWS restarted with updated configuration
Checks
- Open API settings and read the active socket port
- Compare the script configuration to the desktop setting
Resolution path
- Update the client port and reconnect deliberately
- Store environment-specific ports in configuration instead of hard-coding them across scripts
Related terms: port reset, socket, TWS settings, configuration
Educational boundary
This lookup is for technical troubleshooting and reproducibility. It is not financial, investment, trading, tax, or legal advice. Prefer paper trading and read-only checks while diagnosing live connectivity or data issues.
Interactive Brokers, IBKR, Trader Workstation, and IB Gateway are trademarks or registered trademarks of their respective owners. InQuantWeTrust is independent and is not affiliated with, endorsed by, or sponsored by Interactive Brokers.
