All problems
TMKR-4004
Error
Vendor or customer
Maximum concurrent sessions reached
The license already has as many active sessions as it allows, so a new one was refused.Session & heartbeat•Also known as: MAX_SESSIONS_EXCEEDED, max-sessions-exceeded, concurrent_session_limit
Symptoms
API response error_code: MAX_SESSIONS_EXCEEDED (HTTP 409), context shows active_sessions and max_sessions.
Causes
The product is running on more charts/terminals than the license permits.
A previous session did not end cleanly and still counts as active.
How to fix it
If you're the customer (running the product)
1
Close extra sessionsRemove the product from other charts or terminals using this license, then try again. A stale session frees up automatically after its timeout.
2
Upgrade if you need moreIf you legitimately need more simultaneous sessions, upgrade the license to a higher session limit.
If you're the vendor (publisher)
1
Close test sessionsDuring testing, end old test sessions (or wait for the timeout) before starting new ones, or raise the session limit on the test license.