Cannot Get Connected to QuickBooks Desktop

Applies to QuickBooks Desktop for PC.


If you are having problems getting the invoiceASAP Desktop Connector to connect to your QuickBooks account, there can be several reasons why.

This article walks you through the most common reasons to the least common reasons.

Chances are, you will find the reason why you cannot get connected in this article.


First Things First

If you have not viewed the documentation that shows how to get connected, please do this first.

You might be surprised how many people cannot get connected because they have not pressed the "Connect" button.

Here is the link:   Getting Connected to QuickBooks


If you still have a problem, please walk through each of the steps below.

After fixing the problem described, close the invoiceASAP Connector, then re-open it and follow the instructions from Getting Connected to QuickBooks.


The Four Most Common Reasons Why You Cannot Connect

Reason #1:  Your QuickBooks File is not open.  

This is easy to fix.  Simply open your QuickBooks file.


Reason #2:  You Are In Multi-User Mode.  

For the initial sync, you must be in Single User Mode in your QuickBooks. 

After you are connected and have run the first sync, you can switch back to Multi-User mode. 


Here is how to check if you are in Single User mode or Multi-User mode

From your QuickBooks, select File.

Does it say "Switch to Multi-User Mode?"  If so, then you are in Single User mode, and you can continue to the next step.

If not, change switch to Single User Mode, close the invoiceASAP Connector, re-open it and go to Setup to get connected.




Reason #3:  You are not an Admin.

You must be an admin to be able to get connected to your QuickBooks company from invoiceASAP. 

If you don't know whether or not you are an Admin, continue to the next step. 

You can only do the next step if you are an Admin.


Reason #4:  You Have Not Given invoiceASAP Permission to Access Your Company File

From your QuickBooks, select Edit > Preferences.



On the left nav, select Integrated Applications.

On the right pane, select Company Preferences.

NOTE:  If you cannot view the Company Preferences, then you are not an Admin.

Please have an Admin login to your account and try to get Connected again.

Make sure that the checkbox that reads, "Don't allow any applications to access this company file" is unchecked.

If you see invoiceASAP listed, make sure it is checked, then click on the Properties button.



On the Properties button, make sure you have "Allow this application to read and modify this company file" checked.

Click Okay.




Company Name Issue

Although not very common, there are some instances where the QuickBooks File does not have a company name.

This is very easy to check.

From your QuickBooks, select Company > Company Info



Make sure that you have a Company Name filled in. 

The Company Name cannot be blank, as shown below.



Getting Technical with the Log File

If you have tried all of the above and you still cannot get connected, then it is time to look at the Log File to see what the error is.

The Log File is in a Hidden Folder, and it is accessed via a hidden button.


From the invoiceASAP Connector, click on Advanced Mode.




Using the screen shot below, double-click in the white space. 

This is where the hidden button is located.




 A hidden folder is opened.

Double-click on the file called LogFile.log to open it in Notepad, then scroll to the bottom of the file.





The LogFile is pretty technical, but there are some key words and phrases to look for that will tell you what the problem is.

Each of these errors is listed below with the key words to look for in bold red.

This should make it easier for you to spot the error and fix it immediately.


No Permission

Here is an example of a log file where the user does not have permission to get connected.

If you get this error, you have not given invoiceASAP permission to access your company file.

Please refer to Reason #4, above. 

7/2/2013 3:22:04 PM: Exception Details:
Type: System.Runtime.InteropServices.COMException
Message: 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.
Source: QBXMLRP2.RequestProcessor.1
Target: Void BeginSession(System.String, Interop.QBFC10.ENOpenMode)
Stack Trace:    at Interop.QBFC10.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
   at QuickBooksDP.QBSessionMgr.OpenConnection(String sFile, String sAppName, Boolean bIsQBOE)
7/2/2013 3:22:04 PM: about to try beginsession 2nd time
7/2/2013 3:22:05 PM: Error occured during OpenConnection: 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.
7/2/2013 3:22:05 PM: Connection type: ctLocalQBD
7/2/2013 3:22:05 PM: We have been unable to establish a connection with QuickBooks. Please try again.
7/2/2013 3:22:05 PM: init failed exception thrown - details: Exception of type 'DataProvider.InitFailed' was thrown.


COM Error:

For a COM error, you are looking for the word "COM" in the log file. 

Please note that there was a COMException in the example above, but its message was very clear that it was a permission issue.

Here is an example (key word in red):

Type: System.Runtime.InteropServices.COMException
Message: BeginSession method has not been called or it did not succeed.
Source: QBFC10.QBSessionManager.1
Target: System.String[] get_QBXMLVersionsForSession()
Stack Trace:    at Interop.QBFC10.QBSessionManagerClass.get_QBXMLVersionsForSession()
   at QuickBooksDP.QBSessionMgr.GetQBFCLatestVersion()
   at QuickBooksDP.QBSessionMgr.GetLatestMsgSetRequest()
   at QuickBooksDP.QBCompanyInfoDP.get_SalesTaxEnabled()
   at SyncMgr.SyncMgrTxns.SyncData()
   at SyncMgr.SyncMgrAF.RunSync()
1/22/2013 12:03:17 PM: sync failed
1/22/2013 12:03:17 PM:

 You may also get an error similar to this one:

Unhandled exception has occurred in your application. If you click Continue the application will ignore this error and attempt to continue. If you click quit the application will close immediately.
Retrieving the COM class factory for component with CLSID {6C9E80E3-B780-A693-5E5C6BDC83A9} failed due to the following error. 800736b1


A COM error occurs in some versions of Windows XP or Windows 7 because Microsoft has put its COM objects in a place that Intuit does not know about.

To resolve this error, download and install this file:


Anti-Virus Software Error:

Some anti-virus software programs prevent InvoiceASAP from connecting to your QuickBooks, but the error is rather obtuse.

8/7/2014 8:21:46 AM: Exception Details:
Type: System.Net.WebException
Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Source: System
Target: System.IO.Stream GetRequestStream(System.Net.TransportContext ByRef)
Stack Trace:    at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at CustomSyncProcessor.DPFactory.TestConnection(String sUserName, String sPwd, String sServiceUrl)

 If you get the SSL/TLS listed in the log file, then you need to disable your Anti-Virus software in order to connect to get connected from InvoiceASAP to your QuickBooks file.



This error is a little harder to figure out, as the problem is not in the Exception part of the log, but a little further down in the log file.

We have seen this error occur only twice of all the QuickBooks Desktop users we have.

Here is an example:

6/18/2013 12:34:52 PM: Exception Details:
Type: System.Exception
Message: We have been unable to establish a connection with QuickBooks. Please try again.
Source: QuickBooksDP
Target: Boolean Initialize()
Stack Trace:    at QuickBooksDP.DPFactoryQB.Initialize()
   at QuickBooksDP.DPFactoryQB.Initialize(Config cfg)
   at SyncMgr.SyncMgrAF.RunSync()
   at SyncMgr.SyncRunner.SyncThread(Object objConfigFile)
6/18/2013 12:34:52 PM: sync failed
6/18/2013 12:34:52 PM: starting sync operation
6/18/2013 12:34:52 PM: opening connection to QB file: ''
6/18/2013 12:34:53 PM: OpenConnection2 successful.
6/18/2013 12:34:53 PM: BeginSession successful.
6/18/2013 12:34:53 PM: Unexpected error. Check the "qbsdklog.txt" file for possible additional information.


The qdsdklog.txt file is an Intuit file.

It is located in one of these two locations (depending on your operating system):

C:\Documents and Settings\All Users\Application Data\Intuit\QuickBooks


When you find the qbsdklog.txt file, open it in NotePad.

Here is an example of the qbsdklog.txt file:

20130606.172625    I    4268    RequestProcessor    ========= Started Connection =========
20130606.172625    I    4268    RequestProcessor    Request Processor, QBXMLRP2 v12.0
20130606.172625    I    4268    RequestProcessor    Connection opened by app named 'invoiceASAP QuickBooks Connector'
20130606.172625    I    4268    RequestProcessor    OS: Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit
20130606.172625    I    4268    RequestProcessor    Current Process is elevated
20130606.172625    I    4268    RequestProcessor    Current User is in AdminGroup
20130606.172625    I    4268    RequestProcessor    Current Process is ran as Admin
20130606.172625    I    4268    RequestProcessor    Current Process Integrity Level : 3000
20130606.172626    I    4268    RequestProcessor    Getting the IUnknown COM instance of QB
20130606.172626    I    4268    RequestProcessor    Opening the file in the DoNotCare mode.
20130606.172626    E    4268    RequestProcessor    Process Request error = 80042505, QBXML components have not been installed.
20130606.172626    E    4268    RequestProcessor    Process Request error = 80042505, QBXML components have not been installed.
20130606.172626    E    4268    RequestProcessor    Process Request error = 80042505, QBXML components have not been installed.
20130606.172626    E    4268    RequestProcessor    Process Request error = 80042505, QBXML components have not been installed.
20130606.172626    E    4268    RequestProcessor    Unable to process Host Query request.
20130606.172626    I    4268    RequestProcessor    Connection closed by app named 'invoiceASAP QuickBooks Connector'
20130606.172626    I    4268    RequestProcessor    ========== Ended Connection ==========

 If you see this error, then there is a component in your QuickBooks Installation that hasn't been installed.

Here is a link to a blog that describes the problem and the resolution:



The above reasons are the reasons that we have found for why you cannot get connected to your QuickBooks.

If you have gone through each of the above and still cannot get connected, please click here to create a new support ticket.

Please let us know that you have read this article and tried all of the above steps.

You can also attach a copy of the LogFile.log to the support ticket, and that will help us a lot.

We will get in touch with you and probably schedule a Join.Me session to see what is happening with your QuickBooks Connector.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk