QuickBooks Return Codes

General

When using the AutoPal QuickBooks error, if the actions that you are trying to perform are causing QuickBooks some kind of error, these errors are returned to AutoPal and can be viewed inside the QWC Logs tab of the QuickBooks Live tool.

QWC Logs

There error codes are not easy to understand, so this article will give an explanation of what each error code means and what should be done about it.

Error Codes

Error: 1

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

  • Solution: Make sure the data you are trying to pull from QuickBooks (e.g. loan, customer) actually exists in QuickBooks.

Error: 500

One or more objects cannot be found. The query request has not been fully completed. This generally means that AutoPal sent a request to QuickBooks which refers to an object that doesn’t exist.

  • Solution: Make sure the customer, loan, etc. that you are trying to create an invoice for actually exists. You may have to re-sync a loan in order for this to work.

Error: 501

An object referenced in a QuickBooks request is not in the QuickBooks specification. Only certain objects can be requested from QuickBooks through the web connector. This may happen because you are using an older version of QuickBooks. This is an unlikely error because AutoPal has programmed is application to pull only core things from QuickBooks, so all the objects AutoPal requests should be found.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 510

An object requested from QuickBooks cannot be returned. This typically happens because the object isn’t a part of the QuickBooks specification. This error is unlikely.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 530

A field name AutoPal used in the XML request is not supported by QuickBooks.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 531

A value sent to QuickBooks in an AutoPal XML request is not supported by QuickBooks.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 550

Cannot save notes. When data is saved by QuickBooks, corresponding notes are saved. If you encounter this error, the main data sent to QuickBooks was saved, but the notes record was not saved.

  • Solution: Ignore this code. If the problem persists, restart QuickBooks. In extreme cases, reinstall QuickBooks.

Error: 560

Deprecated field used. This means that one or more of the XML fields in the AutoPal request to QuickBooks is currently supported, but may not always be.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 570

Cannot link to transaction. This error occurs if you are trying to reference a transaction, loan, customer, etc. in QuickBooks that has been closed.

  • Solution: Make sure the transaction, customer, loan, etc. that AutoPal is trying to access is not closed in QuickBooks.

Error: 600

No cleared state to return. This error is returned if QuickBooks could not determine a reason for the error.

  • Solution: Restart QuickBooks. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 1000

Internal error. There was an internal QuickBooks error when processing the request.

  • Solution: Try sending the request again. If the problem persists, restart QuickBooks, or in extreme cases reinstall QuickBooks.

Error: 1010

System not available. This means that QuickBooks is not available through the Web Connector.

  • Solution: Make sure that QuickBooks is running. If it is running, make sure the Web Connector can reach it. If not, reinstall the Web Connector. Otherwise, restart QuickBooks. Make sure you open your company file. In extreme cases, reinstall QuickBooks.

Error: 1030

Unsupported message. The request made to QuickBooks is not supported by the current implementation of the QuickBooks API.

  • Solution: This is a very unlikely problem because of the way AutoPal has created its Web Connector application. It’s possible you may need to reinstall QuickBooks.

Error: 1060

Invalid request ID. The ID for the request is invalid. This is most frequently caused by and ID that’s too long.

  • Solution: Shorten the loan ID or customer name that the request is being sent for. Unfortunately, the length restriction is set by QuickBooks and there is nothing else AutoPal can do about it.

Error: 3000

Invalid object ID. The ID for the object you are trying to update in QuickBooks is incorrect. Most often happens when your company file is not open in QuickBooks, a loan is not correctly synced with QuickBooks, or your are using the wrong accounts-receivable account.

  • Solution: Make sure your company file is open in QuickBooks. Make sure the loan from which data is being sent is synced with QuickBooks. If you are sending information that is modifying a payment, QuickBooks will always look at the accounts-receivable account that you used last, so you will have to use the Auto Notes Receivable account inside QuickBooks in order to get QuickBooks to look at payments in that account.

Error: 3010

Invalid Boolean. This will only occur if the request sent from AutoPal contains incorrectly formatted true or false values.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3020

Invalid date. This will only occur if the request sent from AutoPal contains incorrectly formatted date values.

  • Solution: Make sure the loan for which you are sending/requesting data doesn’t have any incorrectly formatted dates. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 3030

Invalid date range. The “from” date in a requested date range is greater than the “to” date.

  • Solution: This is a very unlikely issue. If there are any date ranges associated with the loans that are having issues, make sure the “from” date is previous to the “to” date.

Error: 3031

Invalid string range. A non-date range has a “from” value that is greater than the “to” value.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3035

Invalid time interval. The QuickBooks request contained an incorrectly formatted time interval.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3040

Invalid amount. The QuickBooks request contained an invalid amount.

  • Solution: This is an unlikely error since QuickBooks and AutoPal validate that when a number is required, only a number can be entered. If you see this error, check the loan you are trying to send/request data for and make sure there are no values that should be a number that are actually letters or other characters.

Error: 3045

Invalid price. There was an error in the Price value inside a QuickBooks request that was sent from AutoPal.

  • Solution: AutoPal does not include a price in any of it’s requests, so you should not see this error. If you encounter this error, email AutoPal Support (support@autopalsoftware.com).

Error: 3050

Invalid percentage. There was an incorrectly formatted percentage sent from AutoPal to QuickBooks.

  • Solution: Ensure that the loan for which you are sending/requesting data does not have any strange values where a percentage is required. If you can’t find the problem, email AutoPal Support (support@autopalsoftware.com).

Error: 3060

Invalid quantity. There was an error in a quantity that was sent from AutoPal to QuickBooks.

  • Solution: Make sure none of the fields that should contain a number in the loan for which you are trying to send/request data contain letters or other special characters.

Error: 3065

Invalid GUID. The Global Unique Identifier was invalid.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3070

String too long. A string value submitted in a request from AutoPal to QuickBooks is longer than the maximum number of characters QuickBooks allows for that value. This most often happens with customer names or loan IDs.

  • Solution: Truncate the loan ID, customer name, or other loan or customer value that is too long.

Error: 3080

Invalid string. A string value received by QuickBooks through an AutoPal request was not actually a string or contained invalid characters.

  • Solution: Check the data values for the loan for which you are sending/receiving QuickBooks data to make sure there are no saved values that contain special characters or any values that look wrong.

Error: 3085

Invalid number. There was an incorrectly formatted number sent from AutoPal to QuickBooks.

  • Solution: Ensure that the loan for which you are sending/requesting data does not have any strange values where a number is required, including letters or special characters. If you can’t find the problem, email AutoPal Support (support@autopalsoftware.com).

Error: 3090

Invalid object name. An object that was part of the QuickBooks request had an invalid name.

  • Solution: Check to see if your account number or customer name contains special characters. Make sure that neither name is too long.

Error: 3100

Name is not unique. Some of the data sent as part of a QuickBooks request is already in use inside of QuickBooks. This usually happens if a customer account is no longer linked to its account in QuickBooks.

Solution: Check to see if the account you are looking at in AutoPal already exists in QuickBooks. Make a small change to the account name in QuickBooks. Sync the account with QuickBooks. Merge the old account with the new account in QuickBooks.

Error: 3101

Resulting amount too large. You have sent an amount with your QuickBooks request that is larger than the maximum allowable amount in QuickBooks.

  • Solution: Check the account for which you are getting the error to make sure none of the amounts are exceptionally large. If you can’t find the problem, or the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 3110

Invalid enum value. There is an invalid enumerated value in the QuickBooks request.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3120

Object not found. Invalid object ID. The ID for the object you are trying to update in QuickBooks is incorrect. Most often happens when your company file is not open in QuickBooks, a loan is not correctly synced with QuickBooks, or your are using the wrong accounts-receivable account. This can also happen if you are sending a payment that uses a payment method that has not been created in QuickBooks. This might also happen if there is no vendor in QuickBooks that matches what AutoPal is sending over.

  • Solution: Make sure your company file is open in QuickBooks. Make sure the loan from which data is being sent is synced with QuickBooks. If you are sending information that is modifying a payment, QuickBooks will always look at the accounts-receivable account that you used last, so you will have to use the Auto Notes Receivable account inside QuickBooks in order to get QuickBooks to look at payments in that account. If this doesn’t work, check that the payment methods for the payments being sent by the request have been created in QuickBooks. Check to make sure all of your source companies have been sent to QuickBooks.

Error: 3121

OwnerID not found. The data type for one of the objects sent in a QuickBooks request is not recognized.

  • Solution: Make sure QuickBooks is open. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 3130

Parent reference not found. An object in the QuickBooks request refers to a parent element that doesn’t exist.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3140

Reference not found. The QuickBooks request contains a reference to a field or object in QuickBooks that doesn’t exist.

  • Solution: Make sure all the payment methods exist in QuickBooks for payments you are trying to send to QuickBooks. Make sure the source company for the loans for which you are getting this error have been sent to QuickBooks. You can check this in your company QuickBooks tools. Make sure the correct receivable account is open. QuickBooks will use the last receivable account that was used when attempting to apply payments.

