Databases
StackOverflow2013
Postsdbo
POQB PRO 2013 + Web Connector with closed company
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQB PRO 2013 + Web Connector with closed company
    text
    copied!<p>I have Quickbooks Pro 2013 with the Web Connector installed. </p> <p>I have created a sync application, granted permissions and everything, and I get the Web connector to exchange data between the company file (QB PRO 2013) and a web service successfully. </p> <p>This happens only while QB PRO 2013 is <strong>OPEN</strong>. It doesn't require a logged in user, just keeping the application open is good enough for the Web Connector to connect to the company file and exchange data.</p> <p>The thing is when I close the application the Web Connector starts complaining with a <strong>QBWC1013</strong> error, saying: <strong>Could not start QuickBooks.</strong> - second row in this link: <a href="http://www.zoho.com/crm/help/quickbooks/troubleshooting.html#sthash.hk3Dc8dl.dpuf" rel="nofollow">http://www.zoho.com/crm/help/quickbooks/troubleshooting.html#sthash.hk3Dc8dl.dpuf</a></p> <p>I'm used to QB POS, where I don't need the company open. Is this behavior different on non POS products ? Do I need to keep QB open all the time ? The path to the company file is OK as well as the syncing logic, we are able to connect, authenticate, exchange data both ways smoothly but only while QB is open (being logged in is not necessary, just keeping the app open).</p> <p>It is like the Web Connector needs a running instance of QuickBooks to authenticate, because when it does so, QuickBooks flickers like if someone were logging in and then logging out. </p> <p>The Web Connector application has been granted full access and Admin login to the company file.</p> <p>Any thoughts :)</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload