We are an accounting and tax company and manage books for a number of clients on various years of QuickBooks. We have recently built a new application server on Windows Server 2019 with 2012 - 2019 QuickBooks Accountant installed. Data is on another Windows 2019 Server.
We have had 2 issues so far with different years of QuickBooks when attempting to print reports from a QBA file. In both cases (2019 and 2016) QB appear to freeze when displaying the dialog box indicating the job is printing to our HP 4515 Network printer (configured via fixed IP).
The first time I was able to open Task Manager and kill a job under the QB process. It was not there for the second, but I did not check this until after I tried to just delete the job from the print queue. At the time I tried to delete the job it indicated spooling which seems consistent with the hanging.
It also appears that the error occurs on the first use of the application, but subsequent attempts to run reports work OK, at least we have not been able to break it so far.
I have already checked the basics, but not run the "Doctor". I tend to think this may be more hand off to the server related.
I realize 2 data points is not much to go on as yet and this is may be a pretty rare configuration.
The problem may be caused by the issues on the computer itself or by how QuickBooks interacts with your system. Be sure to always update your QuickBooks to the latest release so it becomes available to ensure you have all the updated components. For your guide, read this article: Update QuickBooks Desktop to the latest release.
You can also follow the steps provided in these articles to resolve issues that cause QuickBooks to stop working:
I generally agree it's a handoff issue between QB and server 2019 and was hoping someone had seen similar. I also want to rule out any odd behavior with QBA files specifically.
Maybe I should indicated that once I kill print processing I can get control back in QB so I do not really see the first links applying.
I have read the other article and have reviewed the basics. As this is an RDP server I need to schedule downtime to run any utilities, so do not wish to run file doctor or make any changes that may impact users.