Error: 3150

Missing required element. An element required by QuickBooks to complete a requested action (e.g. apply a payment) was not included in the request.

  • Solution: Make sure the payments, loans, or customers you are sending to QuickBooks aren’t missing any essential information. If you are unable to find the problem, email AutoPal Support (support@autopalsoftware.com).

Error: 3151

Invalid element for request. The QuickBooks request contains a field or object that can’t be used in that type of request.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3153

Element conflict in request. 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.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3160

Object cannot be deleted. The request is attempting to delete an object that is required.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3161

Cannot delete before closing date An attempt was made to delete a fieldValue with a date that is on or before the closing date of the company.

  • Solution: If you are sure you really want to do this, please ask a user with Admin privileges for QuickBooks to remove the password for editing transactions on or before to closing date (this setting is in the Accounting Company Preferences), then try again.

Error: 3162

Not allowed in multi-user mode. The request send to QuickBooks is trying to perform an action that is not allowed in multi-user mode.

  • Solution: You may need to switch to single-user mode. If you are hosting QuickBooks on a server, this is not advisable.

Error: 3170

Object cannot be modified There was an error when modifying an element. You can get this error message as the result of a lot of different actions. You’ll really have to read the error description to figure out exactly what’s going wrong.

Also see the notes for error 3180, which shares the same error messages

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3171

Cannot modify before closing date. An attempt was made to modify an element with a date that is on or before the closing date of the company.

  • Solution: 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.

Error: 3172

Cannot modify prior to last condense. An attempt was made to modify an element with a date that is on or before the last inventory condensed date.

  • Solution: AutoPal doesn’t make requests that involve the inventory functionality in QuickBooks, so it’s unlikely that you will get this error. Email AutoPal Support (support@autopalsoftware.com).

Error: 3173

Related object deleted or modified. An object related to a transaction that’s being sent from AutoPal has been manually deleted in QuickBooks.

  • Solution: You may have to recreate, for example, the invoice you are trying to apply a payment to. You can also resend all the transaction history for the loan in question and then remove any duplicate invoices.

Error: 3175

Object is in use. There was an error adding, modifying or deleting an object because it is already in use.

See the notes for error 3180, which shares the same error messages

  • Solution: You may need to resend the QuickBooks requests from AutoPal. If the problem persists, close QuickBooks and reopen it.

Error: 3176

Related object is in use. An object related to a transaction that AutoPal is sending to QuickBooks is already in use. This usually stops the transaction from posting.

See the notes for error 3180, which shares the same error messages

  • Solution: Close and reopen your QuickBooks company file. If the problem persists, email AutoPal support (support@autopalsoftware.com).

Error: 3177

Duplicate AppliedToTxn IDs. A transaction ID is being sent twice by the same request or already exists in QuickBooks.

  • Solution: Resend the AutoPal request for the transaction that is giving the error. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 3180

Object cannot be added. There was an error when saving a object in QuickBooks. This error occurs most often when using QuickBooks Enterprise Edition. This error is caused when QuickBooks locks elements or accounts because it thinks they are in use by another user.

  • Solution: Resend the request that is causing the error. In extreme cases, close and reopen QuickBooks.

Error: 3185

Object cannot be voided. Cannot void an object in QuickBooks.

  • Solution: This is an unlikely error because AutoPal doesn’t send requests to void transactions. Resend the account information that’s giving the error. Close and reopen QuickBooks and try again. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 3190

Cannot clear required element. An element cannot be cleared because it’s required.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 3200

Outdated edit sequence. The edit sequence sent in the QuickBooks request is no longer the one QuickBooks sees as the most current.

  • Solution: Send the data from AutoPal to QuickBooks again. If that doesn’t work, close and reopen QuickBooks and then send the data again. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 3205

Invalid address. An address sent in a QuickBooks request takes up more than the allowed 5 address lines in QuickBooks.

  • Solution: Make sure the street address portion of any address being sent to QuickBooks (usually sent as part of source company data) is not exceptionally long.

Error: 3210

Other validation error. This usually happens when an invalid value is sent to QuickBooks. This can also happen if you try to apply a payment to an invoice, and the invoice has an open balance of less than the payment applied amount.

  • Solution: Make sure that the accounts containing the data that are giving you the error don’t contain any special characters or letters in fields that should only contain numbers. Check the invoices for these loans in QuickBooks to make sure you aren’t sending a payment amount that is larger than the available invoices. This usually won’t be a problem because AutoPal applies payments to interest and fees invoices and also to loan notes.

