I don’t know when this began, but I just happened to see Task Manager on a server running QuickBooks, and it is very clearly running “SQL Anywhere Network Server (32 bit)”, which is some version of Sybase SQL Anywhere:
The last time I checked this, which was a while ago, it looked like a much more hidden version of Pervasive SQL. This may be a major change at the heart of QuickBooks, hopefully for the better. One does wonder if we could use those command-line options to advantage…
As of version 2019 (and possibly before), QuickBooks has a new feature: native support of Office 365 webmail and some other major email providers. When users send email via QuickBooks, go to Preferences, Send Forms, and instead of choosing Outlook, choose Webmail, and then set up integration with the user’s Exchange Online account. Works much smoother, faster, more reliably.
The QuickBooks File Doctor now takes care of Windows networking changes.
The QuickBooks File Doctor now takes care of Windows Firewall.
If you are getting persistent H303/H505 errors or the like, check the .ND file corresponding to the QuickBooks database you are trying to load. If it has an IPv6 address within, that’s probably the problem, we need to set IPv4 as dominant on the server:
Reboot is required before the setting takes effect.
Deep in this page:
we have a strange piece of input stated as being specifically and only to Server 2012 R2, to prevent H202 errors and the like. We are to do the following:
- Stop the Base Filtering Engine in services.msc
- Perform a Scan in the QuickBooks Database Server Manager, after making sure that appropriate folder(s) are selected
- Start the Base Filtering Engine in services.msc
This one reinstalls, repairs, and refreshes a wide variety of bits which QuickBooks uses. Helps with both installs and malfunctions.
This is a tool from QuickBooks, new to me, which can fix a lot of different Windows library and other issues, to be used sometimes when QuickBooks fails to install.
Reportedly in February 2016, Microsoft began to automatically upgrade all Office 365 customers to version 2016. One has to search for the words “February” and “automatic” in the page below to see it:
Among many others, this can cause major problems for users of QuickBooks of all versions before 2016; all integration with Excel fails, and we can expect other problems (e.g., Outlook integration) as well. There is no easy revert procedure, we just have this:
There is a method to prevent the upgrade via Group Policy: