Overview
In the QQube Configuration Tool, the synchronization log list may display a red failed entry when QQube can no longer connect to the QuickBooks Enterprise Custom Reporting feature. Select that red status link to open this guide.
Resolve every failed entry
A later synchronization that reports Success does not mean this earlier error corrected itself. The failed entry must still be reviewed and resolved.
The detailed synchronization log for this entry contains a message similar to the following:
Detailed synchronization log message
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 10/15/2027 06:44:57 PM >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SybaseSession_ExecuteNonQueryCommand ExecuteNonQuery Unable to connect to server 'QQube_CustomReportingServer': [Sybase][ODBC Driver][SQL Anywhere] Invalid user ID or password CREATE EXISTING TABLE "41646d696e"."crp_AccountQuery" AT 'QQube_CustomReportingServer. v_lst_account' <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
What the Error Means
QQube uses selected information from the QuickBooks Enterprise Custom Reporting feature to supplement data available through the Intuit Software Development Kit.
This error means QQube can no longer authenticate with the Custom Reporting user configured for the affected QuickBooks company file. The most common causes are a missing Custom Reporting user, a changed password, changed permissions, or a QuickBooks company-file access problem.
Resolution
Complete these checks in order.
1. Confirm the Custom Reporting User Exists
If the required Custom Reporting user is missing, recreate it and assign the required permissions.
Follow Create Connection Users.
2. Correct the Custom Reporting Password
If the password changed, restore the password originally stored in QQube.
If a new password must be used, remove the company file from the QQube Configuration Tool and add the company file again during the same operation. This stores the new Custom Reporting credentials in QQube.
3. Restore the Required Permissions
Review the permissions assigned to the Custom Reporting user and restore the required access.
4. Repair QuickBooks or Company-File Access
If the credentials and permissions are correct, check for a damaged QuickBooks installation, Database Server Manager folder tracking problems, or incorrect permissions on the QuickBooks company file or folder.
Run the QuickBooks utility that repairs company-file and network problems. In a Multi-User implementation, run it on the server.
Review Fix company file and network issues with QuickBooks File Doctor.
Expected Result
QQube connects successfully to the QuickBooks Enterprise Custom Reporting feature, and the synchronization completes without another invalid user ID or password error.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article