Error: 3220

Not authorized operation. You are trying to access a feature through the web connector that has been turned off in QuickBooks.

  • Solution: The specific error message will likely give more detail. Make sure you have payment application, invoice creation, etc. turned on inside your QuickBooks.

Error: 3230

Status rollback. The request has been rolled-back.

  • Solution: Requested changes are no longer affecting QuickBooks. Send the requests from AutoPal again.

Error: 3231

Status unprocessed. The request has not been processed.

  • Solution: Send the data from AutoPal to QuickBooks again.

Error: 3240

Time creation mismatch. Object specified in the request cannot be found.

  • Solution: Send the data that is giving you the error from AutoPal again. It may be that you are trying to apply a payment to an invoice that doesn’t exist or something similar. You may have to resend more data from the problem loans. In extreme cases, change the account name in QuickBooks and then un-sync and re-sync it in AutoPal.

Error: 3250

Feature not enabled. Your request refers to a feature that either is not active in QuickBooks or doesn’t exist in the version of QuickBooks you are using.

  • Solution: Make sure all of your QuickBooks features are turned on.

Error: 3260

Insufficient permissions. Insufficient permission level to perform this action. This means QuickBooks is denying the updates you AutoPal is trying to do because it doesn’t have permission.

Error: 3261

Application has no sensitive data permission. AutoPal has no permission to access sensitive data.

 

Error: 3262

Requires payroll subscription. In order to complete this request, the company data file has to be subscribed to the Intuit Payroll Service.

  • Solution: You should not get this error because the AutoPal integration doesn’t access any payroll functions in QuickBooks. If you do see this error, email AutoPal Support (support@autopalsoftware.com).

Error: 3263

Not authorized for write access. This request cannot be completed because AutoPal has been given read-only access.

  • Solution: Inside of QuickBooks, grant outside applications write access. You may need to reinstall the web connector and make sure you choose the correct access options.

Error: 3270

Missing posting account. This can occur when you’re trying to do something unsupported with the SDK. For instance, if you try to add a Sales Order to QuickBooks Pro, you’ll get back this error message, as you can only create Sales Orders in QuickBooks Premier and Enterprise Solutions editions. In QuickBooks Pro, you may be able to work with existing sales orders but you can’t create new ones.

  • Solution: This is an unlikely error since AutoPal accesses functionality that should be supported by most versions of QuickBooks. If you get this error, you may need to upgrade your QuickBooks to a newer version. If you are unsure, email AutoPal Support (support@autopalsoftware.com).

Error: 3280

Item type mismatch. An object sent to QuickBooks cannot be used in this line item because its data type is incorrect.

  • Solution: This is an unlikely error. If this error appears, email AutoPal Support (support@autopalsoftware.com).

Error: 3290

Item line out of order. The line items in the request are in a different order than the line items in the transaction.

  • Solution: This is an unlikely error. If you encounter it, email AutoPal Support (support@autopalsoftware.com).

Error: 3300

Cannot open requested window. Could not open the requested form or window in QuickBooks.

  • Solution: Make sure your QuickBooks company file is open and running.

Error: 3301

Not allowed in unattended mode; cannot perform this request unless an interactive QuickBooks user is logged in.

  • Solution: Make sure your QuickBooks company file is open an running.

Error: 3310

Unknown employee time status Failed to save the Time Tracking transaction. The employee provided in the TimeTrackingAdd request has the checkbox “Use time data to create paychecks” set to the Unknown state. Have AutoPal 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.

  • Solution: This is an unlikely error because the AutoPal QuickBooks integration does not support employee time tracking. If you encounter this error, email AutoPal support (support@autopalsoftware.com).

Error: 3320

Could not create report The required report could not be generated.

  • Solution: This is an unlikely error because AutoPal’s integration with QuickBooks does not request the generation of any reports. If you encounter this error, email AutoPal Support (support@autopalsoftware.com).

Error: 3330

Invalid GUID for request. A field in the request has a value that cannot be used for that field.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 3340

Not allowed in data event callback This request cannot be processed from within a data event callback procedure.

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 3350

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

  • Solution: This is an unlikely error. You may have too many custom payment methods defined in AutoPal. Email AutoPal Support (support@autopalsoftware.com).

Error: 3351

Invalid type for custom field. The value or values provided in a custom QuickBooks field are of a type that is not allowed.

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 3352

Not allowed to reuse custom field. An attempt is made to use a QuickBooks custom field more than once.

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 3360

Callback app cannot be verified. The callback application cannot be found using the ID provided. This usually means QuickBooks is unable to communicate with AutoPal.

Error: 9001

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

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 9002

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

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 9003

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

  • Solution: Restart QuickBooks. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 9004

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

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 9005

An error recovery record could not be saved An attempt was made to save an error recovery record for a message set. The save operation failed and the record wasn’t saved.

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 9100

Macro name not unique The macro name “fieldValue” is already in use; it may only be defined once.

  • Solution: AutoPal doesn’t access QuickBooks macros, so this is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 9101

Macro name too long The macro name “fieldValue” is too long.

  • Solution: This is not a likely error. Check QuickBooks macros to make sure none of the names are too long. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 9102

Macro name invalid The macro name contains invalid characters.

  • Solution: This is not a likely error. Make sure your QuickBooks macro names don’t contain special characters. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 9103

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

  • Solution: This is not a likely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040300

Attempted to retrieve a value before it has been set.

  • Solution: Send the request again. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040301

Internal error interpreting the response.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040302

The given enum value is invalid. The request contained an invalid enumerated number.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040303

The given numeric value is out of range. A number in the request is outside the range allowed by QuickBooks.

  • Solution: Make sure all the numbers for the account that’s giving the error look correct. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040304

The given string is longer than the maximum length allowed. (Note that for many strings, the maximum length is different for desktop versions of QuickBooks than for QuickBooks Online Edition.)

  • Solution: Check your source companies, customers, and loan IDs to make sure they aren’t too long.

Error: 0x80040305

The given value has an invalid format.

  • Solution: Make sure that the values being sent from the loan that’s giving you errors don’t contain any special characters or values that don’t look right.

Error: 0x80040306

Attempted to retrieve a value that has been set to empty. This usually occurs when a value was manually deleted in QuickBooks and AutoPal is trying to pull it.

  • Solution: Re-sync the loan that is giving errors with QuickBooks.

Error: 0x80040307

This message will indicate why the verification of the request set failed.

  • Solutions: Try to assess from the additional data why the error was received. If you are unable to do so, email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040308

Could not communicate with the QuickBooks SDK.

Error: 0x80040309

The QuickBooks SDK is a pre-release version.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004030A

The given version of qbXML is not supported.

  • Solution: An update of the AutoPal integration is required. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004030B

This feature is not supported in the specified version of qbXML.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004030C

This message set must be used with the QBSessionManager, not QBOESessionManager. -or- This message set must be used with the QBOESessionManager, not QBSessionManager.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004030D

HTTP-specific error text.

  • Solution: See if you can find the error using this list of HTTP status codes. If you are unable to find the error, email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004030E

Specific error-recovery messages will be sent with this HRESULT.

  • Solution: See if you can find the error using the additional information provided. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004030F

This function is supported by a newer version of Request Processor.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040310

Error recovery is enabled. Process or clear the saved Response status before issuing another request.

  • Solution: Send the AutoPal data again. If the problem persists, restart QuickBooks and then resend the AutoPal data.

Error: 0x80040311

The ConnectionTicket must be filled in.

  • Solution: This is an unlikely error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040312

The Country value is invalid.

  • Solution: Check the customer country to make sure it’s valid. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040414

A dialog box is being displayed in the QuickBooks user interface. AutoPal cannot access QuickBooks until you dismiss the dialog box.

  • Solution: Open QuickBooks and close any dialog boxes or pop-up windows displayed in QuickBooks. QuickBooks itself should remain open.

Error: 0x80040416

Your QuickBooks company file is not open.

  • Solution: Either open the appropriate company file in QuickBooks, or configure QuickBooks to accept automatic logins from the Web Connector.

Error: 0x80040420

The QuickBooks user has denied access.

  • Solution: Make sure the appropriate company file is open in QuickBooks. Configure QuickBooks to accept automatic logins from the Web Connector. Check user security settings in QuickBooks to make sure you have access.

Error: 0x8004041A

AutoPal does not have permission to access your QuickBooks company data file. You can grant access permission through the Integrated Application preferences.

  • Solution: Configure QuickBooks to accept automatic logins from the Web Connector.

Error: 0x80040400

QuickBooks found an error when parsing the XML text stream it received from AutoPal.

  • Solution: This error means that some of the data in your company account is corrupted. Look at the account(s) you are trying to send data from to see if there are any anomalies in the data.

Error: 0x80040401

Could not access QuickBooks.

  • Solution: Make sure your company QuickBooks file is open.Configure QuickBooks to accept automatic logins from the Web Connector. If no other solution works, QuickBooks may have an error in the install and you may need to reinstall it.

Error: 0x80040402

Unexpected error.

  • Solution: Check the qbsdklog.txt file for possible, additional information about the error.

Error: 0x80040403

Could not open the specified QuickBooks company data file.

  • Solution: Make sure that the correct company file is open in your QuickBooks. Check that the QuickBooks version matches the version of the company data file.

Error: 0x80040404

The version of QuickBooks currently running does not support qbXML.

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

Error: 0x80040405

qbXML components have not been installed.

  • Solution: It is possible that the QuickBooks installation was incomplete. Reinstall QuickBooks.

Error: 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.

  • Solution: Your QuickBooks installation may be incomplete. Reinstall QuickBooks.

Error: 0x80040407

The installation of QuickBooks appears to be incomplete. Please reinstall QuickBooks.

  • Solution: Your QuickBooks installation may be incomplete. Reinstall QuickBooks.

Error: 0x80040408

Could not start QuickBooks.

  • Solution: Make sure the correct company file is running in your QuickBooks. Your QuickBooks installation may be incomplete. Reinstall QuickBooks.

Error: 0x80040409

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

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

Error: 0x8004040A

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

  • Solution: The AutoPal connection with QuickBooks can only use a single company file. You must only open one company file at a time on a single machine.

Error: 0x8004040B

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

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

Error: 0x8004040C

BeginSession method has not been called or it did not succeed.

  • Solution: Make sure the correct company file is open in your QuickBooks. You may need to restart QuickBooks.

Error: 0x8004040D

The ticket parameter is invalid.

Solution: This is not a common error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004040E

There is not enough memory to complete the request.

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

Error: 0x8004040F

The OpenConnection method has not been called.

  • Solution: Resend the data from AutoPal to QuickBooks. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040410

The QuickBooks company data file is currently open in a mode other than the one specified by AutoPal.

Error: 0x80040411

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

  • Solution: Restart QuickBooks. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040412

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

  • Solution: This is not a common error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040413

QuickBooks does not support the rollbackOnError value of the onError attribute.

 

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040415

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

  • Solution: This is not a common error. Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040417

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

  • Solution: Make sure QuickBooks is open and the appropriate company file is also open.

Error: 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.

  • Solution: Make sure that you have given permission inside of QuickBooks so that AutoPal can access your QuickBooks data.

Error: 0x80040419

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

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004041B

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

  • Solution: Send the data from AutoPal again. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004041C

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

  • Solution: Send the information from AutoPal to QuickBooks again. Restart QuickBooks. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004041D

AutoPal 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.

  • Solution: Check your Integrated Application Preferences inside QuickBooks to make sure AutoPal is allowed to log in automatically.

Error: 0x8004041E

AutoPal’s certificate is expired.

  • Solution: If you want to allow AutoPal to log into QuickBooks automatically, log into QuickBooks and try again. Then click Allow Always when you are notified that the certificate has expired.

Error: 0x8004041F

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

  • Solution: Upgrade to a more advanced version of QuickBooks.

Error: 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.

  • Solution: Contact AutoPal Support (support@autopalsoftware.com).

Error: 0x80040422

AutoPal requires Single User file access mode and there is already another application sharing data with this QuickBooks company data file.

  • Solution: Make sure no other user or software application is accessing your QuickBooks data.

Error: 0x80040423

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

  • Solution: Contact AutoPal Support (support@autopalsoftware.com).

Error: 0x80040424

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

  • Solution:  Resend the information from AutoPal to QuickBooks. Restart QuickBooks.

Error: 0x80040425

Invalid parameter.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040426

Scripts are not allowed to call QBXMLRP.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040427

Unregistered QuickBooks.

  • Solution: Make sure you have a version of QuickBooks (2003 or newer) that supports the web connector. Make sure your QuickBooks software is registered.

Error: 0x80040428

The current request processor does not support the request.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x80040429

The current message set is not supported.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004042A

Remote access is not allowed.

  • Solution: Make sure remote access is allowed in your QuickBooks preferences. If the problem persists, email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004042B

Unsupported interface.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Error: 0x8004042C

Certificate has been revoked.

  • Solution: Email AutoPal Support (support@autopalsoftware.com).

Leave A Comment?