Troubleshooting - QODBC Record Set Issue

Problem Description:

I am using below code it is returning records & giving me the correct result. But If I change query from "SELECT Name FROM customer" to "SELECT * FROM customer" it does not returns any records & giving me the incorrect result. I am getting below error:

[QODBC] Internal error
440: Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record.



Public Sub exampleSelect()
Const adOpenStatic = 3
Const adLockOptimistic = 3
Dim oConnection
Dim oRecordset
Dim sMsg
Dim sConnectString
Dim sSQL

sConnectString = "Driver={QODBC Driver for QuickBooks};DFQ=C:\QuickBooks\Maintenance.qbw;OpenMode=F;OLE DB Services=-2;"
sSQL = "SELECT Name FROM customer"
Set oConnection = CreateObject("ADODB.Connection")
Set oRecordset = CreateObject("ADODB.Recordset")

oConnection.Open sConnectString
oRecordset.Open sSQL, oConnection, adOpenStatic, adLockOptimistic
sMsg = "**********************" & Chr(100)
Do While (Not oRecordset.EOF)
sMsg = sMsg & oRecordset.Fields("Name") & Chr(100)
oRecordset.MoveNext
Loop
sMsg = sMsg & "**********************"
MsgBox sMsg

oRecordset.Close
Set oRecordset = Nothing
oConnection.Close
Set oConnection = Nothing
End Sub

Solution:

You need to add below line in your connection string to resolve the issue.

OptimizerAllowDirtyReads=N

For Example:

sConnectString = "Driver={QODBC Driver for QuickBooks};DFQ=C:\QuickBooks\Maintenance.qbw;OpenMode=F;OLE DB Services=-2;OptimizerAllowDirtyReads=N"

After changing this you can get the correct result.

Troubleshooting - How do I know which version of QuickBooks my QODBC license works with?

Problem Description:

How do I know which version of QuickBooks my QODBC license works with?  

Solution:

To find out which version of QuickBooks with your QODBC license works please follow below steps:

1. Click Start > All Programs > QODBC Driver for use with QuickBooks
2. Click QODBC Setup Screen
3. Click the About tab


4. In the middle of the About Tab window, you will see a hyperlink that says “Check website for updates”, just below this, you will see your Serial Number in the format X00X12345678.

The first character in the Serial Number indicates the type of license you have. R indicates, Read Only, W indicates Read Write and S indicates the Server edition of QODBC

The second and third characters indicate the QuickBooks year number (e.g. 13 is for 2013 and earlier, 12 is for 2012 and earlier) that your QODBC license is compatible with.

The fourth character is "U" for the USA, "O" for Australia/New Zealand/South-East Asia, "K" for UK/Europe, Middle-East and Africa editions of QuickBooks. Other letters are for different regions.

The remaining characters form the rest of your serial number.

So if you have a Serial Number of W16U12345678 your QODBC license is a Read Write version compatible with QuickBooks 2016 US edition and earlier.

If you are using QODBC Read Only which comes with QuickBooks Enterprise, then you will notice Licensed To: QuickBooks Enterprise User in the middle of the About Tab below the “Check website for updates”.

Licensing FAQ:

Question 1:

How can I know for which year and QuickBooks my QODBC license valid for? Can install higher QODBC version with the lower license?

Answer 1:

QODBC license is licensed for QuickBooks Version(Year). E.g If you have QODBC Licensed for 2015, You can use QODBC with QuickBooks 2015,2014,2013 and so on but not with QuickBooks 2016.

You can install QODBC v15,v16 with no upgrade cost. Upgrade cost is only applicable when your license does not match the year.

For Example:
If you have QODBC licensed for 2015 & you are using QODBC v15 & QuickBooks 2015, you can install QODBC v16 and use it with QuickBooks 2015.

Question 2:

How do I know what is my CD KEY??

Answer 2:

You can get your CD KEY from purchase email from your registered email ID. In case you have deleted/lost email, please raise a support ticket with "Sales - Registration - Activation Department" Click Here for raising a support ticket.


Also Refer:

