TWS error 10197: competing market-data session

Quick answer

Error 10197 can mean that two sessions are trying to use the same live feed. This can affect a paper account that shares data with a live user. Check which user is signed in to each app before buying or changing a feed.

Educational software guidance. Trading involves risk. Read the financial and information disclaimers.

Step by step

1 List the live and paper sessions now open across TWS, Gateway, mobile, and Client Portal.
The DATA indicator at the top of the paper TWS window shows which market-data session this login is using.
2 Check which live username shares data with the paper account.
3 Close the conflicting use during a planned test, without losing oversight of live orders.
4 Reconnect the intended paper session and request the same product.
The TWS Connections window lists each market-data farm and its status, with a Reconnect All Farms button.
5 If concurrent use is needed, ask IBKR about the correct username and subscription arrangement.

A practical example

A live session and a paper session may both try to use shared live data. The paper quote then stops even though the subscription is still paid. Check which user is active in each app. Close the conflicting use only when it is safe to do so, then test one quote. Buying the same feed again is not the first step when the problem began as soon as another login opened.

Illustrative scenario, not a record of a trade placed during this review.

Screen reference

TWS paper watchlist with instrument rows and quote columns — Use the same instrument row when comparing data. Captured outside the tested execution workflow; this image does not establish real-time entitlement. Captured in TWS paper mode on 3 October 2026. Open the image for full size.

How to confirm the result The intended session should receive data without the competing-session message.

Mistake to avoid

Buying another exchange feed will not necessarily resolve a conflict between sessions using the same data access.

Common questions

Does live usage have priority?

IBKR’s message guidance describes live preference in the needed live-versus-paper conflict.

Is changing a client ID enough?

A client ID is a local API identifier, not a separate broker username.

TWS error 200: contract not found or ambiguous TWS error 201: read the order rejection reason TWS error 202: why was the order cancelled? Why TWS disconnects when you log in to TradingView

Financial and information disclaimers

Financial disclaimer

These guides explain software. They are for education, not financial, investment, tax, or legal advice. No example is a suggestion to buy or sell a product or use a trading strategy. Trading can lose money, including all funds you put at risk. With margin, futures, short sales, or some options, losses can exceed your starting funds. Automation can fail, send duplicate orders, or act late. Stops do not guarantee a fill or a price. Review your orders and positions, and seek advice from a qualified professional for your own needs. Paper trades, examples, and past results do not predict live results or promise a profit.

Information disclaimer

This is general help based on the sources and check date shown on the page. Screens, settings, fees, data access, and product support can change or differ by app version, account, country, and broker. The content may contain errors or become out of date; accuracy, completeness, and continuous service are not guaranteed. Check current broker and app instructions before acting. Screenshots show where controls are; they do not prove that an order test passed. This guide does not replace broker terms or risk notices. References to IBKR and TradingView identify their products and do not imply their endorsement of this guide.