lohayy.blogg.se

1. #INSTALL MICROSOFT XPS DOCUMENT WRITER WINDOWS 10 PDF#
2. #INSTALL MICROSOFT XPS DOCUMENT WRITER WINDOWS 10 WINDOWS#

I don't think I would have ever found answer that fixed this particular customer's problem without there being another bug in the company file rename process. Extremely frustrating for a customer who can't email or print POs for their vendors. Both Microsoft and Intuit acknowledged it as an issue but provided no dates for a fix or workaround.

#INSTALL MICROSOFT XPS DOCUMENT WRITER WINDOWS 10 WINDOWS#

Since the users didn't receive their Windows updates on the same day, the ones who didn't were still able to print and email, so it had to be something in the updates responsible for the issue. However, that was before the recent April/May Windows roll-ups. I have encountered these issues before, but only with the first print or email attempt.then it would work. You would have thought the print/email-specific tool would have fixed the problem.

#INSTALL MICROSOFT XPS DOCUMENT WRITER WINDOWS 10 PDF#

The XPS and PDF writers would constantly lock up when Quickbooks tried to print or email, forcing the user to end the task manually, then start Quickbooks again.

After those Windows security updates, things really went downhill with Quickbooks printing. I didn't have it go missing after the updates, but I did delete it manually and try to recreate it during one of my troubleshooting sessions. If I removed the logos from the templates, I could print and email again. Now I knew what the issue must be! Microsoft security updates were likely attempting to block graphic or image files being included as custom logos in the reports.

I manually copied the image files (.jpg) to the new folder and tried to print and/or email the documents. I checked out the server and noticed that while the rename of the company file created a new images folder for Quickbooks, it did not move the images over to the new folder from the old folder (which was still in existence). HOWEVER, they immediately noticed they were missing something.none of their custom logos printed - just the forms themselves.

I tried that on my test server and it actually worked! I did the same in production and it worked there as well. Somehow, that fixed the problem and they no longer got hung up printing or emailing. In another forum, a user had said that their fix for the problem was renaming the company file so it didn't have spaces.