Knowledgebase
[QODBC-Desktop] What's the meaning of numeric error code from QuickBooks
Posted by Juliet (QODBC Support) on 31 March 2010 08:12 AM

Error Code Information for QODBC

 

QuickBooks Enterprise User Expired Message? Click Here

 

Note: Each qbXML response message called by QODBC can include three status attributes: statusCode, statusSeverity, and statusMessage.

 

 

statusSeverity

General Description

     statusSeverity - General meaning of codes in this range

Detail Description

     0-499 INFO - QuickBooks processed the request and has returned data in the remainder of the message.

     500-999 WARNING - QuickBooks processed the request and has returned data in the remainder of the message, but the results might not be consistent with what you expected.

     1000-1999 ERROR - A general error has occurred, and no data is returned.

     2000-2999 ERROR - This request is not supported for QuickBooks, and no data is returned.

     3000-3099 ERROR - A format error has occurred, and no data is returned.

     3100-9099 ERROR - Some other error has occurred, and no data is returned.

     9100-9199 ERROR - A macro-related error has occurred, and no data is returned.

 

statusCode and statusMessage

General Description

     All statusCode Values - Code Meaning Explanation

     statusMessage:

Detail Description

     0 - The QuickBooks server processed the request successfully.

     Message:Status OK

     1 - No match.

     Message: The filters used in the query request did not return any matching objects from QuickBooks.

     500 - One or more objects cannot be found. The query request has not been fully completed.

     Message: There was a required element ("fieldValue") that could not be found in QuickBooks.

     501 - Object not in this qbXML specification

     Message: Unable to represent objectName "fieldValue" in this version of the qbXML spec.

     510 - Object cannot be returned

     Message: Unable to return object.

     530 - Unsupported field

   Message: The field "fieldName" is not supported by this implementation.

     531 - Unsupported enum value

     Message: The enum value "fieldValue" in the field "fieldName" is not supported by this implementation.

     550 - Cannot save notes

     Message: The objectName object was saved successfully, but its corresponding Notes record could not be saved.

     560 - Deprecated field used

     Message: This field will not always be supported.

     570 - Cannot link to transaction

     Message: Unable to link to transaction "fieldValue" because it has already been closed.

     600 - No cleared state to return (For error recovery; no message is returned.)

     1000 - Internal error

     Message: There has been an internal error when processing the request.

     1010 - System not available

    Message: System not available

     1030 - Unsupported message

     Message: This request is not supported by this implementation.

     1060 - Invalid request ID

     Message: The request ID "fieldValue" is invalid, possibly too long, max 50 chars.

     3000 - Invalid object ID

     Message: The given object ID "fieldValue" in the field "fieldName" is invalid.

     3010 - Invalid Boolean

     Message: There was an error when converting the boolean value "fieldValue" in the field "fieldName"

     3020 - Invalid date

     Message: There was an error when converting the date value "fieldValue" in the field "fieldName"

     3030 - Invalid date range

   Message: Invalid date range: From date is greater than To date.

     3031 - Invalid string range

     Message: The "From" or "To" values in the provided fieldName are invalid.

     3035 - Invalid time interval

     Message: There was an error when converting the time interval "fieldValue" in the field "fieldName"

     3040 - Invalid amount

     Message: There was an error when converting the amount "fieldValue" in the field "fieldName"

     3045 - Invalid price

     Message: There was an error when converting the price "fieldValue" in the field "fieldName"

     3050 - Invalid percentage

     Message: There was an error when converting the percent "fieldValue" in the field "fieldName"

     3060 - Invalid quantity

     Message: There was an error when converting the quantity "fieldValue" in the field "fieldName"

     3065 - Invalid GUID

     Message: There was an error when converting the GUID value "fieldValue" in the field "fieldName"

     3070 - String too long

     Message: The string "fieldValue" in the field "fieldName" is too long.

     3080 - Invalid string

     Message: The string "fieldValue" is invalid.

     3085 - Invalid number

     Message: There was an error when converting the number "fieldValue" in the field "fieldName"

     3090 - Invalid object name

     Message: There was an error when storing "fieldValue" in the "fieldName" field.

     3100 - Name is not unique

     Message: The name "fieldValue" of the list element is already in use.

     3101 - Resulting amount too large

     Message: Multiplying the rate and the quantity results in an amount that exceeds the maximum allowable amount.

     3110 - Invalid enum value

     Message: The enumerated value "fieldValue" in the field "fieldName" is unknown.

     3120 - Object not found

     Message: Object "fieldValue" specified in the request cannot be found.

     3121 - OwnerID not found

     Message: Data Extension Definitions specified by OwnerID fieldValue not found for this object type.

     3130 - Parent reference not found

     Message: There is an invalid reference to a parent "fieldValue" in the objectName list.

     3140 - Reference not found

     Message: There is an invalid reference to QuickBooks fieldName "fieldValue" in the objectName.

     3150 - Missing required element

     Message: There is a missing element "fieldName."

     3151 - Invalid element for request

     Message: Cannot use the element "fieldName" in this request.

     3152 - Invalid enum value for this request

     Message: The enumerated value "fieldValue" may not be used in the element "fieldName" in this request.

     3153 - Element conflict in request

     Message: This error is returned whenever there is a conflict in the elements in the request. Each element has valid value, but their combination becomes invalid.

     3160 - Object cannot be deleted

     Message: Cannot delete the object specified by the id = "fieldValue."

     3161 - Cannot delete before closing date

     Message: An attempt was made to delete a fieldValue with a date that is on or before the closing date of the company. If you are sure you really want to do this, please ask a user with Admin privileges to remove the password for editing transactions on or before to closing date (this setting is in the Accounting Company Preferences), then try again.

     3162 - Not allowed in multi-user mode

     Message: This operation is not allowed in multi-user mode.

     3170 - Object cannot be modified

     Message: There was an error when modifying a fieldValue.

     3171 - Cannot modify before closing date

     Message: An attempt was made to modify a fieldValue with a date that is on or before the closing date of the company. If you are sure you really want to do this, please ask a user with Admin privileges to remove the password for editing transactions on or before to closing date (this setting is in the Accounting Company Preferences), then try again.

     3172 - Cannot modify prior to last condense

     Message: An attempt was made to modify a fieldValue with a date that is on or before the last inventory condensed date.

     3173 - Related object deleted or modified

     Message: The related fieldName transaction object fieldValue was deleted or modified.

     3175 - Object is in use

     Message: There was an error adding, modifying or deleting fieldValue because it is already in use.

     3176 - Related object is in use

     Message: The related fieldName transaction object fieldValue is already in use." // "specified by the ID" is appended to fieldValue if necessary.

     3177 - Duplicate AppliedToTxn IDs

     Message: The transaction object "fieldValue" may only be provided once in this request.

     3180 - Object cannot be added

     Message: There was an error when saving a fieldValue.

     3185 - Object cannot be voided

     Message: Cannot void the object specified by the id = "fieldValue"

     3190 - Cannot clear required element

     Message: Cannot clear the element in the fieldName field.

     3200 - Outdated edit sequence

     Message: The provided edit sequence "fieldValue" is out-of-date.

     3205 - Invalid address

     Message: There was an error when composing an address in "fieldValue"

     3210 - Other validation error

     Message: The "fieldName" field has an invalid value "fieldValue

     3220 - Not authorized operation

     Message: There is no permission to perform this request, or the feature has been turned off in QuickBooks.

     3230 - Status rollback

     Message: The request has been rolled-back.

     3231 - Status unprocessed

     Message: The request has not been processed.

     3240 - Time creation mismatch

     Message: Object "fieldValue" specified in the request cannot be found.

     3250 - Feature not enabled

     Message: This feature is not enabled or not available in this version of QuickBooks.

     3260 - Insufficient permissions

     Message: Insufficient permission level to perform this action.

     3261 - Application has no sensitive data permission

     Message: The integrated application has no permission to access sensitive data.

     3262 - Requires payroll subscription

     Message: In order to complete this request, the company data file has to be subscribed to the Intuit Payroll Service.

     3263 - Not authorized for write access

     Message: This request cannot be completed because the integrated application had requested read-only access. Have the integrated application request read/write access, and have the QuickBooks administrator grant this access.

     3270 - Missing posting account

     Message: Missing posting account.

     3280 - Item type mismatch

     Message: The item "fieldValue" cannot be used in this line item. It does not have a correct type.

     3290 - Item line out of order

     Message: The line items in the request are in a different order than the line items in the transaction.

     3300 - Cannot open requested window

     Message: Could not open the requested objectName form or window.

     3301 - Not allowed in unattended mode

     Message: Cannot perform this request unless an interactive QuickBooks user is logged in.

     3310 - Unknown employee time status.

     Message: Failed to save the Time Tracking transaction. The employee "fieldValue" provided in the TimeTrackingAdd request has the checkbox "Use time data to create paychecks" set to the Unknown state. Have your application ask the user whether or not to set time tracking for this employee. Then issue an EmployeeMod request to set this option to either True or False. If True, activities will be transferred to paychecks.

     3320 - Could not create report

     Message: The required report could not be generated.

     3330 - Invalid GUID for request

     Message: Cannot use the value "fieldValue" in the "fieldName" field in this request.

     3340 - Not allowed in data event callback

     Message: This request cannot be processed from within a data event callback procedure.

     3350 - Custom field list is full

     Message: Unable to define a new public data extension; the list of public extension definitions is full.

     3351 - Invalid type for custom field

     Message: The value or values provided for AssignToObject or RemoveFromObject may not be used for public data extension requests.

     3352 - Not allowed to reuse custom field

     Message: The data extension named "fieldValue" was previously defined with a different, incompatible AssignToObject. Unable to use the AssignToObject type in this request.

     3360 - Callback app cannot be verified

     Message: The callback application cannot be found from the CLSID or ProgID provided in the subscription request.

     9001 - Invalid checksum (For error recovery; no message is returned.)

     9002 - No stored response found (For error recovery; no message is returned.)

     9003 - Reinitialization problem (For error recovery; no message is returned.)

     9004 - Invalid message ID (For error recovery; no message is returned.)

     9005 - An error recovery record could not be saved

     Message: An attempt was made to save an error recovery record for a message set. The save operation failed and the record wasn't saved.

     9100 - Macro name not unique

     Message: The macro name "fieldValue" is already in use; it may only be defined once.

     9101 - Macro name too long

     Message: The macro name "fieldValue" is too long.

     9102 - Macro name invalid

     Message: The macro name "fieldValue" contains invalid characters.

     9103 - Macro substitution failure

     Message: The request was unable to use a macro value, probably due to an earlier error encountered when defining the macro.

HRESULT Values for QODBC

 

     The COM methods in the qbXML API used by QODBC return HRESULT values that report connection, parsing, or file I/O errors. The QuickBooks qbXML COM interface called by QODBC supports the IErrorInfo interface, so you can use IErrorInfo to get more information about the HRESULT values.

HRESULT Values and Actions

     0x80040400 - QuickBooks found an error when parsing the provided XML text stream.

     Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040401 - Could not access QuickBooks.

     Action: Perhaps the QuickBooks installation is not complete.

     0x80040402 - Unexpected error. Check the qbsdklog.txt file for possible, additional information.

   Action: Check the log specified for details.

     0x80040403 - Could not open the specified QuickBooks company data file.

   Action: Check that the QuickBooks version matches the version of the company data file.

     0x80040404 - The version of QuickBooks currently running does not support qbXML.

     Action: Check that you have QuickBooks Pro 2002 or higher (USA version), or Pro 2003 or higher in other regions. QuickBooks Basic not supported in any version.

     0x80040405 - qbXML components have not been installed.

   Action: Perhaps the QuickBooks installation is not complete.

     0x80040406 - Could not determine the version of the QuickBooks company data file, or the data file has been modified and requires a newer version of QuickBooks.

   Action: Perhaps the QuickBooks installation is not complete.

     0x80040407 - The installation of QuickBooks appears to be incomplete. Please reinstall QuickBooks.

     Action: Perhaps the QuickBooks installation is not complete.

     0x80040408 - Could not start QuickBooks.

   Action: Perhaps the QuickBooks installation is not complete.

     0x80040409 - The current version of QuickBooks cannot work with the specified company data file.

   Action: Check that the QuickBooks version matches the version of the company data file.

     0x8004040A - QuickBooks company data file is already open and it is different from the one requested.

   Action: The QODBC Driver uses the QuickBooks SDK, which is limited to the features of the standard QuickBooks desktop product, which cannot open multiple company files. You must only open one company file at a time on a single machine.

     0x8004040B - Could not get the name of the current QuickBooks company data file.

   Action: Check that the QuickBooks version matches the version of the company data file.

     0x8004040C - BeginSession method has not been called or it did not succeed.

    Action: Contact QODBC support with a description of what was happening when you got this error.

     0x8004040D - The ticket parameter is invalid.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x8004040E - There is not enough memory to complete the request.

   Action: Check that your machine meets the memory requirements of QuickBooks.

     0x8004040F - The OpenConnection method has not been called.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040410 - The QuickBooks company data file is currently open in a mode other than the one specified by your application.

     Action: The QODBC Driver uses the QuickBooks SDK, which is limited to the features of the standard QuickBooks desktop product, which cannot open multiple company files. You must only open one company file at a time on a single machine.

     0x80040411 - Before calling the BeginSession method, you must call the EndSession method to terminate the current session.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040412 - You cannot make multiple successive calls to the OpenConnection method. Call CloseConnection before calling OpenConnection again.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040413 - QuickBooks does not support the rollbackOnError value of the onError attribute.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040414 - A modal dialog box is showing in the QuickBooks user interface. Your application cannot access QuickBooks until the user dismisses the dialog box.

   Action: Check the QuickBooks desktop application for the described condition.

     0x80040415 - A call to the OpenConnection method must include the name of your application.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040416 - If QuickBooks is not running, a call to the BeginSession method must include the name of the QuickBooks company data file.

   Action: Make sure the DSN you are using includes the path to the company file you require, and that you have followed the security setup steps in our users manual.

     0x80040417 - If the QuickBooks company data file is not open, a call to the BeginSession method must include the name of the data file.

   Action: Make sure the DSN you are using includes the path to the company file you require, and that you have followed the security setup steps in our users manual.

     0x80040418 - This application has not accessed this QuickBooks company data file before. Only the QuickBooks administrator can grant an application permission to access a QuickBooks company data file for the first time.

   Action: Make sure that you have followed the security setup steps in our users manual.

     0x80040419 - This application’s certificate is invalid. An application must have a valid certificate to access QuickBooks company data files.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x8004041A - This application does not have permission to access this QuickBooks company data file. The QuickBooks administrator can grant access permission through the Integrated Application preferences.

   Action: Make sure that you have followed the security setup steps in our users manual.

     0x8004041B - Unable to lock the necessary information to allow this application to access this company data file. Try again later.

    Action: A QuickBooks error, contact Intuit if this happens frequently.

     0x8004041C - An internal QuickBooks error occurred while trying to access the QuickBooks company data file.

   Action: A QuickBooks error, contact Intuit if this happens frequently.

     0x8004041D - This application is not allowed to log into this QuickBooks company data file automatically. The QuickBooks administrator can grant permission for automatic login through the Integrated Application preferences.

   Action: Make sure that you have followed the security setup steps in our users manual.

     0x8004041E - This application’s certificate is expired. If you want to allow the application to log into QuickBooks automatically, log into QuickBooks and try again. Then click Allow Always when you are notified that the certificate has expired.

   Action: Make sure that you have followed the security setup steps in our users manual.

     0x8004041F - QuickBooks Basic cannot accept XML requests. Another product in the QuickBooks line, such as QuickBooks Pro or Premier, 2002 or later, is required.

   Action: Check that you have QuickBooks Pro 2002 or higher (USA version), or Pro 2003 or higher in other regions. QuickBooks Basic not supported in any version.

     0x80040420 - The QuickBooks user has denied access.

   Action: Check the security settings for the user in QuickBooks.

     0x80040421 - The returned text is passed via the qbXML COM Request Processor directly from QuickBooks to your application and is not issued by the qbXML COM Request Processor itself. You may find it useful to copy the text verbatim to your message window.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040422 - This application requires Single User file access mode and there is already another application sharing data with this QuickBooks company data file.

   Action: A company file can only be open in one mode at a time. Certain operations require exclusive (single-user) mode, and can only be run when there are no other users of QuickBooks.

     0x80040423 - The version of qbXML that was requested is not supported or is unknown.

     Action: Check that you have QuickBooks Pro 2002 or higher (USA version), or Pro 2003 or higher in other regions. QuickBooks Basic not supported in any version.

     0x80040424 - QuickBooks did not finish its initialization. Please try again later. 0x80040425 Invalid parameter.

   Action:  A QuickBooks warning, contact Intuit if this happens frequently.

     0x80040425 - Invalid parameter.

     Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040426 - Scripts are not allowed to call QBXMLRP.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040427 - Unregistered QuickBooks.

   Action: Check that you have QuickBooks Pro 2002 or higher (USA version), or Pro 2003 or higher in other regions. QuickBooks Basic not supported in any version.

     0x80040428 - The current request processor does not support the request.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x80040429 - The current messageset is not supported.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x8004042A - Remote access is not allowed.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x8004042B - Unsupported interface.

   Action: Contact QODBC support with a description of what was happening when you got this error.

     0x8004042C - Certificate has been revoked.

     Action: Contact QODBC support with a description of what was happening when you got this error.

 

RDS Error and Explanation

RDS Client Error and Explanation

     80040402 - Remote QuickBooks access failed unexpectedly.

     Explanation: Make sure you are using the web or remote version of QODBC, and contact QODBC support with a description of what was happening when you got this error.

     80040407 - Error retrieving the QuickBooks remote server name and port.

    Explanation: Make sure you are using the web or remote version of QODBC, and contact QODBC support with a description of what was happening when you got this error.

     8004040D - Remote QuickBooks access failed because the remote server name and/or port have changed.

    Explanation: Make sure you are using the web or remote version of QODBC, and contact QODBC support with a description of what was happening when you got this error.

     80040414 - A modal dialog box is showing in the QuickBooks Remote Data Sharing Client user interface. The application cannot access QuickBooks until the dialog is dismissed.

    Explanation: A QuickBooks error, contact Intuit if this happens frequently.

     8004041A - Remote QuickBooks access failed because login and/or password do not match those on the server.

    Explanation: Check the security settings in the QODBC setup screen.

RDS Server Error and Explanation

     80040420 - The user has denied remote access to QuickBooks.

    Explanation: Make sure you are using the web or remote version of QODBC, and contact QODBC support with a description of what was happening when you got this error.

     80040421 - Unable to establish a remote connection to QuickBooks.

    Explanation: Make sure you are using the web or remote version of QODBC, and contact QODBC support with a description of what was happening when you got this error.

(202 vote(s))
Helpful
Not helpful

Comments (4)
Ramaraj
18 September 2013 02:07 PM
i got error in qb:
could not start quickbooks
Error code: 2147220472
Rajendra Dewani
21 September 2013 07:46 AM
I would suggest you to keep QuickBooks running, and try again.

I kindly suggest you to try Keeping QuickBooks running, logged in as Admin, single user mode.
Your QuickBooks file should be accessible and should not be in restricted folder.

Are you trying to run QODBC/QuickBooks in auto login? And is your machine having Terminal serviced/remote desktop enabled i.e. multiple user logging in to your machine using Remote desktop connection?"

If your Answer is No, Please make sure you are not running Your Application in evaluated user context , i.e. you should not run it as "Run as administrator" , Please share log files from QODBC Setup Screen -- Messages -- Review QODBC Messages & Review SDK Messages.

If your answer is yes, then I would like to inform you that QuickBooks SDK has a known limitation with this type of Environment setup and many time it cannot start the QuickBooks in background. (If more than one user is logged in to machine and QBW32.exe is running on more than one user account)

Workaround for the above issue.
1) Make sure you un-select the option of "Keep QuickBooks running for quick start-up" under QuickBooks -- Edit Preferences -- General.
Close all other QuickBooks instances of all other users and then try. (Please verify no instances are running of QBW32 under task manager --processes -- view all user processes)
OR
2) Keep QuickBooks running and try connectin1) Make sure you un-select the option of "Keep QuickBooks running for quick start-up" under QuickBooks -- Edit Preferences -- General.
Close all other QuickBooks instances of all other users and then try. (Please verify no instances are running of QBW32 under task manager --processes -- view all user processes)g.
OR
3) For QODBC 13.0.0.291 and upwards, under Advance tab, enable "Force Start QuickBooks", Make sure you un-select the option of "Keep QuickBooks running for quick start-up" under QuickBooks -- Edit Preferences -- General


