I have a simple task-pane Outlook add-in. When I install it manually (uploading the manifest file) to one account, it works well : on Outlook Desktop, Outlook online, OWA, and the iOS Outlook app.
When I install it to the whole organization through the Microsoft Exchange Admin Center (Organization --> Add-ins --> Add), two stranges behaviors occur :
1) It is immediately deployed to all accounts ; except for the administrator himself (~3 hours of delay before it is deployed !). Why ?
2) Once deployed, the Outlook iOS app support disappears, whereas the uploaded manifest is the exact same file. Desktop, Web, and OWA apps works well. The add-in indeed appears in the "Parameters > Manage add-ins > My add-ins" of each user.
I can't find or explain this problem. Did anyone find a solution or an explanation ?
The delay can actually affect all users. We cache installed add-ins server side for performance improvements.
In terms of the add-in on ios, the scenario of admin installing add-in to mobile is currently not supported. This is in our backlog, and we'll be getting to this soon.
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.
I recently did fresh installs of Windows 10 and installed the latest Office 2019 (Office 365). All of my google accounts (free gmail accounts and corporate account) have IMAP disabled and app passwords disabled. I only allow oauth connections to my google accounts. Outlooks refuses to try oauth and only tries IMAP. Prior to Win 10 installs I had Win 8.1 with Office 2016 and it connected via oauth to google emails without issue. I tried on 2 separate Win 10 instances, and then created a fresh Win 10 VM with a fresh Office 2019 install (changed no settings) and behavior across all 3 instances is the same. If I put in a google address it immediately goes to the IMAP page and asks for a password instead of bringing up an authentication to my google account using 2 factor (2FA). Additionally I check the box "Advanced options -> Let me set up my account manually" and click on the G (Google) icon and it still doesn't try the oauth authentication - it just goes to the IMAP setup page.
Luckily I was able to get in touch with an MS Office support team - if anyone else experiences this issue it has to do with the Office updates channel. If you are a developer it defaults to a channel that doesn't support oauth. To fix add the registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate]
"updatebranch"="Monthly"
After adding the registry key close all office apps, restart them, go to File -> Office Account -> Update Options - > Update Now and it'll install the missing files.
The issue is that users trying to connect to a SharePoint 2016 site using https will be continually prompting for credentials when browsing using an Apple iOS devices (iPhone, iPad, etc).
We have spoken to Microsoft about this issue and appears to be a known problem and came back to us with the following response.
This issue occurs as the SharePoint Authentication is not compatible
with the IOS
As of now this issue has been reported but the change is required from
the Apple end, such that the IOS accepts the SharePoint
Authentication.
They recommended a few work arounds, but it appears that there are a lot of cases with similar problems, so I was just wondering what work around others are using, until a fix is put in place.
Using Http url for SharePoint
Using a Web Application Proxy for SharePoint https://blogs.msdn.microsoft.com/sambetts/2015/07/01/sharepoint-server-and-web-application-proxy-continued/
The current work around for me is to use a web proxy but this pain as it needs to be updated on each device for each connection.
I had exactly the same issue with HTTPS and SharePoint 2016.
The issue was solved by disabling HTTP/2 for IIS 10. I had to create two registry keys: under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
EnableHttp2Tls REG_DWORD 0
EnableHttp2Cleartext REG_DWORD 0
Update
This should only take effect after you restart the server.
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.
On my development machine (which has the Quickbooks SDK installed) I can connect and interact with QB just fine; the standard workflow of granting access to the external app from w/i QB works. However, on my production machine I get various and sundry errors:
Can't start QB.
Can't start QB because it's already running.
Can't open more than one company file.
The dev docs lead you to believe that the app must be signed while elsewhere I've found examples where you could run an un-signed example app. So what is it? If signing isn't strictly required then any clues as to why I can't get this to work?
Production Machine
QuickBooks Pro 2011 Release R9P (US)
Our installed, OOB, Silverlight app
Dev Machine
Quickbooks Premier Contractor Edition 2010 Release R13P (US)
Silverlight 4 using COM/C# to connect to QB
Quickbooks SDK 11.0
As I've said, the dev machine works as it should. On the production machine we've tried every combo of not having QB open, having it open but no client file open, having it open and a client file open and we'll get one error or another right at the point we're trying to open a connection. Also, our app never shows up in the integrated applications settings page (but it does show up on the dev machine's QB). We've tried both admin and non admin.
No, you DO NOT need to sign your apps.
You didn't provide anywhere near enough information for us to really give you a solution.
Did you check your SDK logs?
What version/year/edition/country of QuickBooks?
Are you building for the Web Connector, or using C#, or VB .NET, or...?
If you're using the Web Connector, what do your Web Connector logs look like?
Are you logged in as the QuickBooks admin user?
Is QuickBooks already running?
Is there another QuickBooks company file already open?
Did you revoke permission from the integrated application?
If you expect answers, you have to post some details.
It's a Silverlight app with full trust. It looks as though it was something with SL itself. Once we upgraded to SL5 it worked fine.