Knowledgebase
[QODBC-Desktop] Create DCOM Instance Error = 80070005
Posted by Juliet (QODBC Support) on 25 June 2010 09:15 AM

Troubleshooting: Create DCOM Instance Error = 80070005

Problem Description

All worked fine on QuickBooks and QODBC version 9, integrated to a web shipping system that is all hosted on XP PC. After upgrade both QuickBooks and QODBC to version 10, got the following error:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[QODBC] QB Open Connection Failed. Create DCOM Instance Error = 80070005, Unknown error. Created qbXMLRP2 OK.

Reset permission on the DCOM objects both using the tool and manually did not help any. But can run the TestDCOM.ASP and get successful messages on all objects tested. Use the VB sample program to query data just fine, however, anything through IIS like the DisplaySQL.ASP and qbcust.asp will produce the above error.

Solutions

     Somehow something is not 100% set correctly. You might try re-registering the DCOM items and setting them up again. Below are the lines to run at the Windows Start -> Run prompt:

"C:\Program Files\QODBC Driver for QuickBooks\qbXMLRPeQODBCInteractive.exe" /UnRegServer
"C:\Program Files\QODBC Driver for QuickBooks\qbXMLRPeQODBCInteractive.exe" /RegServer
"C:\Program Files\QODBC Driver for QuickBooks\qbXMLRP2eQODBCInteractive.exe" /UnRegServer
"C:\Program Files\QODBC Driver for QuickBooks\qbXMLRP2eQODBCInteractive.exe" /RegServer

     Then manually setup the DCOM settings again. Make sure you are in the Console session when running dcomcnfg. (Not Terminal serviced in).

(101 vote(s))
Helpful
Not helpful

Comments (2)
Paul King
27 December 2013 08:48 AM
This did not help in our case (version 14 access via MSSQL 2012). Had to run SQL service as a priv'd account to resolve. By the way, lots of us in the cloud - I wouldn't know what country my physical console is in in most cases. Mstsc /admin seemed to work ok.
Jack
08 July 2014 10:45 AM
Hi Paul,

When using Remote Desktop Connection, DCOM will work only if the user is connected to remote desktop & user session is active. If the user is disconnected & session is active, then DCOM will not work. User connection & session, both should be active (Session will be either console or any other session).
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please complete the captcha below (we use this to prevent automated submissions).