If you are still facing issue, I kindly request you to create a support ticket and provided below listed files.
1) Screenshot of QODBC Setup Screen -- > About
2) Screenshot of the issue you’re facing.
Log Files from
3) QODBC Setup Screen -- > Messages -- > Review QODBC Messages
4) QODBC Setup Screen -- > Messages -- > Review SDK Messages
craig darley-usmar
18 September 2017 12:57 PM
I’ve hit some basic issues trying to use the QB API from Dell Boomi.
Specifically I’m issuing a bill_query_request and trying to filter for invoices that are unpaid only.

I’m setting a field called “paidstatus” to “false” but I’m just getting this response…..

<?xml version="1.0" encoding="UTF-8" standalone="no"?><BillQueryRs requestID="2" statusCode="3110" statusMessage="The enumerated value’Unpaid’; in the field ‘PaidStatus’ is unknown or invalid for the qbXML version in use." statusSeverity="Error"/>

Do you know anyone who could help me with this?
I’d also like to know if it’s possible to use the SOAP UI testing tool to connect into Quickbooks to speed up my testing.
Jack
18 September 2017 01:53 PM
Hi Craig,

You’re using Sybase SQL Anywhere ODBC and Not QODBC.

Refer:
qodbc.com/links/2604

Please refer below articles for how to use QODBC:
qodbc.com/links/2512

Please note: you need to select “QuickBooks Data” (if the application is 32 bit) or “QuickBooks Data-64bit QRemote” (if the application is 64 bit) when you choose data source instead of select other data source.

If you are still facing the issue, Please raise a support ticket to the QODBC Technical Support department from below mentioned link & provide requested information:
http://support.flexquarters.com/esupport/index.php?/Tickets/Submit

We may need the following information, Please attach below listed files when replying to the ticket.
1) Screenshot of QODBC Setup Screen -- > About
2) Screenshot of the issue you’re facing.
Share Entire Log Files as an attachment in text format from
3) QODBC Setup Screen -- > Messages -- > Review QODBC Messages
4) QODBC Setup Screen -- > Messages -- > Review SDK Messages
Refer: How to take screenshot: www.qodbc.com/links/screenshot.htm
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please complete the captcha below (we use this to prevent automated submissions).