Share via

What is this Bookings app error means

ANAND PRAKASH 0 Reputation points
2026-04-30T19:26:42.4333333+00:00 
UTC Date: 2026-04-30T19:12:33.340Z
Client Id: 5FC6DA6CB599410D82B94C346
Session Id: 452ef75d-ec9a-4b33-8df0-
Client Version: 20260430040
BootResult: fail
Back Filled Errors: Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined
err: Error: 401
esrc: StartupData
et: ServerError
estack: Error: 401
    at Object.I [as createStatusErrorMessage] (https://res.df.onecdn.static.microsoft/owamail/hashed-v1/msalv5/scripts/owa.bookingsindexv2.565c1814.js:1:1836)
    at https://res.df.onecdn.static.microsoft/owamail/hashed-v1/msalv5/scripts/owa.bookingsindexv2.565c1814.js:1:159493
st: 401
reqid: c04d2c48-69db-8049-aeb7-56ec9462eb
cv: OC58suSAurBK8/N+78kr0c.0.1.1

I am accessing Booking from teams, Teams version is 26093.415.4620.1935., Does anybody else have the similar issue

Microsoft Teams | Microsoft Teams for business | Other

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-04-30T19:27:04.5733333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error indicates that the Bookings web app inside Outlook/Teams is failing to start because it receives an HTTP 401 (unauthorized) response while loading its startup data, and then fails when trying to parse the (missing) JSON response.

    Key parts of the log:

    • BootResult: fail and esrc: StartupData – the failure happens while loading initial configuration/startup data for Bookings.
    • err: Error: 401 and st: 401 – the server is returning HTTP 401 Unauthorized.
    • Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input – the client code expects a valid JSON body but gets an empty/invalid response because of the 401, so JSON parsing fails.

    In practice this usually means:

    • The current sign-in/token for Bookings is not valid or not accepted (authorization issue), or
    • There is a transient backend/service problem returning 401 instead of the expected startup payload.

    Because the context only documents a specific, different Outlook/Teams integration issue (the “We can't open the Teams App right now. Please try again later” error) and a generic transient error pattern for Bookings, the only supported guidance is:

    1. Treat this as a transient or sign-in/authorization issue.
    2. Fully close Teams and Outlook, then sign in again and retry Bookings.
    3. If the problem persists, contact the Microsoft 365 admin or Microsoft support and provide:
      • The error details (especially err: Error: 401, esrc: StartupData, reqid, and cv values).

    If other users in the same tenant can open Bookings successfully, this further points to a user-specific auth/tenant condition; if all users are affected, it is more likely a service-side issue that needs to be checked via the Microsoft 365 Service Health dashboard or support.

    References: