Troubleshooting - QuickBooks Begin Session Failed. 653 - There was an error while communicating with the Ids Server. The Response Stream was null or empty. - QuickBooks Online API Status

Problem Description:

I am using QODBC Online. I have authorized QODBC Online at QuickBooks Online.

When we try to connect, the following error appears:

*********************************************************************************************************************
IsAService: False
Begin Session Failed. S0000 00000 [QODBC] QuickBooks Begin Session Failed. 653 - There was an error while communicating with the Ids Server. - - The Response Stream was null or empty.

or

*********************************************************************************************************************
S0000 10054 [QODBC ONLINE] QuickBooks message: 653 - There was an error while communicating with the Ids Server. - - The Response Stream was null or empty.
[10054] [QODBC ONLINE] QuickBooks message: 653 - There was an error while communicating with
the Ids Server. - - The Response Stream was null or empty.

Is there currently an outage or any issues with QODBC Online and QuickBooks Online?

Solution: 

QODBC Online connects to your QuickBooks Online company through Intuit's QuickBooks Online REST API (web services). Unlike QuickBooks Desktop, where QODBC communicates with a locally installed QuickBooks application, QODBC Online depends on communication between your computer, the Internet, QODBC Online, and Intuit's QuickBooks Online API services.

If the QuickBooks Online API is timing out or have Outage, QODBC Online may not receive a response from QuickBooks Online within the expected time, resulting in a connection timeout, an empty response, a request timeout, or similar communication error.

This can be caused by temporary delays in QuickBooks Online's web services or by issues with your Internet connection. If you encounter this error, please wait a few moments and try connecting to QuickBooks Online again.

If the issue persists, we recommend checking the QuickBooks Online API service status to determine whether there is a known service interruption or performance issue.

Possible Causes

A delayed or timed-out request can occur for several reasons, including:

• Temporary performance issues with the QuickBooks Online API.
• High load or temporary service degradation on Intuit's servers.
• A temporary interruption or instability in your Internet connection.
• Network latency between your computer and the Intuit API servers.
• Firewall, proxy, VPN, or other network-security software interfering with HTTPS communication.
• Temporary congestion or packet loss on the Internet connection.
• A large or complex QuickBooks Online request taking longer than expected to process.
• Temporary authentication or API service issues.
• Scheduled maintenance or an incident affecting QuickBooks Online or Intuit's developer services.

Because QODBC Online relies on external web services, the availability and response time of those services can affect QODBC Online operations.

What to Do When a Timeout Occurs

1. Wait and retry the operation

If the error occurs only occasionally, wait a few minutes and retry the operation.

A temporary API delay may clear automatically, and the same request may complete successfully when retried.

If the query or operation succeeds after retrying, this generally indicates that the original problem was temporary rather than a persistent QODBC configuration issue.

2. Check your Internet connection

Verify that your Internet connection is stable.

If possible:

• Open QuickBooks Online in a web browser.
• Browse to other websites to confirm general Internet connectivity.
• If you are using a VPN, temporarily test without the VPN.
• Check whether other computers on the same network are experiencing similar connectivity problems.
• If you are using a corporate proxy or firewall, verify that HTTPS connections to Intuit services are not being blocked or interrupted.

A working web browser does not completely rule out network-related problems, but it can help identify a general connectivity issue.

3. Check QuickBooks Online service status

Before troubleshooting QODBC further, check whether Intuit is reporting an outage or degraded performance.

The official QuickBooks Status page provides the current status of QuickBooks Online services and regional services:

You can check the current QuickBooks Online API service status using the link(s) below.

QuickBooks Online Services Status

Intuit also provides a separate Developer Platform Status page that specifically reports the status of developer services and the QuickBooks Online API:

The Developer Platform Status page includes a specific QuickBooks Online API component, which is particularly relevant when QODBC Online reports API-related connection or timeout errors.

QuickBooks Online API Status

IntuitDev: Status Twitter Handle

StatusGator - Intuit QuickBooks Online API Status

Check for an active API incident

If the status page reports Degraded Performance, Partial Outage, or Major Outage, the problem may be on the Intuit service side.

In such cases, repeatedly restarting QODBC or reinstalling the driver is generally not necessary. Wait until the service issue is resolved and then retry the operation.

Intuit's status system also provides information about current and historical API incidents and scheduled maintenance.

QuickBooks Online API Status

QuickBooks Online Application Status

If the Problem Continues

If the timeout occurs repeatedly and the Intuit status pages show that all relevant services are operational, perform the following checks:

1. Retry the same operation after a few minutes.
2. Determine whether the problem occurs with all queries or only a specific query/table.
3. Test a simple query to determine whether basic API communication is working.
4. Check whether QuickBooks Online can be accessed normally through a web browser.
5. Test the connection from a different Internet connection, if available.
6. Temporarily test without a VPN or restrictive proxy.
7. Check firewall and network-security software for blocked or interrupted HTTPS connections.
8. Record the exact error message and error code reported by QODBC Online.
9. Note the date and time when the timeout occurred.
10. Check the Intuit status pages for incidents occurring at the same time.

When Contacting QODBC Support

If the issue continues after confirming that the QuickBooks Online API is operational, provide the following information when contacting QODBC Support:

• Exact QODBC error message and error code.
• QODBC Online version/build number.
• Date and time of the failure.
• Whether the problem occurs consistently or intermittently.
• The SQL query or operation that produced the error.
• Whether other queries execute successfully.
• Whether QuickBooks Online is accessible through a web browser.
• Whether retrying the operation resolves the problem.
• Whether the problem occurs from another computer or Internet connection.
• Any relevant information shown on the Intuit service-status pages.

This information can help determine whether the problem is related to the QODBC configuration, the local network, or a temporary issue with the QuickBooks Online API.

Tags: QuickBooks Online, QBO, Internet, QODBC Online, Online API, 653, QuickBooks Online API Status