I have an Automation Server where both the Control Room and the clients are installed. The Automation Server is accessed from another Main Server and so the Control Room. I have created some clients in the Control Room from the Main Server. I have logged in to 3 different sessions of the Automation Server and also logged in to the Clients which were created in the Control Room on the Main Server.Now, when i am trying to run a bot from the Main Server, the bot is running on the Automation Server but only in the first client logged in even if i have not selected it. Can anyone help or suggest anything about this issue?
I am expecting to run a bot from the Control Room of the Main Server into the Automation Server into the selected clients.
Related
QB desktop 2021 Enterprise version,
Multi-user mode not enabled,
qwc: Quickbooks Web connector
I am using Consolibyte's PHP sdk to connect QB desktop with our CMS. I am pulling some accounting reports from the QB desktop. My concern is that we have some 10 different company files (10 different clients). I need to pull the report for each client so I have prepared 10 QWC connections i.e one for each company file. My concern is that I cannot set Auto-Run for each web-connector setting (despite of having a gap of 1 hour between each entry). While installing qwc file, I have set automatically open the company file if not open("Always allow access even if Quickbooks is not running") but I keep on getting below error message when ever Auto-run tries to execute the configured app. I get the same error even if I do not open the QB company file in the QB and tries to run the same manually
Application requested to Abort
If I open up the company file in QB and then select the qwc application and select "update selected" then it works fine.
This is creating concern as I am not able to run the qwc apps automatically and have to run it manually. I will be having 50 company files and running it manually is time consuming. Can anyone please guide me as why it needs the company file to open prior running the web-connector (then what is the use of selecting ("Always allow access even if Quickbooks is not running")) and in that case automatic execution of qwc app not possible as somebody has to open the company file first. Kindly guide
Adand,
I had faced similar problem with consilbyte SDK for QBD web connector integration.
Sometime the problem is that QBD services are running in background and connected to one of the company, which we don't know where.
so in order to reset all things and try once again, you should kill following services which are running in your windows PC. and then start all company sync in web connector.
This should solve your problem. if not then share the web connector log file. so i can investigate and provide solution.
additionally you should try these solutions specific to Web Connector https://quickbooks.intuit.com/learn-support/en-us/help-article/open-programs/fix-common-web-connector-errors-quickbooks-desktop/L9slolvg0_US_en_US
I have found the solution for problem. Issue was that when we have multiple company files and if we want QWC to open up the right company file automatically then we have to set the company file path for each QWC user in the QB table (Consolibyte PHP SDK) "quickbooks_user"
UPDATE quickbooks_user SET qb_company_file = 'C:\path\to\your\file.QBW' WHERE qb_username = 'your-web-connector-username'
I have found this answer through below stackoverflow threads
Error in web connector when quickbooks not running
How to set .QBW file path for response in Authenticate for Quickbooks Web Connector?
and from Wiki pages by Keith/Consolibyte:
http://wiki.consolibyte.com/wiki/doku.php/quickbooks_integration_php_consolibyte#how_can_i_tell_the_web_connector_to_connect_to_quickbooks_even_if_quickbooks_is_not_open
I have tried this and it works. QB company file is opened up in background by QWC, data pulled and then company file is closed by QWC. I am hopeful that this inbuilt solution will allow me to automate 50+ QWC executions.
As Solace does not support deleting and disconnecting client via SEMP over a message bus, as mentioned here, may I know how do I do that programmatically? I need to manage clients, especially client connection from my application. Can I run trigger CLI scripts from my program to achieve that?
Thank you.
Disconnecting a client is an administrative action that can only be executed by management users over the management interface. Client applications are not allowed to execute this action.
To disconnect a client, you can send a SEMP command through the management interface using a management user. (Not via SEMP over Message Bus.)
I have created a sample .NET web app that connects to QuickBooks Online and using pages/forms in the app I can create/update customer records in QB. I would like to know how customer records in my database can be migrated to QB Online so that user does not have to explicitly logon to QB online. I read about WebConnector but it works with desktop version of QB. So I need to have ability to be able to create/update records in QB Online (using a background process) whenever customer records are added or updated in my SQL Server database without connecting to QB Online.
I am thinking of writing a WCF windows service that will call QBOnline API to do this work periodically but not sure how I will connect that service to QB Online. Please suggest if QB supports this (and how) or I have to force users to logon to QB to create/update customers.
I would like to know how customer records in my database can be migrated to QB Online so that user does not have to explicitly logon to QB online.
The very first time you establish a connection to QuickBooks Online, the user must login.
That only needs to be done ONCE. After that very first time, you should be storing your OAuth tokens, and you can send data over anytime you want without any user interaction what-so-ever.
If that's not the behavior you're seeing, it's probably because you're not storing the OAuth tokens like you should be.
I read about WebConnector but it works with desktop version of QB.
Do not use the Web Connector. If you've already implemented a sample .NET web app that connects to QuickBooks Online, then you're on the right path.
I am thinking of writing a WCF windows service that will call QBOnline API
Why would you do this? This is making things so much harder than they have to be... you already implemented a sample .NET web app, keep doing what you're doing.
Please suggest if QB supports this (and how)
It does.
You already implemented a sample app, which means you've already done what you're asking to do. Just make sure you're storing the OAuth tokens so you don't have to keep reconnecting all the time. The connection process by the user should happen ONLY ONCE. If it's happening more than once, you're not storing the tokens like you should be.
My application Connecting to QuickBooks 2013 with QBFC 12.
QuickBooks is running on a Server
Multiple users login to the same server and run QuickBooks from the server at the same time.
Application is also running on the Server.
Application connects to QuickBooks if only ONE user is logged in to the Server and has QB running.
If any other user logs in to the server and opens QuickBooks then the application does not connect.
Message Type: ERROR
Message: The application trying to connect to QuickBooks is not supported while multiple instances of QuickBooks are running.
at Interop.QBFC11.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
at QBFSSyncManager.OpenQBSession()
Message: The application trying to connect to QuickBooks is not supported while multiple instances of QuickBooks are running.
at Interop.QBFC11.QBSessionManagerClass.BeginSession(String qbFile, ENOpenMode openMode)
at Turbo.THUB.QBProcess.QBFSSyncManager.OpenQBSession()
Solution that I found (if it applies to your problem):
If you are running your application from within Visual Studio (any version), make sure VS is NOT running as an Administrator.
This took me hours of hair pulling, name calling, forum screaming and a broken mouse to figure out.
My application works with multiple users, each with separate computers and separate instances of QB, all working in the same QB file via network file share.
I recommend move your application to a separate computer with its own QB instance and open the QB file remotely (not by remote desktop).
A common approach is to move Quickbooks to its own machine , and then write your application such that it receives requests from the other machines. The request can be processed and some sort of message returned. The message can be either a result set or a message letting the caller know if it worked, or if there was a problem.
Without knowing more about what you are trying to do, its hard to give specific advice.
I have Quickbooks Pro 2013 with the Web Connector installed.
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.
This happens only while QB PRO 2013 is OPEN. 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.
The thing is when I close the application the Web Connector starts complaining with a QBWC1013 error, saying:
Could not start QuickBooks. - second row in this link: http://www.zoho.com/crm/help/quickbooks/troubleshooting.html#sthash.hk3Dc8dl.dpuf
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).
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.
The Web Connector application has been granted full access and Admin login to the company file.
Any thoughts :)
First, know that the very first time you connect things you have to make sure QuickBooks is open. If you haven't had QuickBooks open at all yet, make sure it's open the very first time to get things connected.
After that, QuickBooks does not have to be open, provided you have configured things correctly.
To answer your questions:
Is this behavior different on non POS products ?
Yes. Slightly.
Do I need to keep QB open all the time ?
No.
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).
Hit F2 in QuickBooks, and make sure that the path that's shown in the dialog window that pops up is EXACTLY the path that your web service is returning to the Web Connector. It must be EXACTLY the same.
If you're still having trouble, double-check that the app is allowed to connect in the QuickBooks settings, and that a valid user is chosen in the settings, restart the computer, and try again.
If you're still having trouble, post your Web Connector logs (in VERBOSE mode: QuickBooks Web Connector - how to set VERBOSE mode) so that we can help you troubleshoot.