QODBC Licensing Information
QODBC with QRemote Licensing Information
How to activate QODBC
How to deactivate QODBC and How to transfer license to a new computer
For Purchasing QODBC License click here

Troubleshooting - How to get Advanced Pricing Module in QODBC

Problem Description:

We are using advanced pricing module in QuickBooks and would like to know what tables we need to access to pull that information for the system.  

Solution:

Advanced pricing module data (Price Rules) is not available through the Intuit SDK so they are not available through QODBC.

QODBC is an ODBC driver for QuickBooks. It uses the QuickBooks SDK to communicate with QuickBooks, which means if Intuit doesn’t expose one feature to the application in SDK, QODBC could not do it either.

Also Refer:

How to export QuickBooks data not available in QODBC

Troubleshooting - How to close SQL Linked Server connection

Problem Description:

We are using QRemote with SQL Linked Servers with several different QuickBooks files. How can we close the connection to a QuickBooks file after the query has run, then open to connect to another database?

Solution:

SQL Server Linked Server automatically handles disconnect.

SQL Server Linked Server does not have a disconnection command which can be fired/executed.

After the query is executed you will have to wait for 30-45 seconds, if there is no activity on the linked server connection SQL Server will automatically send the disconnect command.

Troubleshooting - Reporting Ship To Addresses

Problem Description:

Has anyone run a report that will pull the all the detail for a range of invoices? In particular, I'm looking to run a report that shows ship to addresses for particular products over a date range.

Solution:

Please use below query to get ship to addresses for particular products over a date range.

select InvoiceLineItemRefFullName, RefNumber, TxnDate, ShipAddressAddr1, ShipAddressAddr2, ShipAddressAddr3, ShipAddressAddr4,ShipAddressAddr5, ShipAddressCity, ShipAddressState, ShipAddressPostalCode,ShipAddressNote from InvoiceLine where TxnDate >= {d'2009-01-01'} and TxnDate <= {d'2009-03-01'} and (InvoiceLineItemRefFullName = 'Cabinets' or InvoiceLineItemRefFullName = 'Window') order by InvoiceLineItemRefFullName, RefNumber, TxnDate

Troubleshooting - SP_Report Changing Days Per aging using QODBC

Problem Description:

I recently discovered QODBC and have been playing around with it for a few days now. It's pretty good.

The problem I have is when I try to to get an A/P aging. The A/P aging has a default of 30 - 90 days. I need the report to show 180 -720 days. I use the example A/P aging report...

sp_report APAgingDetail show TxnType_Title, Date_Title, RefNumber_Title, Name_Title, DueDate_Title, Aging_Title, OpenBalance_Title, Text, Blank, TxnType, Date, RefNumber, Name, DueDate, Aging, OpenBalance parameters DateMacro = Today, AgingAsOf = 'Today'

...but this does not let me change the SQL statement as it is accessing a stored procedure report. The report runs fine; it's just the days that are wrong. Can anyone tell me how I can change the days per aging?

Solution:

AgingAsOf can be either ReportEndDate or Today depending on how you want to use your system date or QuickBooks date.

When using:

sp_report APAgingDetail show Text, Blank, TxnType, Date, RefNumber, Name, DueDate, Aging, OpenBalance parameters DateMacro = 'All', AgingAsOf = 'Today'

You can't change the Interval (days) and Through (days part due), like you can using the QuickBooks UI.

Troubleshooting - Code differences between QODBC Desktop and QODBC Online

Problem Description:

I have a MS Access application using QODBC to connect to desktop QuickBooks. Can I use the QODBC Online driver to connect to QuickBooks Online without changing my MS Access code?

Solution:

QODBC Online is the different product from QODBC Desktop driver. So you cannot use QODBC Desktop driver with QuickBooks Online. You need to use QODBC Online driver to connect with QuickBooks Online.

Most of the Tables, table columns, reports, report columns & report parameters in QuickBooks Desktop & Online are same. But not all the tables, reports & fields are available in QuickBooks desktop are available in QuickBooks Online. You might have to change few fields to match with QuickBooks Online. You need to refer QODBC Online reports/tables/fields & make changes in your code.

Please refer Difference between QODBC for QuickBooks Desktop and Online & make required changes in your code & use code with QODBC Online.

Troubleshooting - Connection Serial, Limitation , Queue and upper limit

Problem Description:

How many concurrent connections does the Server edition support?

Is the product QB version specific, requiring additional purchases with each version. AKA. Upgrading from V15 to V16?

Solution:

There is no limit on QODBC for the concurrent connection but more the number of connection more QuickBooks has to work. QuickBooks SDK will process all the request in a sequence, so if have 3 connection and 3 queries going at same time, SDK will execute it in sequence.

QODBC license is licensed for QuickBooks Version(Year). E.g If you have QODBC Licensed for 2015, You can use QODBC with QuickBooks 2015,2014,2013 and so on but not with QuickBooks 2016.

You can install QODBC v15,v16 with no upgrade cost. Upgrade cost is only applicable when your license does not match the year.

For Example:

If you have QODBC licensed for 2015 & you are using QODBC v15 & QuickBooks 2015, you can install QODBC v16 and use it with QuickBooks 2015.

Using ADODC and ADODB with QODBC

Download Sample

ADODB with QODBC

Open VB6, you can find it via Windows Start->All Programs->Microsoft Visual Studio 6.0 :

Create New Standard EXE project.

Then Add "Command Button" by double click on command button Icon. Command button will be added rename it to Get Customer via ADODB:

Double click on Command Button & add below code in the command button click event:

Private Sub Command1_Click()

Dim oConnection As ADODB.Connection
Dim oRecordset As ADODB.Recordset
Dim sMsg As String
Dim sConnectString As String
Dim sSQL As String

sConnectString = "DSN=Quickbooks Data;OLE DB Services=-2;"
sSQL = "SELECT top 10 Name FROM Customer"
Set oConnection = New ADODB.Connection
Set oRecordset = New ADODB.Recordset
oConnection.Open sConnectString
oRecordset.Open sSQL, oConnection, adOpenStatic, adLockOptimistic
sMsg = "**********************" & Chr(10)
Do While (Not oRecordset.EOF)
sMsg = sMsg & oRecordset.Fields("Name") & Chr(10)
oRecordset.MoveNext
Loop
sMsg = sMsg & "**********************" & Chr(10)
MsgBox sMsg

oRecordset.Close
Set oRecordset = Nothing
oConnection.Close
Set oConnection = Nothing

End Sub

Now execute the code from Run >> Start With Full Compile

Double click on Get Customer via ADODB which will get top 10 customer's name & display it in msg box:

ADODC with QODBC

Now we will add ADODC control in the same project which we created in above ADODB example.

New we will configure ADODC control by right click on ADODC control & click on ADODC Properties:

From General tab, Select ODBC Data Source QuickBooks Data.

Navigate to RecorSource tab, Select Command type to 2 - adCmdTable & table name Customer and click OK.

Now we will add three text box which will show Customer table data through ADODC control.

Now we will configure text box for display data from ADODC control. Choose DataSource Adodc1 (i.e. ADODC Control name) & DataField FullName (i.e. Field name which you want to show):

Same way we will configure other two text box with Phone & Email field.

Now execute the code from Run >> Start With Full Compile

By clicking on "Next" button, next customer data will be displayed.

Troubleshooting - How to cancel subscription of QODBC Desktop Driver for QuickBooks Online

Problem Description:

I want to cancel my QODBC Online monthly subscription.

How to cancel the subscription of QODBC Desktop Driver for QuickBooks Online?

Solution:

You can manage the subscription of QODBC Online using the link which you received in your renewal email.

You will find the link as below in your renewal email.

https://sites.fastspring.com/flexquarters/order/s/FLE111111-1111-111111

Please visit that link & click on Cancel Subscription to cancel your QODBC Online subscription:

Troubleshooting - Changes to the Integrated Application Authentication for QuickBooks

Intuit is reinforcing existing security features that help protect QuickBooks customers’ sensitive information.
Refer : Intuit's News : Changes to the Integrated Application Authentication for QuickBooks Desktop users


As a result of this effort, Intuit is delivering an update that impacts third-party applications that connect to QuickBooks using the QuickBooks SDK.

A new file specific to a Windows user in a given machine is created on user login that provides access to an SDK app in QuickBooks.

The implementation of this update will require customers to re-enter their login-in credentials & authorize application(i.e QODBC) in QuickBooks.

For Example, You have 4 windows users. All of those 4 windows users uses QODBC via Microsoft Excel,Access, Crystal or any other applications. You will need to authorize EACH applications from all the 4 Windows user. That means you will need to login to the 1st windows user, authorize all the applications that will be using QODBC, then login to 2nd Windows user and authorize all the applications that will be using QODBC. This is because Intuit's LGB file which was common earlier is now changed to new a method and integration information will be stored for each Windows user separately.

Above is applicable for a Single machine, Terminal Services(Remote desktop connection) or Workstation(s).

Problem Description:

Get the following errors from QODBC driver:

ERROR [00000] [QODBC] QB Begin Session Failed. Error = 8004041d,80040418 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.

Test connection to Quick Books - FAILED: "[QODBC] QB Begin Session Failed. Error = 8004041a. 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"

Solution:

You need to follow below steps to reauthorize QODBC for QuickBooks.

1. Login to Windows, Open QuickBooks & login to company file as Admin.
2. Switch Company File to Single User Mode.


3. Connect using your application. It should pop-up Data Access Certificate on QuickBooks, Please accept the Certificate. QuickBooks issue Certificate is for each application, So you need to accept the certificate for all application which you are using with QuickBooks.




4. You need to log in for each Windows Users who is accessing QuickBooks Data using QODBC.

If Windows User/Work Station changed, then you need to reauthorize application using above steps.

If the company file has Personally Identifiable Information (PII) in QuickBooks, users will be required to login with a password; the SDK app will only be allowed to connect once the login has been completed for that user.

When logging in, customers will be instructed to set up a strong password. Customers should use unique letters and numbers in a password, not basic words that can easily be found online or in the dictionary.

Troubleshooting - QODBC installer error Windows cannot find explorer.exe. Could not execute the external program

Problem Description:

We downloaded the QODBC trial from your website. At the end of the installation process - after clicking the 'finish' button, a dialog appears saying that 'explorer.exe' cannot be found.

I am getting below error:

Windows cannot find 'C:\Users\SAMMYH~1\WINDOWS\explorer.exe'. Make sure you typed the name correctly, and then try again.


Could not execute the external program

C:\Users\SAMMYH~1\WINDOWS\explorer.exe


The installation process aborts and the software is then uninstalled.

Solution:

This issue occurs when using QODBC V16.0.0.317 installer & Windows folder is personalized to point to User's Roaming profile. We have fixed this issue in our latest version of QODBC (V318 or above). You can download QODBC latest by clicking here.

If you want to use QODBC V317, then please follow below steps to resolve the issue:

1. Open windows Explorer.
Navigate to
C:\Windows\




2. Inside the "Windows" folder you should find "explorer.exe"


Copy explorer.exe, By right click on explorer.exe & click copy.


3. Navigate to

C:\Users\Windows Username\Windows\
(Windows Username = The current logged in Windows Username)

In this example my Windows username is Dewani. So I am navigated to C:\Users\Dewani\Windows


4.Paste the copied file in the directory C:\users\Windows Username\Windows\
In this example my Windows username is Dewani. So I am pasting the file to C:\Users\Dewani\Windows By right click on C:\Users\Dewani\Windows folder & click Paste.




5. Now try to install QODBC again. You will not get this error.

How to use QODBC with SSIS

Either QODBC or QRemote is required on the machine where SSIS package will be developed, deployed or SSIS services are installed.

Development - On the machine, you are developing SSIS package - You should have QODBC installed.

Deployment - On the machine, you wish to deploy or run the SSIS Package - You should have QODBC installed.

The first step is to install and test QODBC.

Please refer Connecting QODBC Driver to QuickBooks for the First Time (Video)

If QuickBooks application is installed on another machine, then you can connect to QuickBooks from a remote machine using QRemote Server. You need to install QODBC on both machines.

Please refer Accessing QuickBooks Data Remotely using QODBC & QRemote. (Video)

When you are deploying SSIS package to SQL Server you need to configure QRemote client to connect with QuickBooks.

Please follow below steps to use QODBC with SSIS

1. Go to Start menu & open SQL Server Business Intelligence Development Studio from SQL Server.

2. Create new Integration Service Project by clicking on Integration Service Project & Enter Project Name, set project location and click OK.

The Project is created.

3. In this sample project, we will transfer QuickBooks data using ADO.Net source to Flat File Destination. To perform we need to add Data Flow Task in Control Flow tab. You can add it by double click on Data Flow Task.

4. Now we need to add ADO.Net Source in Data Flow tab. You can add it by double click on ADO.Net Source.

5. Now we need to configure ADO.Net Source. By right click on ADO.Net Source & click on Edit.

Add new ADO.Net connection by click on New.

Add new Data connection by click on New.

Select Provider to .Net Providers\Odbc Data Provider, Select DSN to QuickBooks Data QRemote and click on Test Connection.

Test Connection Succeeded.

Click on OK & you will notice connection is added. You can select Data Access Mode as Table or view for accessing whole table data. You can also select Data Access Mode as SQL command for accessing table data with condition & accessing report data using sp_report. In this example, I have selected Table or view as Data Access Mode & selected Customer table.

You can preview output data by clicking Preview button.

Close the Preview by clicking the close button & click on OK to save configurations.

6. Now we need to add Flat File Destination in Data Flow tab. You can add it by double click on Flat File Destination.

7. Now we need to link ADO.Net Source with Flat File Destination by dragging link from ADO.Net Source to Flat File Destination.

8. Now we need to configure Flat File Destination. By right click on Flat File Destination & click on Edit.

Add new Flat File connection by click on New.

Select Flat File Format & click OK.

Select Destination file in which you want to store output using Browse button.

Enable Unicode & Column names in the first data row option & Click on OK to save configurations

You will notice OK button is disabled, To enable it you need to click on Mapping, then click OK to complete configuration.

9. Run SSIS package to perform transfer operation by clicking play icon.

SSIS Package execution completed & 163 rows are transferred from ADO.Net Source to Flat File Destination.

Here is a Flat text file which is containing ADO.Net Source result.

Please click here for downloading Sample SSIS Package.

Problem Description:

I am evaluating your driver and have had success running SELECT queries against QB in SSMS, where I was able to use the QRemote DSN. When setting up ODBC connection in SSIS , I get an error when trying to enumerate the columns.

Unknown Data type found on column

Solution:

You need to select “ADO.NET Source.” instead of ODBC Source in SSIS package to resolve this error.

Troubleshooting - Can I use QODBC with QBB ( QuickBooks backup ) file

Problem Description:

I am trying to find a way we can pull data from a .QBB file without having to restore the .QBB file and/or go through QuickBooks.

Is QODBC capable of doing so? I watched a few videos and it appeared that all files used were regular company files.

Solution:

It is not possible to pull data from a .QBB file without having to restore the .QBW file and/or go through QuickBooks because QuickBooks SDK does not provide this feature.

The only way that QuickBooks allows us to access any data is if there is a QuickBooks session running on the machine with the company file is loaded.

QODBC is an ODBC driver for QuickBooks. It uses the QuickBooks SDK to communicate with QuickBooks, which means if Intuit doesn’t expose one feature to application in SDK, QODBC could not do it either.

Troubleshooting - QB Begin Session Failed. Error - Unauthorized-401

Problem Description:

I was able to use QODBC Online. Suddenly, I am getting below error when I tried to connect QBO using QODBC Online. It was working properly. No known changes to Windows or QODBC. Begin Session Failed. S0000 00000 [QODBC] QB Begin Session Failed. Error - Unauthorized-401 - - Fault Exception of type: AUTHENTICATION has been generated.

Solution:

Authorized access token for QBO will remain active for 180 days. An authorized access token expires after 180 days. When this occurs, responses to calls to QuickBooks Data Services and the QuickBooks Online API indicate that the access token is invalid.

