Knowledgebase
[QODBC-ALL] Troubleshooting - Microsoft Excel 2013 or Microsoft Access 2013 (Office 365 / 365) crashes / Required Activation
Posted by Jack - QODBC Support on 30 December 2015 10:24 AM

Troubleshooting - Microsoft  Excel 2013 (Office 365 / 2016) crashes / Required Activation

Troubleshooting - Microsoft  Access 2013 (Office 365 / 2016) crashes / Required Activation

 

Problem Description 1:

I am having significant difficulties with QODBC since upgrading to Quickbooks Enterprise 16.0. Right now the Test Connection in the QODBC Setup Screen comes back saying it is connected, and the VB Demo returns results, but Excel crashes as soon as you select using the Quickbooks Data* Database option in the connection wizard.

Problem Description 2:

I have today downloaded the QODBC drivers to start work on a development project but I am facing issue. If I click the Test Connection button on the General tab of the Setup dialog. The test is successful. But when I try and use MS Access 2013 or MS Excel 2013 and connect to a QB data set using the ODBC driver MS Access and MS Excel both crash.

Problem Description 3:

We have two licenses for QODBC Online. One is used at the consultants office and one is used by the client Admin. Both obtained authorization for access to QuickBooks using the same QBO Login.

 

The problem appeared this morning after the consultant (me) loaded a new copy of the Access 2016 code that the client is using. Because the DNS entries on the two different systems have different names, I attempted to use the Access Linked Data Manager to relink the databases to Access. When I did this, I got an Authorization error, which I interpreted to mean that I needed to reconnect the databases in the DNS object to QBO. I reverted to using VB Demo and it also got the authorization error. I then used the DNS Configure function for the 32 bit DNS entry for QODBC and disconnected from QB Online. I then connected to QB Online and everything functioned as expected. Now when I attempt to use VB Demo to access the QB Online Data, I got the message that prompted "QODBC Driver QuickBooks Online not licensed for this QuickBooks Edition"

 

Solution:

Due to some security added to Office 2013 & later version, this issue is happening. This issue only happens when using MS Office 2013 / 2016 / 365 and not with MS Office 2010 or downwards
MS Office is not allowing to write to the registry and thus QODBC those this error.

To fix this issue, please run the patch or follow the manual steps.

Patch:

Please close QuickBooks, Access, Excel any other application which is using QODBC.

Download fix patch by clicking here

Extract the file, Right click on zip file & click on Extract ALL


Select destination & extract file by clicking on Extract.


You will find two exe from extracted folder. First Double click "x64-Office2013Fix-20151221.exe". Please click on yes to run exe.


After the process is completed, Press any key to close the application.


Now, Double click "x86-Office2013Fix-20151221.exe". Please click on yes to run exe.


After the process is completed, Press any key to close the application.


Run your application and see if that has fixed the issue.

If above does not resolve the issue, then please follow below alternate solution(Manual Steps):

Manual Steps:

QODBC shows RegFile1 License error when using MS Excel 2013 or Access 2013, Excel Crash, Access Crash (Video)
MS Excel 2013 or Access 2013 (Office 365) crashes as soon as trying to connect to QuickBooks Data

 

(3 vote(s))
Helpful
Not helpful

Comments (5)
m.ezekiel
07 January 2016 05:44 PM
fix worked, thanks
Dat
18 January 2016 05:20 AM
I have this error for a long time with QBE 15 and Office 2013 but couldn't find the solution until now.
Jack
18 January 2016 07:49 AM
Hi,

Thanks for the update.

If you are still facing issue, I kindly request you to 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 following information, I kindly request you to 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
Roger
04 April 2016 05:14 PM
downloaded qb enterprise 2016, installed qodc driver that's part of it, installed the qodbc office2016 patch

I still get 'error retrieving evaluation days left' when trying to get external Access data when opened as administrator

QB support suggested I contact you
Jack
05 April 2016 08:08 AM
Hi Roger,

I would like to inform you that when QODBC is installed on a new machine it starts with 30-day evaluation (All features are active). But QODBC evaluation version will turn to Read Only edition for QuickBooks enterprise edition – automatically after 30 days (If QuickBooks Enterprise Edition v10 or above is installed).

So QODBC will turn to read only mode after 30 days. You can use it as read only. QODBC Read-only edition for QuickBooks Enterprise does not include QRemote License. So after 30 days, you may not be able to use QRemote.

If you are still facing issue in MS Office, I kindly request you to 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 following information, I kindly request you to 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
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).