I have a scheduled task run a script which first launches QBw32.exe if it is not already running and then launches OSRUN to launch a sync. It pipes the output to a text file and analyzes the text file after completion to log the error and retry the sync in certain cases.
What we are seeing is that if another user has the bank feeds locked in Quickbooks enterprise a dialog box will pop up as soon as OSRUN starts to sync saying that another user has bank feeds locked. If this box is not clicked away the sync will fail.
I do not have a solution for this and it is pretty frustrating that QB is so noisy. Does anyone have an idea how to solve this from causing a sync to fail?
I thought of finding a way to have a script click “OK” but it seems like a messy solution and a bit time consuming. Is there a way to prevent the dialog box in the first place?
Which version of QuickBooks and OpenSync are you running?
Enterprise accountant 17. Open Sync 2.0.76.
If the script does not launch QBW32.exe the sync will also fail. In other words OSRUN seems unable to launch QBW32.exe itself. There was another post on this issue having to do with Remote Desktop sessions and the solution was to launch QBW32 manually. This is not an RDP server but it is a Windows server which supports 2 RDP sessions.
Can you post your log files? was it working fine and then this error out of the blue?
It was and is working fine so long as no user is logged into the bank-feeds section of Quickbooks.
It seems some update to QB included this locking feature for BankFeeds. Now whenever a user has bank-feeds open it automatically locks it and any other user who logs into the same QB file receives a pop-up window worning them that the bank feeds are locked by another user. It is this pop up window which breaks the sync. I have to manually click OK in order process the sync which breaks OSRUN automation.
you will have to make sure that windows doesn’t show anymore.
That is my goal. We are asking people to stay out of bank feeds but it is a bit backwards. I was hoping for a way to sync without having to open the GUI at all. Is this possible? Perhaps a different OS? Run the sync in Windows 10 instead of Server 2016? Would that solve the problem of the pop-ups or would that be a waste of time?
If OpenSync is not running on a terminal server, the QuickBooks can be closed. If it is a terminal server, it has to be open in order to run.
I just now realized what this means. While we are not running the software on a terminal server we are using RDP to connect to the server. We have switched over to using another remote support tool and so far the problem seems to be resolved.
The takeaway for me is don’t use Remote Desktop. Login at the console or use another remote solution.
Great to hear that. Thanks, Tim for your input.
Unfortunately we are now seeing the issue once more. It seemed to resolve for a few weeks. Even without Remote Desktop. It seems that there is another reason why OpenSync may launch the QB GUI aside from Remote Desktop. It seems that if the bank feeds are open by any user in QuickBooks OpenSync will launch the GUI.
If there are any fixes/workarounds for this it would be much appreciated. Attached is the error.
If someone is using the form, QuickBooks will block it and OpenSync cannot access it until it is released.
What I am seeing is that OpenSync can access all of the data that it needs. It is only the error message pop-up which prevents the sync from proceeding.
If I click “OK” on the dialog box within a few minutes the sync will proceed and complete. If I do not it will time out. This prevents the sync from completing on schedule without manual intervention.
The goal is to have the sync proceed without opening QB in the first place thus eliminating the dialog box and the failed sync. The question is why is QB launched in this scenario and how do I prevent it.
Is there any reason to believe that this behavior has improved in newer versions of QB/OpenSync?
We are using Quickbooks 17.0, OSync 2.0.76
If it is a window popping on QuickBooks, you need to make sure that it doesn’t show anymore. I recommend you to upgrade your OpenSync.
So upgrading did nothing for this problem. It did completely crash the software triggering a complete rebuild of the server as OpenSync would not even load directly after upgrading. Huge nightmare. Could not go back as we had paid a lot to update Quickbooks and they wanted to keep the newer version.
Anyways, OpenSync is doing something with BankFeeds causing this error message. If I login to Quickbooks normally the message does not pop up. It only appears if I try to open the BankFeeds manually. OpenSync is interacting with the BankFeeds somehow through the API or otherwise causing the problem.
If no users are in the bank feeds then QuickBooks GUI does not even open, the sync just completes as expected.
The worst part is that OpenSync does not need access to the BankFeeds to complete the sync. If I manually click “OK” it will continue with the sync and complete. It just cannot get past the dialog box.
The issue of “terminal server” was a complete red herring. It only affects the QB GUI opening. If the user session is open via Remote Desktop then Open Sync can’t launch QB (so you have to open QB manually. If you connect at the terminal or use remote access software, OpenSync does not need to launch QB in order to sync. It has no effect on the Bank Feeds dialog box either way.
I have yet to receive a relevant suggestion but figured this information might help someone else.
The forum ‘OpenSync’ is closed to new topics and replies.