So, You need to reauthorize/reconnect QODBC Online at QBO to resolve the issue.

Please refer How to Reconnect QODBC Online with QuickBooks Online Edition

Troubleshooting - DSN Connection Not Consistent across multiple computers

Problem Description:

I have a pass through query in access:

Select * from Item

The connection string is as follows:

ODBC;DRIVER={QODBC Driver for QuickBooks};SERVER=QODBC;DFQ=x:\qb\MyQBcompanyfile.qbw;OpenMode=F;OLE DB Services=-2;OptimizerOn=No;

This works on pc #1 if QB file is open OR closed (desired behavior).

This ONLY works on pc #2 if QB File is Closed.

Why is it operating different?? I am using the same access file on both pc.

I need this to be running on some computers in the office. Some of the computers are allowed to use QuickBooks, and some are not, so I need a flexible DSN connection string that will work for both circumstances.

Solution:

Please verify company file path from non working machine. The other computer might accessing the company file mapped via network name i.e. \\servername\folder\ (e.g \\qbfileserver\qb\MyQBcompanyfile.qbw ), when the connection string is using a mapped drive i.e. x:\

Please Start QuickBooks from non working machine, login to the company file, press f2 and verify if the file path is the same in connection string & test again.

Troubleshooting - QODBC Logging in with Wrong User account

Problem Description:

I am using ms access. I have the integrated application certificate set up correctly (see screenshot). The username for this certificate is "odbc".



Quickbooks is closed.

Ms access file connects to QB via the connection string:

"ODBC;Driver={QODBC Driver for QuickBooks};DFQ=D:\QB\MyCompanyFile.qbw;OptimizerOn=No;IAppAutomaticLogin=n;OpenMode=F;OLE DB Services=-2;"

Connection works.

Another user tries to login in as "Admin" into QB on another computer, but it fails and says already logged in. See screenshot.



Why is QODBC using the "Admin" account?? I was expecting it to use the "odbc" account.

Solution:

You need to remove QODBC integrated application entries in QuickBooks & companyfilename.lgb and delete it to resolve the issue.

Please refer Connection Lost Between QODBC and QuickBooks. QuickBooks Asking for Password for more details.

Troubleshooting - How do I see backorder items that have been invoiced but not shipped

Problem Description:

Could someone kindly provide me with a sample, or is there a stored procedure that would allow me to only pull out back ordered invoices from the invoice table?

If a customer orders some items, we create an invoice. Then if some things are back ordered, when the packing slip is created it shows they were not sent out, and that item is back ordered. I was looking for a query or a SP that would show me only invoices that have not been completely shipped or just all the items on back order.

Solution:

All you really need to do is use the ItemInventory table to pick up the quantity on hand and compare it with the ordered quantity ordered and invoiced to date (invoiced or not) and call the column "Qty to Pick".

Something along the lines of:

SELECT SalesOrderLine.SalesOrderLIneItemRefFullName as Type, SalesOrderLine.TxnDate as Date, SalesOrderLine.DueDate, SalesOrderLine.RefNumber as Num, SalesOrderLine.CustomerRefFullName as Name, SalesOrderLine.SalesOrderLineQuantity as "Qty Ordered", SalesOrderLine.SalesOrderLineInvoiced as "Qty Invoiced", (SalesOrderLine.SalesOrderLineQuantity - SalesOrderLine.SalesOrderLineInvoiced) as "Qty to Pick", ItemInventory.QuantityOnHand as "Qty Available", ItemInventory.QuantityOnOrder as "Qty on Back Order" FROM SalesOrderLine, ItemInventory where SalesOrderLine.SalesOrderLineItemRefListID = ItemInventory.ListID and SalesOrderLine.IsFullyInvoiced = FALSE and SalesOrderLine.SalesOrderLineInvoiced < SalesOrderLine.SalesOrderLineQuantity

Troubleshooting - Trying to update ItemInventoryAssemblyLine table

Problem Description:

I am using MS Access connected to Quickbooks via QODBC. I am using queries in MS Access to load/synchronize Inventory data from my master inventory list, which is kept outside of QuickBooks, to make sure QB has the latest inventory data. All our products are Inventory Assemblies.

I have successfully inserted ItemInventoryAssemblyLine entries , but now I'm trying to update the Quantity information on component parts for existing assemblies.

To do the update, I need to join to a local table that I've created from the external inventory data, which I've loaded with the ListID, ItemInventoryAssemblyLnItemInventoryRefListID, and FQPrimaryKey values from ItemInventoryAssemblyLine, in order to facilitate joins.

Here's my SQL (from MS Access Query Designer):

UPDATE ItemInventoryAssemblyLine INNER JOIN Assemblies_with_PK ON ItemInventoryAssemblyLine.FQPrimaryKey = Assemblies_with_PK.FQPrimaryKey SET ItemInventoryAssemblyLine.ItemInventoryAssemblyLnQuantity = [Qty];

"Qty" is a column in the local table that has the updated Quantity that I'd like to update into the Quickbooks table.

When I run this query, I get the dreaded "Error parsing complete XML return string." error. I have tried alternatively joining on the combination of ListID and ItemInventoryAssemblyLnItemInventoryRefListID instead of FQPrimaryKey with the same result.

I have been able to update Custom Fields in the parent ItemInventoryAssembly table using the exact same approach with no problems.

Any help with this would be greatly appreciated!

Solution:

Please update your QODBC to latest QODBC Version and test again.

Please click here to get a QODBC latest version.

If you are still getting the same error after updating version, then I kindly request you to please raise a support ticket to the QODBC Technical Support department by clicking here

Troubleshooting - QuickBooks Displays a Revoked Certificate Warning

Problem Description:

I am trying to connect to QuickBooks using QODBC. At a time of connection, QuickBooks Displays a Revoked Certificate Warning.

Solution:

Please update your QODBC to latest QODBC Version and test again.

Please click here to get a QODBC latest version.

If you are still getting the same error after updating version, then Please check digital signature of the application you are using like crystal report, excel.

For Example:

If you are using MS Excel and the getting error, then please check digital signature in MS Excel.

Open task manager right-click on EXCEL.EXE and click on Open File Location.

You will be navigated to application location. In this example we will navigate to Excel exe location.

Once we reach to exe location, then we need to right-click on exe and click on Property. In this example, we will right click on EXCEL>EXE and click on Property.

Navigate to Digital Signatures tab & click on Details.

Click on View Certificate to see certificate validity details.

You can see certificate validity details.

If your application Digital Certificate validity is expired, then you need to get in touch with Vendor of application to resolve the issue.

Windows Enforcement of Authenticode Code Signing and Timestamping

On Windows 7 platforms and above, the following are new guidelines from Microsoft:

• Microsoft will no longer allow new SHA-1 code signing certificates to be used for signing files on Windows 7 and above starting Jan. 1, 2016.
• Files signed previously with a SHA-1 certificate will continue to work on Windows 7 and above for an additional year as long as they were time-stamped before January 1, 2016.
• Windows 7 and Server 2008 R2 will require a hotfix for SHA-256 support.
• Starting on Jan. 1, 2017, all SHA-1 signed files will be blocked on Windows 7 and above, regardless of when they were time-stamped.

On Vista and Server 2008 platforms:

• Microsoft will execute end of life support for Vista on April 2017, and for Server 2008 on January 2020.
• SHA-1 certificates will be supported through the end-of-life for these operating systems.
• There will be limited support for SHA-256 on these platforms which will require a patch nd only allows for downloads or installations of SHA-256 signed content.

Microsoft TechNet:
Windows Enforcement of Authenticode Code Signing and Timestamping

On Vista and Server 2008 platforms:
Microsoft Authenticode - Dual Code Signing Instructions with SHA1 & SHA256 hashing Algorithm


For more details refer:
Microsoft Windows SHA-1 & SHA-2 Code Signing Hash Algorithm Support
SSL News
SHA-1 Hash Algorithm Migration for SSL & Code Signing Certificates
SHA-1 Deprecation, On to SHA-2

Also refer:

Revoked Certificate Errors With QuickBooks Desktop Apps