Tagged: error, quickbooks
This topic contains 18 replies, has 6 voices, and was last updated by contact2 4 years, 3 months ago.
Opensync is not able to open quickbooks “error: Could not start Quickbooks.: -2147220472” it works for 3 sync jobs and then stops working.
This is a catch all error generated by QB for a number of reasons. You need to look at the QBSDKLOG.TXT file to determine a more accurate reason for the failure. Also, search these forums for this error as it has been discussed extensively in other threads.
I’ve look and the QBSDLOGS and here is what the logs say
”
20131223.114444 I 9320 RequestProcessor ========= Started Connection =========
20131223.114444 I 9320 RequestProcessor Request Processor, QBXMLRP2 v13.0
20131223.114444 I 9320 RequestProcessor Connection opened by app named ‘OpenSync’
20131223.114444 I 9320 CertVerifier The file does not contain an Authenticode signature.
20131223.114447 I 9320 RequestProcessor OS: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
20131223.114447 I 9320 RequestProcessor Current Process is elevated
20131223.114447 I 9320 RequestProcessor Current User is in AdminGroup
20131223.114447 I 9320 RequestProcessor Current Process is ran as Admin
20131223.114447 I 9320 RequestProcessor Current Process Integrity Level : 3000
20131223.114448 I 9320 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20131223.114448 I 9320 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20131223.114449 I 9320 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20131223.114449 I 9320 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20131223.114450 I 9320 RequestProcessor Previous instance of QB is going down..! Wait and retry to get a new instance.
20131223.114450 E 9320 RequestProcessor Could not find or create an instance of QuickBooks using InstanceFinder
20131223.114450 I 9320 RequestProcessor Connection closed by app named ‘OpenSync’
20131223.114450 I 9320 RequestProcessor ========== Ended Connection ==========
”
Ive search your forms on this and i haven’t seen a solution on how to resolve this issue. we’ve been down now for a week. can someone please help thank you.
Any updates, I am encountering the same issue?
This error generally occurs when you are running under Terminal Services. In this environment, you must leave QB open in the session where OpenSync is running.
Do the same rules apply to a Virtual Machine? Just curious…do we need to leave QB open and have OpenSync run at the same time?
Paul
So i resolved my issue, I’m running a complete Virtual environment and created a windows 7 box. openeync is running on it own virtual machine and running great. make sure to turn off windows updates and your firewall.
And you don’t have to keep Quickbooks open. OpenSync logs in on its own, and shutdowns. What is the interval length for your service? And what is your host system for the virtual environment? Could you provide some clues to possibly make my life a little easier. 🙂
Paul
hey Paul,
quick books doesn’t have to be open just the opensync app. I have opensync broke out into 4 different category, SO/PO, ITEMS, Vendors/Cust and everything else, I have opensync running every 1min and it never shuts down. Im running vmware esxi 5. let me know if theres anything i can help you with, Ive done alot of trouble shooting on this haha..
can we move our discussion offline? (email perhaps)??
Paul
right now, my test environment is in a Parallel Desktop VM (similar to your VMWare ESXI 5 environment). The target system is a WinXP SP3, and will eventually migrate to Win7, and the target Quickbooks file is on a shared network drive.
Paul
im running quickbook 14 with opensynce 2.0, my quickbooks file is on a shared network as well. whats your email address?
email me @ paul.brun<at>pbrunconsulting.com
I’d like to hear an update on this. I am getting the same error after upgrading to Quickbooks Premier 2014 and Opensync 2.0.
My problems went away when I migrated to a Windows 2012 Standard Server platform hosted within VMWare. I think Parallel Desktops runs the VM’s a little differently, so don’t know the exact cause. Also, running/hosting the software out of a Terminal Services environment is not ideal..
Paul
The forum ‘OpenSync’ is closed to new topics and replies.
Copyright © 2013 Synergration Inc