QuickBooks 2010 and 2009 PDF Printer Problems with 64 Bit Systems
If you are using a 64 bit operating system and QuickBooks 2009 or 2010, you may run into some problems This article talks about how to resolve the problem.
Please note that this article relates to specific revisions/versions of the US editions of QuickBooks:
- QuickBooks 2010 R4 and later
- QuickBooks 2009 R10 and later
If you are using a 2007 or 2008 version of QuickBooks, or a 2009 version with revisions older than R10, then please refer to my previous article on QuickBooks problems on 64 bit Vista.
If you don’t know how to tell what “revision” you are running, please see this FAQ article .
This article was updated on 1/5/2010, and again on 1/12/2010
UPDATE 02/12/2010: QB 2009 R11 has been released to fix this problem, see the 2009 R11 article
QuickBooks PDF Driver
QuickBooks includes a PDF driver that it installs. This is used in a number of places in the program. If you are sending forms via email, the PDF driver creates the image of the form that is attached to the email. When you reconcile accounts (bank accounts, etc.), a copy of the reconciliation report is archived in PDF format. There is a save as PDF option in the File menu. In 32 bit systems it generally works quite well. Unfortunately, in 64 bit systems, Intuit runs into problems on occasion.
In the 2009 release of QuickBooks the driver didn’t work in 64 bit systems – this wasn’t fixed until the R7 release . In the 2010 release, it worked fine (at least it did in my system).
Recently, Intuit updated the PDF driver to a new version which unfortunately seems to be incompatible with 64 bit systems. This was updated in the 2009 R10 and 2009 R4 releases. The problems vary from installation to installation – and the problem can be very tricky. It doesn’t always show up. I had a hard time pinning this one down myself – the program would work fine, then I’d come back and find that it wasn’t working. These kinds of transient problems are very hard to catch in testing of releases, and are hard to fix.
The Problem
In my Windows 7 x64 system, the problem I most often came across was Could not print to printer.
Another common error is QuickBooks PDF Converter Activation Error –20. There are a variety of other errors that might pop up, all relate to performing some operation that invokes the PDF driver.
The Solution
Fortunately, Intuit discovered the problem and posted a temporary fix in Support Article 898690 .
The solution involves obtaining a DLL file (a program component file) from Intuit and installing it in the appropriate place. I can’t provide you with the DLL – you have to go to that support article and click on the download link. You will be asked to provide your email address and name, and they will email the link to the DLL to you very quickly.
I would like to point out (their initial article didn’t make this really clear) that you should only make this change if you have one of the revisions that are affected that I list above. If you make the change with an older revision – such as I accidentally did with a 2009 R8 test installation, you will get a different series of errors. So check your revision first before doing this.
The email message that contains the link to the DLL file will have specific instructions for Windows 7, Windows Vista and Windows XP. I’ll illustrate the process here (and fill in a few blanks) using Windows 7 – the general process is the same in all three operating systems, the difference is finding the printer device in the Control Panel.
1. Log in to your Windows system as the administrative user.
2. Exit QuickBooks if you have it running.
3. Click the Windows (start) button and select the Control Panel.
4. Under Hardware and Sound click the lick for View devices and printers.
3. Locate the QuickBooks PDF Converter 3.0 icon.
Note that there may be several PDF icons if you have installed older products. In my Vista system, that I’ve used for several years, I saw three separate icons. Make sure you delete the 3.0 version.
In some cases in Windows 7 the 3.0 icon might be hidden. In one system the program only listed a 2.0 converter, which confused me at first. If I right clicked on the icon I noted that there were several options under the printing preferences menu option – it was showing that this icon represented both the 2.0 and the 3.0 driver, even though the icon only said it was for 2.0.
In this case, you can select the 2.0 icon and perform the next step, it works on the 3.0 driver.
5. Right click on the icon (the 3.0 icon, or the 2.0 icon if that is all you see) and select Remove Device.
6. Locate the qbwpr32.dll program file. The folder name varies with the version of QuickBooks you use. The path will be C:\Program Files (x86)\Intuit\product, where product will be something like QuickBooks 2009, QuickBooks 2009, QuickBooks Enterprise Solutions 9.0 or QuickBooks Enterprise Solutions 10.0.
7. Right click on the file and rename it from qbwpr32.dll to qbwpr32.old.
8. Download the dll file from the link Intuit provides and place it in this folder.
9. Restart QuickBooks and see if the problem is solved. Note that you may see the error one more time, but if you then exit QuickBooks and try the operation a second time the error should not occur. In my Enterprise 10 installation the problem didn’t pop up that first try, but in my Enterprise 9 installation it did – and it cleared up the second time.
If you have both the 2009 and 2010 versions installed please note that you need to make the DLL file change in both directories for this to work properly.
Update on 1/5/2010: Some users have run into a problem after installing the new DLL file, getting a “Microsoft Visual C++ Runtime Library” error. Intuit is investigating this. I don’t have this issue on MY system, but a few others have reported it. If you run into this you can delete the DLL file and rename the “OLD” file to the original name. I’ll post an update when we know what is going on
If That Doesn’t Work
This section was added on 1/12/2010.
Some people (as you can see from the comments below) have run into problems with the DLL solution. Some have found that they have slightly different problems than what are outlined here. Intuit is working on a further solution, and we’ll post information here when we find it.
If the DLL creates a worse problem than the one you started with, one simple fix is to delete that new DLL and rename the “old” one back to the original name. That puts you back to the place that you started at.
You can get a PDF printer driver (Adobe Acrobat is what I use, some people use “CutePDF” which I haven’t tried) and use that to print PDF documents as a normal printer, BUT that isn’t a full solution as you still can’t reconcile accounts, and you don’t get the email message created with the customer email address.
Some people have found that after deleting the PDF driver per the instructions above, a new PDF driver is not created automatically as it should. I’m not sure why this happens. But, here is a solution to try based on feedback from several users, as well as input from Sudhir Navalapakam of Intuit.
You can install the PDF converter from files in your QuickBooks folder. Go to C:\Program Files(x86)\Intuit\QuickBooks 2010 (the last folder will be QuickBooks Enterprise Solutions 10.0 if you are using Enterprise).
Locate Install.exe, and run that file. This is the Amyuni PDF driver installer (Amyuni is the company that makes this program). Note that the installer is not “signed” so you may get a warning, this is OK).
This should create an Amyuni Document Converter icon in your printer section of the control panel. You can rename it to “QuickBooks PDF Converter 3.0″. Right click on it and select printer properties, and check to ake sure that it uses the “NUL:” port.
If for some reason the installer fails, which might happen for some people, you can use the add a printer wizard to add a printer from the control panel.
Select Add a local printer.
Select an existing port if NUL: exists, or you will have to create it.
Select the Amyuni driver.
Click Have Disk, and brows to the same folder as I specified above, to find the amyuni.inf file.
Make sure that you do NOT set this to be the “default” printer.
My thanks to Intuit employees Laura Messerschmitt and Sudhir Navalapakam for their assistance with this information.
Greg Charland | Jan 4, 2010 | Reply
Charlie, thanks for posting this. I’ve got your original QB PDF printer post saved as a favorite, it’s helped me and my clients many times!
Nice to see Intuit taking action on this. Even Microsoft’s own OneNote printer driver fiasco has taken YEARS to straighten out.
Barry | Jan 4, 2010 | Reply
Charlie,
Just sent you an email. I am now getting a Runtime error with this new file. I will keep experimenting.
Timothy McNinch | Jan 4, 2010 | Reply
There is also a problem with the PDF driver for printing items like Payment receipts. This occurs on a WIN7×32 in 2010 Mfg & Wholesale
Charlie | Jan 4, 2010 | Reply
Barry, what REVISION level are you at?
Timothy, what REVISION level are you at, and are you saying this happens WITH the dll fix or WITHOUT the dll fix. And are you printing to the PDF driver like it is a regular printer?
Garrett Griffin | Jan 5, 2010 | Reply
Charlie, thanks a ton for this update.
We’ve been dealing with this exact issue for about a month. I’ve tried your other article in its entirety probably 3 times with only temporary success.
I look forward to trying this solution later today. Fingers crossed that it takes care of everything!
Thanks a lot, your walkthroughs are immensely helpful.
Becca | Jan 5, 2010 | Reply
Charlie – I did this as well, but am now getting a runtime error too. QB won’t even load. I’m sure it was my fault, as I was unable to download the file w/ the old one renamed as .old, so I have to revert to the .dll file, and run the download. Apparently QB won’t work without the original? I’m in a world of hurt – any advice?
QB Pro 09, v10. Windows 7 64 bit….
Charlie | Jan 5, 2010 | Reply
Becca, I’m not sure what you are saying about how you couldn’t download the file – that is a bit confusing.
I’ve not seen the runtime error myself, so I don’t have an answer at this time. Everything is running fine on my side of things. Were you an administrative user when you renamed and downloaded the DLL?
Becca | Jan 5, 2010 | Reply
Yes, I was administrator, but I repeatly got a message that I was not able to modify the program, and needed to contact the administrator. ?? But when the file was not .old, but the original .dll file, I was able to download. I’m mystified, and thinking that the only way back (as I foolishly didn’t save a copy of original .dll file) is to reload QB Pro 09, and after doing all the updates, restore my company.
Charlie | Jan 5, 2010 | Reply
Becca, this is a bit confusing. You needed to rename the existing DLL to “old” so you would have the old copy. When you download the new dll you should download it to your download or my documents folder, then copy it to the target folder after renaming the old one…
Huey | Jan 5, 2010 | Reply
Where do you find the link for the .dll from Intuit?
Charlie | Jan 5, 2010 | Reply
Huey, in the article, under the heading “The Solution”, there is a link to KB article 898690 in the Intuit web site. Follow that link, on that page is a link to get the DLL. Note that they don’t let you download it directly – you have to give them your email address, and then they’ll send you the link via email
Huey | Jan 6, 2010 | Reply
well i am one of those that is getting the runtime error when trying to start QB now! This is really not good news for me!
Charlie | Jan 6, 2010 | Reply
Huey, if you restore the “old” dll (delete the new one, rename the old one to the original name) the runtime error should go away. One of the engineers at Intuit is investigating the cause of this problem, I’ll post info here when I hear back from them.
Garrett Griffin | Jan 6, 2010 | Reply
Worked brilliantly for me, I’m sorry for everyone getting runtime errors
.
I wish everyone the best of luck and applaud Intuit for fixing this for us!
Melissa Keuning | Jan 7, 2010 | Reply
I am having same trouble as Becca: when I try to download new dll it tells me I need “administrators permission” and yes I am logged in as administrator. Then I downloaded in my documents and tried to copy it to target folder and got the same “administrator” flag. Also, getting runtime error now too.
Becca | Jan 7, 2010 | Reply
thanks Charlie – I’ve now tried the fix a couple of times and the runtime error is still there. I will do the revert to the old file trick and hang tight to see if Intuit can come up with something for us!
Sandy | Jan 7, 2010 | Reply
I too am very frustrated with this situation. I’m on Win7, QB Premier 2009, R10. I was getting the PRINT DRIVER HOST FOR 32 BIT APPLICATION HAS QUIT error. Went thru all the hoops to install the new DLL file. THen I also got the QB runtime error preventing QB from loading. I was at least able to rename the old dll file and get back to the PRINT DRIVER HOST problem.
I’m dead in the water until I can email POs, Invoices and better yet, Financial Reports to all the people screaming at me.
Any suggestions at this point? Any way to back out the R10 release and get back to a version that saved and emailed? Any idea how long it will take Intuit to fix this problem?
Bill | Jan 7, 2010 | Reply
I followed these steps and received the C++ runtime error. After putting the old DLL back in place I was able to print without issue. Running Win 7 64-bit and QB 2009 R10.
Charlie | Jan 7, 2010 | Reply
Sandy, I’ve not seen THAT specific error message, so I can’t say if it is the same issue (but it sure sounds like it might, if you have a 64 bit system).
For everyone, an Intuit engineer has been in contact with several of the people who have been corresponding about the runtime error, and is working to see what the cause of the issue is. I’ll post info here as soon as an answer is available, if it can be worked out.
Melissa Keuning | Jan 7, 2010 | Reply
Sandy (& Charlie), I am back to the same “print driver host for 32 bit applications has stopped” error now also. This is mighty frustrating.
Melissa Keuning | Jan 7, 2010 | Reply
Sorry, The error actually reads “Print driver host for 32bit applications has stopped working” then I click “ok” and the window pops up “could not print to printer, check your printer selection. Printing may have been cancelled from another program”.
Need help soon…. thanks.
Charlie | Jan 7, 2010 | Reply
Sandy, I didn’t answer your other questions.
If you are on R10, going back to an earlier revision of the program can be a bit complicated, even if you have a backup of your company file that is pre-R10. You have to uninstall QuickBooks, reinstall the original version, and then find a way to update to the appropriate revision that matches your backup. AND I am not sure if that will resolve the PDF driver issue (it probably would, but I haven’t tried it).
A better solution would be to see if you have another workstation in the office that has QuickBooks, that is 32 bit, and export things from there. OR, get a PDF printer driver (I use Adobe Acrobat myself, some people like the free CutePDF driver that I’ve never tested) and then print invoices and reports to a PDF file using that. Note that invoices would be PDF documents and you would have to attach them to an email yourself.
Hard to say how long this will take for them to get fixed. It depends on what the error is. Even if they pin it down soon, getting the change out might take awhile…
Melissa Keuning | Jan 7, 2010 | Reply
If I just upgraded from my QB Pro 2009 (just updated this week) to QB Pro 2010 would this solve my 32/64 bit issues? I am on windows 7 home premium with 64 bit os.
I am tired of tryin multiple “fixes” that are not working.
Charlie | Jan 7, 2010 | Reply
Well, Melissa, there is a lot that I like about the 2010 release (although the things I like might not apply to you…), and QB 2010 is the only version “officially” supported on Windows 7 – but if you look at the top of the article you will see that QB 2010 R5 introduced the same error with 64 bit PDF files.
It is hard for me to say if the work would be worth it for you. I’m hoping that we’ll have a swift resolution to this, but I don’t have any control over it so I can’t say.
Don | Jan 8, 2010 | Reply
Add me to the list of folks having the runtime library error on a W7 Home Premium 64-bit laptop. I have QB 2009 Accountant’s Premium edition R10.
Previously I had the “print driver host for 32bit applications has stopped working” message, followed by the “could not print to printer” message shown at the top of the article. These issues were intermittent…this morning I ran maybe 6 bank recs without incident and the QB bombed on the 7th.
I have tried all the other recommended workarounds on the web…downloading 64-bit Amyuni drivers, renaming ports, changing the xmllite.dll file back to an earlier version, unchecking boxes in my Adobe 9 Professional setup. Thought this new dll might finally put this problem to rest. Guess not.
Let me know if I can help.
Barry | Jan 8, 2010 | Reply
For those of you that need to get back up and running the easiest way is probably to do a System Restore to a restore point prior to the R10 release and then use your QB backup file that R10 required you to create.
I am one of the people who spoke with the QB engineer. As of tonight I have not heard anything back from him. Hopefully early next week…
Greg Scott | Jan 10, 2010 | Reply
I am having a similar but not identical problem. I am running Quickbooks 2010 with 64 bit Windows 7 Ultimate. Which revision of QB2010? Well, it would be nice if help…about would tell me but it doesn’t.
Yesterday I was saving invoices to PDF files when suddenly, the “Print driver host for 32 bit applications has stopped working” started up. Invoice number 1056 worked just fine, invoice 1057 failed out of the blue. The crash is the same as documented in earlier posts, with the offending program splwow64.exe.
So what happened leading up to the problem? I was printing invoices, like I’ve done for several years with several different versions of Quickbooks. I printed a couple of invoices on a physical printer, then saved invoice number 1056 as a PDF file. I went to the next invoice, number 1057, and the problem came out of nowhere.
I have since discovered I can’t print from Quickbooks to **any** printer. The problenm is not limited to creating PDF files. Clicking on file…printer setup generates a popup, “There was a problem connecting to your currently selected printer.” It seems Quickbooks broke the ability to interact with **any** printer.
I can print from other 32 bit apps.
I find it distressing that after all these years, a program can still corrupt itself like this.
- Greg Scott
Greg Scott | Jan 10, 2010 | Reply
Help…Update Quickbooks takes me to a dialogue box where I can look at what revision level. It looks like I am running update 5. So QB2010 update 5 and this seems to be the latest and greatest as of this morning.
I am kind of afraid to try the DLL fix mentioned in earlier posts.
- Greg Scott
Greg Scott | Jan 10, 2010 | Reply
I thought some more about trying that DLL fix and ended up downloading and installing it. After installing the replacement DLL, I was able to interact with printers, but still no joy with saving to PDF. I closed Quickbooks, removed the Quickbooks PDF converter, (Printers…remnove device and then lanch install -u). I reinstalled the PDF converter with the install program and now save to PDF seems to work again.
- Greg Scott
Charlie | Jan 10, 2010 | Reply
Greg, glad you tried the DLL fix, as it is a completely reversible fix if you didn’t like the results (just delete the new DLL and rename the old one back to the original name). Every Windows system is a little bit different, and what works for some doesn’t always work for others.
Please note that you can easily see what revision you are on by pressing the F2 key, as mentioned in this FAQ article: http://qbfaq.ccrsoftware.info/2009/12/16/how-can-i-tell-what-quickbooks-revision-im-using/
Steve | Jan 10, 2010 | Reply
I installed the fix, but now when I try to print any reports, I get a blank print reports dialogue box which only has the buttons to Print, Cancel, Help, Preview or Signature. So I can’t specify number of copies or even format the way the report prints (landscape, only certain pages, etc.) If I click the Preview button I see a copy of the report but no menu for Page Setup. Just Print, Previous Page, Next Page, Zoom In, Help and Close. I am using QB Premier Accountants Edition v. 10P on Windows Vista 64 bit. I would never have upgraded to v 10, but had to to use an Acccountants copy from a customer who upgraded. I can send screen shots if you want to see what things look like now.
Bonnie | Jan 11, 2010 | Reply
I am having the same problem as steve. I can print but the printer setup page in quickbooks and the print screen is blank. I have to individually print invoices and it is not letting me print reports. I get “could not printer to printer” and printing to Quickbooks PDF Converter FILE and asks me for an output file.
The fix above did not work for me. I got runtime errors. i ended up adding a printer in the control panel and picking the Amyuni Document Converter. I added that and that took away the pdf converter issues on a lot of my printing and I was able to print.
Charlie | Jan 11, 2010 | Reply
Steve: If you installed the DLL, you can remove it and rename the “old” one back to the original name.
Huey | Jan 11, 2010 | Reply
Still no updates for us? This is getting to be a big hassle, at least i can print invoices to the printer, but i still can’t email them or statements.
Barry K | Jan 11, 2010 | Reply
Same Problem here…installed the DLL, got the runtime error. Went back to the old DLL and at least can get into the proram. Still can’t email my invoices. Hope this gets fixed soon.
Charlie | Jan 11, 2010 | Reply
Huey, as I said earlier, the fix posted here works on my system. I’ve not seen any of the other problems myself, so there isn’t much that I can do to look further.
Intuit engineers are working on it, when they pass anything on to me then I’ll post it here. I don’t have any control over them…
Huey | Jan 11, 2010 | Reply
Thanks charlie!
Eric | Jan 11, 2010 | Reply
Same runtime problem. Hope they fix it soon.
Steve | Jan 11, 2010 | Reply
Bonnie, you’re a lifesaver. I deleted the “patch” DLL, renamed my old one, and once I installed the Amyuni Document Converter as a new local printer everything looks good. Bless you and bless Charlie’s site!
Bonnie | Jan 12, 2010 | Reply
Steve – do you still have a blank print dialogue box. I have not been able to fix that.
Also you have to rename the Amyuni Document Converter to Quickbooks PDF Converter 3.0. That solved the problem I referenced above with the output file error and file error.
Now if I could just get my print dialogue boxes to work properly.
Steve | Jan 12, 2010 | Reply
Bonnie- No, I simply installed the Amyuni Document Converter and everything was back to normal. Didn’t even have to rename it. What I haven’t tried yet is to download a PDF file, but I’ll give that a try and see if there are problems. Printing is A-OK now with the old DLL and the Amyuni.
Charlie | Jan 12, 2010 | Reply
I’ve added some screen shots to the article that talk about installing the Amyuni converter for those who need that.
raxlehead | Jan 12, 2010 | Reply
MUCH EASIER SOLUTION!!!
There is a much easier to solve the non printing issue.
Go to the properties of the Intuit Quikbooks printer and the properties of the Amunyi PDF printer and set them both to “spool documents” instead of ‘print directly to printer’.
When you set it to “spool” it will print perfectly.
This is also an issue with the Amunyi PDF printer in ACI appraisal software systems, if anyone supports those too.
-Raxlehead@yahoo.com
Kevin | Jan 13, 2010 | Reply
I have tried everything above in all its variations. I can only get pdf printing to work temporarily. I then have to run through the steps again. I am using Enterprise 9.0 relase 10. Pdf printing was fine for me until the new release. Has anyone else using this version had success for a full day? Thanks.
-Kevin
Charlie | Jan 13, 2010 | Reply
Raxlehead – thanks for pointing that out, it works in some cases, but unfortunately it often doesn’t. I’m working with a couple of clients where that didn’t resolve the problem. But it may work for others.
Unfortunately, there are so many variables in 64 bit systems and their drivers, that there are many different issues to resolve. One thing that I do see in SOME systems – there are more problems when all of your various device drivers are not upgraded to 64 bit versions. I had that issue with an HP driver on my system.
Kevin | Jan 13, 2010 | Reply
The error that keeps appearing after the temporary solution is “Print Driver Host for 32bit applications has stopped working.” Works for a little while then this error appears and I must close and reopen QB to do any printing at all.
Win 7 Ultimate 64-bit
Marty | Jan 13, 2010 | Reply
Charlie:
Thanks for all the fixes above. I tried them but still have the same problem. When I save as PDF or email invoices in Quickbooks all I get is a blank record. It has the outlines where the data is supposed to be but is blank. Any suggestions? I’m running 2009 R10P Windows 7.
Dave | Jan 13, 2010 | Reply
I tried the .dll update and QuickBooks stopped working. Then deleted the new .dll reverted the .old file back to the original and everything suddenly worked. Can print checks again and now able to run my critical financial reports. This one is sure causing issues. No offence Intuit (QuickBooks) but we pay a lot of money for your software and it’s mission critical to be able to run reports and print checks. You really dropped the ball on this.
Charlie | Jan 13, 2010 | Reply
Not to cast a wet blanket on things for you, Dave, but you may see the problem come back. On several sites (and Intuit confirmed this) I’ve seen where the problem pops up intermittantly. Works this time, reboot the computer and it might not work again.
I can’t believe that they released an update to the PDF driver in the R5 release of 2010. The R5 release was a last minute change to fix a problem in the R4 release, so it was done quickly. They should NOT have decided to throw in a change (upgrade) to the PDF driver in a release that didn’t get wide testing, particularly given the problems that we had with 64 bit PDF drivers the prior year…
Garrett | Jan 14, 2010 | Reply
Charlie is dead on. The latest fix worked for us for about 36 hours, and then it reverted. Now no matter what trick I use, I can’t get it to work. It might work for one print/email, and then it’s worthless again.
Looking forward to hearing more on this issue. Using this page as my source for updates
.
Barry K | Jan 16, 2010 | Reply
I Remember a time before I invested in this new expensive 64 bit, Windows 7 system when I could just invoice my customers via email without having to delete PDF Converters, Switch .DLL files and then switch them back and reboot and change .DLL files again and then switch them back just to send a invoice. Boy…those were the good old days.
Bob M | Jan 17, 2010 | Reply
I too have been fighting this issue to no avail. I’m running QB2009 R10 on Vista 64Bit and cannot get past the -41 error.
I dont know if this is helpful to you folks, but when I look at the printer properties>About tab, the AMYUNI splash doesn’t display the Intuit License, rather it displays [N/A]. I dont know why it isn’t picking the license code, but I believe that is the root of the problem, at least for me…
FYI That DLL file gives me a mostly blank print box; just controls on the right side.
Thanks for the other suggestions,
Bob
Bob M | Jan 17, 2010 | Reply
Thanks for the heads up on CutePDF! It just works…
Bob
Fred | Jan 17, 2010 | Reply
Charlie:
I have read this entire thread and have successfully gone through the PDF converter drill and the .dll drill. I have QB pro 2010 Release R.5P running on Windows 7 and I use MS Outlook 2007 for email.
This was an upgrade from QB Pro 2009. The reason I bought and downloaded 2010 was because I could not get payroll updates, namely 21004, and as such could not process my 2009 W2/W3’s. The system was stuck in 2008.
Well the 2010 upgrade still won’t allow me to get payroll updates even though my account is up to date and active. Adding insult to injury I have also lost my ability to email anything directly from QB.
I keep reading that I have to create an “outlook Profile” from edit – preferences – send forms. But there is no such icon in QB2010. Also when I try to email I get “Navigation to webpage was canceled”.
I am basically worse off than I was with 2009 and plus that I’m $160 lighter! Any suggestions would be appreciated.
Charlie | Jan 17, 2010 | Reply
Bob, be aware that the CutePDF driver only resolves some of the problems. I don’t believe that you will be able to reconcile accounts with that driver. We need Intuit to get us a complete fix for this.
Charlie | Jan 17, 2010 | Reply
Fred, do you have the US version of Pro? And, in your MENU (not icon) bar, click “Edit”, then “Preferences” – if you have the US edition you should see the send forms option listed on the left.
Kevin | Jan 18, 2010 | Reply
Charlie,
Do you have any contact information for some one at Intuit that I can complain directly too. Someone who actually cares that is. I am one of the idiots out there that pays for the annual enterprise upgrade that is very expensive. I do not want to talk to tech support. I want someone who cares when Enterprise customers want to end their upgrade program. I am not sure what I am paying for anymore execpt for software that is not tested. We have been using QB for almost 10 years but I am starting to look else where. Right now I am unable to upgrade computers at our office because new 64 bit computers currently do not work with the newest verisons of QB Enterprise. We are at their mercy and I am tired of it. Thanks for all your help. It is apprecaited!!
-Kevin
Charlie | Jan 18, 2010 | Reply
Kevin, I do have some contacts at Intuit, but I can’t pass out their contact info. All I can say is that some of them read this blog (can’t say if they read down through all the comments when we get this deep) and that they do read the “feedback” comments (in your help menu). That isn’t a great answer, but it is the best I can give since I’m not an employee of their company.
Annette | Jan 18, 2010 | Reply
I have tried so many “fixes” that have not worked. I have been pulling my hair out! I have QB 2009 R10 using 64bit Windows 7 Professional.
Windows7 Professional allows a virtual PC to be created in Windows XP mode. I created the virtual PC in Windows XP mode. Installed my QB 2009 and then restored my database. Everything prints, I can email invoices again, and do everything I need to do. Such frustration. When I called QB they refused to give me help unless I purchased a service contract.
Annette | Jan 18, 2010 | Reply
I forgot to thank everyone here for their suggestions and tips. As I said, I tried everything, but the “fix” I mentioned above was the only thing that worked for me. It’s really not a “fix” really, it’s just a great way to use XP on a Windows 7 machine. (Imagine that, Microsoft did something right!)
I have too much to do (as I’m sure I’m not the only one here) like Quarterly Payroll taxes, end of year payroll taxes, W2s and W3s to print out! I couln’t spend any more late nights and endless hours trying stuff that made me want to scream when it didn’t work.
I’ll keep an eye on the comments to see if QB actually comes up with a viable fix.
Chris Arkwright | Jan 19, 2010 | Reply
Thank you! The first method worked perfectly! Intuit has been terrible as far as support for errors like this.
Charlie | Jan 19, 2010 | Reply
Annette, thank you for pointing out the workaround of using the XP Mode feature of Windows 7. I’m not sure if that will work for people who need multi user access or not (I’m out of the office this week and can’t check that). It only works if you have a higher version of Windows 7 (not the home versions). For those of you who don’t know about this, ready my article at http://qbblog.ccrsoftware.info/2009/10/quickbooks-and-windows-7/
Michael S | Jan 20, 2010 | Reply
Charlie,
I am running Windows 7, 64 bit, QB 2010 rel R5P. I tried the fix replacing the DLL file but that created other print errors so I went back to the old DLL version.
Have you tried this fix: Right click on the Quickbooks software icon, select Properties, select the Compatibility tab and then check Compatibility Mode running as Windows XP (Service Park 3). (oh and also select “Run this program as an administrator” in the same tab.)
Michael
Lou | Jan 20, 2010 | Reply
We too are having the same problem with Windows 7 x64 Enterprise. Tried the steps in the previous article to install the updated x64 quickbooks pdf driver but that didnt work. Also replaced the DLL as this article suggested from Quickbooks but the problem still remains. Setting the compatibility mode to windows xp sp3 didnt work either. help
Annette | Jan 20, 2010 | Reply
Charlie, you’re welcome.
Michael, did that work for you with QB2010? I tried that in in Windows 7 Professional 64bit using QB 2009 R10, but it didn’t work. I still couldn’t print nor email invoices.
Maybe it will help others though!
Michael | Jan 20, 2010 | Reply
Annette,
It has worked so far! I am running Win 7 Ultimate
Charlie | Jan 20, 2010 | Reply
Michael S: I haven’t tried your solution, as the DLL solution works fine on my system. I wouldn’t think that your solution would resolve the problem based on what I think is going on, but if it works for you that is another thing for people to try.
Garrett Griffin | Jan 21, 2010 | Reply
Unfortunately Michael’s solution did not work for me.
To save anyone the trouble, here’s a few more things that DO NOT WORK:
1) Changing the printer driver to that of CutePDF or an older version of Amyuni does not work.
2) Changing the port to share a port with CutePDF worked for one or two invoices, but not properly, and was not a workable solution.
John | Jan 21, 2010 | Reply
Charlie, Thanks for all your work on this. I experienced identical errors and your DLL re-install solution worked – sort of. I can now perform reconciliations, print reports, save reports in pdf format again, but I am having a new problem. When I try to print the Print Reports dialogue box is blank, except for 5 buttoms on the right (print, cancel, help, preview and signature). I can hit the Print button and the report will print, but all other features, like print orientation, # of copies) are unavailable to me. So I am back to exporting reports to Excel, reformatting and printing. Any ideas what is going wrong now – with this weird blank Print Reports dialogue box? Thanks so much.
Tim | Jan 21, 2010 | Reply
We have the same results as John. Win 7(64 bit) with QB2009 R10, new DLL installed. PDF printer works, but the print dialog is empty except for the 5 buttons mentioned.
Is this behavior related to the PDF printer or is it something else entirely? I might guess that it is a different issue than the PDF printer bug.
Perhaps I haven’t thoroughly searched the live community and this is already answered?
All suggestions welcome. This is my first post and I’m very new to QuickBooks.
Charlie | Jan 21, 2010 | Reply
Garret, the CutePDF driver performs a very different function than the Amyuni driver. QB won’t use the CutePDF driver in the same fashion. CutePDF is just another printer driver, it happens to print to a PDF file, and the special PDF functions in QB (reconcilation, email export, etc.) won’t see the CutePDF driver. Totally different thing here.
Try Annette’s suggestion if you have an appropriate version of Windows 7. You can do the same thing in Vista using a download of Microsoft Virtual PC, but that is a bit of extra work to set up (see my older article on this at http://qbblog.ccrsoftware.info/2008/05/quickbooks-in-a-virtual-pc/)
Tim, John, I’ve not seen that happen and I don’t have an answer for you. Each system has different issues. If I haven’t run into it my self I can’t give much help. I’m one of the lucky ones where the DLL problem worked.
I’m actually on the road this week so I’ve not been able to get in touch with my contacts at Intuit to see if there is any good word from them…
Bonnie | Jan 22, 2010 | Reply
Hi. I had the blank print dialogue box. I ended up reinstalling quickbooks and reinstalling my printer several times and it fixed the print dialogue box and the pdf issues. Just kept restarting the computer after quickbooks installation and after each attempt at reinstalling my printer and that solved it finally. when i called intuit for advice they told me their only advice was to upgrade to qb2010 bc it is the only one they support for windows7. nice.
Charlie | Jan 22, 2010 | Reply
That is a stock answer – if you say “Windows 7″ they’ll say “QuickBooks 2010″ regardless of what your issue is, because that is the only release that is officially supported by them on that operating system. It is a support script.
And if you update to the current release of QB 2010 you may still have a problem, as we have seen above.
Flor | Jan 24, 2010 | Reply
it just so bad that quickbooks introduced the R10 without really testing it out good and make us end in a jam, specially now since it is deadline for tax reporting
Sonn | Jan 24, 2010 | Reply
In December I purchased a Dell that has Windows 7 Home Premium (64-bit), and I use QB Pro 2009 R10P. I have been extremely frustrated the past month trying all of these different fixes in order to fix this 32 bit-pdf problem, with only limited success. I have been unable to get the dll file from Intuit; I have requested it several times and never got the email. I am at the point I would just get 2010, but it seems that has the problems as well, which would not be conducive to my stress level. I am “forced” to upgrade QB every 2 years for payroll, and this was not my year. Between QB, the payroll updates, and ProSeries, I give Intuit a lot of money every year and really do not appreciate being left hanging like this while they and Microsoft point fingers. At this point, I will have to consider alternatives.
Zach | Jan 25, 2010 | Reply
I followed all the instructions here without any luck at first. I am running QB 2009 R10 on Win 7 x64. Finally, I just tried uninstalling, rebooting, and re-installing. To my surprise QB had no issues with PDF printer afterwards. When I uninstalled I made sure to remove all the PDF printers as well before rebooting.
Mike Lemons | Jan 25, 2010 | Reply
I found this site and this thread very helpful in resolving a cleint’s problem that seemed to relate. They run SBS 2008 (64-bit) and QB Premier Contractor Edition 2010 Release R5P. Their server runs the QB Database and there are 4 or 5 office QB users. The Office Manager has been unable to e-mail pay stubs recently, getting “Your forms were not sent because QuickBooks could not create the necessary PDF files.” We first tried deleting and letting QB recreate the Quickbooks PDF Converter 3.0 virtual printer, but that did not work. Then, based on Charlie’s instructions, I noticed that all 3 QB-related PDF converter virtual printers were set to use Port LPT1. I changed them to use the “NUL” port and the problem was resolved. Did not attempt the DLL update, since all clients are running XP Pro 32-bit.
Huey | Jan 26, 2010 | Reply
Why can’t Intuit just make a patch release that reverts everyone back to the version before R10? Wouldn’t that stop the issues that we are having. By the way Charlie, tried the new work around that you put up about reinstalling the driver from Amunyi, still didn’t work. Getting pretty mad here.
Lynn Glessner | Jan 26, 2010 | Reply
Just to add to how random this is, for a while it started working on my W7 laptop, and I didn’t care why, I was just happy. I created and sent a few invoices successfully. Today I created an invoice and sent it via email. Then I tried to email an old invoice and it failed – repeatedly. I restarted Quickbooks, and send it successfully from the “you have forms to send” screen.
The strategies of reinstalling printer drivers and dll files seems to be mostly coincidence but not actually addressing the real bug — nothing about my system changed during this 15 minute period when it worked, stopped working, and started working again.
Geoff | Jan 26, 2010 | Reply
Charlie: Thanks for the info. My problem is a bit different and I don’t know if it’s one you’re seeing. I run XP-SP2 and have used QB Pro for several years. Last year I also loaded Quicken & Turbo Tax to help a relative with their books, both of which have since been removed via the standard removal routine. My issue is this: I have four (4) QB printers installed: QB PDF [Amyuni Document Converter 2.50d-4], QB PDF Converter [Amyuni Document Converter 2.50d-4], QB Intuit Internal [Amyuni PDF Converter 2.07c], and QuickBooks PDF Converter [Amyuni Document Converter 3.03]. ALL of these are set to the LPT-1 port. I just cannot fathom why (a) these are all here and not cleaned up by Intuit in their install/remove routines; and (b) why I would need more than one?
Sonn | Jan 26, 2010 | Reply
I agree with Lynn, the biggest problem seems to be the randomness of it all. After trying all the fixes, I uninstalled and reinstalled, updated, and things seemed to work…for a short time. My port has always been “NUL”, even “NUL:” as it said somewhere. The only thing I never did try was the dll replacement, and that is only because I could never get the file from Intuit. The final thing I got working before I gave up was to run it in Windows XP mode (service pack 2, not 3), which again worked like twice, then stopped. I think at some point one you have tried so many fixes you have to uninstall/reinstall to clean up.
Charlie | Jan 26, 2010 | Reply
Sonn, if you contact me directly at the email address in the blog “about” page, and mention this problem (not getting the DLL), I’ll see if I can forward the info to someone who can help. I can’t promise it will work for you, but we can try. You might check your junk mail folder as the email message might get stuck in there…
Charlie | Jan 26, 2010 | Reply
Zach, we’ll all cross our fingers for you. Many people find that the fix works for awhile but then fails again later, in the situation you describe. Good luck!
Charlie | Jan 26, 2010 | Reply
Mike, if the clients are 32 bit, the DLL update wouldn’t have any effect. You have a problem (that you fixed) that is unrelated to this particular issue, in my estimation.
Charlie | Jan 26, 2010 | Reply
Lynn, in some situations QuickBooks tries to “repair” itself. If you totally delete the PDF driver, for example, the next time you try something that uses it QB will reinstall it (or try to). So for some reason, QB is trying to “fix” things, and of course it is trying to fix it to the point where the problem exists. At least that is what it looks like to me. The funny thing is, on MY test system, I don’t have any troubles after doing the DLL update. Every system is different, and the fault there isn’t entirely with Intuit. But they did make a big mistake here…
Charlie | Jan 26, 2010 | Reply
Geoff: I can’t answer why Intuit does anything the way they do. It can be a complete mystery. Sometimes they are very clever, sometimes they are very sloppy. Uninstalling drivers can sometimes be a bit tricky. From my experience with a QB-only system you can delete all the old drivers and just reinstall the one that matches your version of QB – assuming you only have one version of QB installed. I don’t want to tell you to do that, though, because you have Quicken and Turbo Tax, and I don’t know which drivers are used by which versions.
Eric Long | Jan 27, 2010 | Reply
Update 1/27/10: SOLUTION!!!!
After easily spending 8 hours on my own researching and trying all the hoops (repair, reinstall, replace qbwpr32.DLL, delete Quickbooks PDF printer and re-create, etc.), and an hour on the phone with Intuit, Charlie, the Customer Service Representative FINALLY got this resolved:
There is an updated PDF convertor. It’s called “PDF V 3.03″ and the direct download link is https://www.quickbase.com/up/ba8uqfzbq/g/ref/eg/va/QBDPDF_303.exe.
In any event, I can now save as PDF and email items on the computer and through Windows Server 2008 R2’s RemoteApp using EasyPrint.
Hope this saves someone the hassle I went through!
Eric Long | Jan 27, 2010 | Reply
I should mention that I am amazed that it took Charlie about an hour to find that solution. In light of all the problems with this, the updated PDF converter should have been the first solution that popped up on his support tools. He really had to dig and of course first suggested, then tried all the things I had previously done.
Charlie | Jan 27, 2010 | Reply
Eric, I’m not sure what exactly you are trying to say about your “amazement”, but I would like to clarify a few things.
The 303 driver you refer to won’t always work. It might, it might not.
That is the Amyuni 300 driver, which I talked about in 2008 when we first had the 64 bit problem in QuickBooks PDF drivers, as I talk about in my article at http://qbblog.ccrsoftware.info/2008/10/solving-quickbooks-problems-on-64-bit-vista/ – that article has a link to that driver also.
That was the first thing I tried on my Windows 7 x64 system because it had worked earlier on my Vista x64 system. It didn’t resolve the problem for me on a permanent basis. When I rebooted my system and ran QB, it stopped working. Note that the latest driver Intuit is providing with this update is the Amyuni 400 driver.
I will note, as you have seen, that this solution may work for some people. It is another approach to try. In MY particular system the DLL solution worked, and it continues to work. Obviously others have found that it works, AND yet others have found that it does NOT work.
There are a lot of variables involved with Vista and Windows 7 x64 systems, and I’m not sure we have a permanent, universal solution yet. I’ve asked for an update from my contact in Intuit, but I haven’t gotten a response for awhile.
In any case, Eric, thanks for pointing out yet another option that may work for some people – we need all the options we can get…
James Morrison | Jan 27, 2010 | Reply
Same kind of problem with Windows 7 and 2010. You would think a company with this kind of money and reputation would have a fix out in 2 days but instead they post “try to fix” articles to make their software work. It’s truly ridiculous that they would release the 2010 version that isn’t compatible with an Operating System that they mark as compatible.
My company will have all the paper work ready Monday morning to file the claim against Intuit for this type of irresponsibility to the consumer. I’ve tried EVERY fix for this suggested, ANYWHERE, including the company’s website. I’ve probably close to 25 hours in trying to make this function so we can email the invoices to our 5,331 clients and I successfully got it to send and create one PDF invoice.
Did they even run a beta for this on Windows 7? If so, what was the lifespan of the beta run? What? 2 days so they could release and pull the profits?
I could understand if this was an isolated problem with a few consumer’s machines but this has been affecting everyone with W7. I got it to create a PDF invoice one time is this is what I did if I recall the steps correctly:
1. Close the app.
2. Reboot.
3. Remove all printer devices.
4. Unplug Laser printer.
5. Reboot.
6. Start the app.
7. Receive the error again.
8. Close the app
9. Remove PDF converter again.
10. Start app.
11. Open invoice.
12. Select send email.
13. Successful once
13. Error received again on next try.
Maybe someone can tell me why I’m getting the error from what I had to do to have it send an invoice via email 1 time.
Thanks,
James
Debbie | Jan 28, 2010 | Reply
I found this post (after several hours of attempting various other fixes) but unfortunately none of the suggested methods worked for me.
I just spent an hour on the phone with Intuit tech support to be told that 2009 R10 is incompatible with Windows 7 and that I needed to upgrade to 2010.
I would be happy to do that, had I not purchased 2009 Pro less than 8 months ago for the very same price that Intuit wants to sell me 2010 for now. Why is the price for the upgrade the same as for the full product?
For now I will live with having to delete the PDF converter every time I need to send an email, and hope that Intuit decides to support long-time users who happen to be using a new OS. I’m not paying for this software again this soon.
Charlie | Jan 28, 2010 | Reply
Here is another thought for those of you who are having difficulties. I don’t like this, but if you are desperate…
Try uninstalling QuickBooks and deleting the PDF driver.
Reinstall QB from your original CD if you have it. You should be back to R1, and you won’t have the problem supposedly. It was introduced in R4 (2010) and R10 (2009).
The problem is that you will get warnings when you open your company file that you are using an older version. For 2009 users you won’t be able to open the file at all. In addition, you get all of the bugs back that were fixed in later revisions.
BEFORE you try this feel free to contact me directly and I can get you a copy of the update program that would take you to R2 (2010) or R9 (2009). Please note that I won’t provide free direct support, I’ll just be providing the updates. AND be aware of what bugs you are reintroducing (you can see the list of bugs that are fixed in R4/5 and R10). This may cause major problems if you are using Payroll, and possibly cause problems with sales tax, as other articles in the blog talk about.
Again, I don’t recommend this unless you are desperate and all other solutions have failed, and if you understand the problems that might be created.
Sonn | Jan 28, 2010 | Reply
Although I have not been able to get back to my own Win7/64-bit and QB 2009 R10 problem, I ran into another interesting problem when helping a friend/client print W-2’s and other payroll reports. I saw some of the exact same messages on her Win7/64-bit system running QB 2010 as I am seeing on my own system. Literally the exact same messages, that all add up to the pdf function not working. This supports the statements made by others that there are also problems with 2010, even though it is supposedly compatible. She got 2010 at the insistence of Intuit since she was still running 2007, needless to say, she is kind of mad there is this problem, and she can’t go back as her data files have been updated to 2010. What a mess!
Barry K | Jan 29, 2010 | Reply
THANK YOU ANNETTE! I tried your advice and I created the virtual PC in Windows XP mode. Reinstalled QB9 in the XP mode. Like you said…it isn’t really a fix but at least for now I can invoice my customers without all the hassles at least until Intuit comes up with something.
Virna M | Feb 1, 2010 | Reply
I know how to fix the ‘contact the administrator’ problem… it’s the permissions on the file folder. You have to set them to allow users to modify. That worked for me with that problem.
Unfortunately, the emailing invoices still won’t. I got it to work one time and then it’s erroring out again everytime after that. I’m going to try the NUL thing now.
Virna M | Feb 1, 2010 | Reply
SCORE on the NUL thing! I have emailed 2 invoices so far, without the glitch. Fingers crossed it stays!
Ashley F | Feb 1, 2010 | Reply
hi there. i have had all the same problems trying to email a statement from qb2009. i have version 19 of 2009 running on Vista/64.
i tried all the fixes and none of them worked, but here’s the deal…i CAN email a statement if i use the simple (ugly) Quickbooks template with no customizations.
if i try to modify (personalize) the template, it will not email and i get the “thunking spooler” stuff.
for those of you who are desperate, you might try using the basic templates that come with QB and see if you are able to at least get your information out to customers.
Ashley F | Feb 1, 2010 | Reply
PS – after trying out lots of variables with the Quickbooks statement forms, it appears pretty much any form will email as a .pdf as long as you don’t use a custom color in the statement. I was able to use my logo and reformat the standard template and send my statement. Only when I added a custom color was I denied with a “thunking spooler.” poo.
Annette | Feb 2, 2010 | Reply
You’re welcome Barry! This is the only work around that has been successful for me thus far. Until there is a final fix from Intuit, I’m going to stick with the virtual PC in XP mode. I’ve been using it for three weeks without a hitch. Just emailed all my February Invoices, printed my quarterly and end of year stuff.
I’m keeping an eye here for any other suggestions, but so far this is working for me. Thanks to everyone here for their efforts. Despite the extreme frustration that everyone is going through, everyone is very civil and helpful here. A sign of true professionals. Kudos to everyone for hanging in there. Shame on you Intuit!
David | Feb 2, 2010 | Reply
Thanks Soooo Much! After 3 hours with “Tech support” they couldn’t solve. But your detailed info and pic’s made it easy. Thanks again!
Tim | Feb 3, 2010 | Reply
Charlie,
Thanks for leading this discussion. You are an invaluable resource.
Could you publish what drivers, settings, and other variables you have on your machine(s) that work? Perhaps if there were more detail, we might be able to identify differences on our systems that aren’t working. And maybe even fix/adjust them so we could get more consistent operation.
Here’s an example of what I’m talking about:
PC is HP Pavilion 6347c with 6 Gig RAM and Athlon 630 quad CPU, running Windows 7 Home Premium. (Considering upgrade to Business or Ultimate to get XP mode)
Office network is router based with NetGear WRG614 (no wireless)
QuickBooks is 2009 R10 in multi-user mode. (All other networked QuickBooks PCs are XP SP3 running QB2009 R10 and work fine.)
Using the latest DLL, we can rarely email invoices, after repeating the install steps, etc.
What other drivers, setups, or configurations might be relevant? I’m particularly interested to hear about stable, working systems.
Thanks again for yours and everyone else’s help.
Tim
Charlie | Feb 3, 2010 | Reply
Tim, unfortunately, I don’t think that will help. I only have one 64 bit system and I don’t have a way of doing extensive testing like I can on 32 bit systems. If I had a system here that did NOT work after trying the DLL, then I would be able to work on pinning down the variables involved.
Also, in my system, I have both the 2009 and 2010 versions installed.
My past experience with Vista on this system (also an HP system) showed me that if I had system drivers that were not the latest 64 bit versions, odd things happened. I had many problems with printing in the system at that time until I found that one of my laser printer drivers was not a 64 bit driver. Problems went away when I got all system drivers updated. And, with HP, I’ll note that the did NOT supply all 64 bit drivers in the system “out of the box” – I had to locate and install the proper drivers myself.
When I set up this Windows 7 system (clean install) I made sure that all drivers were 64 bit versions. I’ve had little trouble with the system since then.
But, without the ability to see a particular problem and work on it myself, I’ve not been able to pin down anything for anyone beyond what I have here.
And for some reason, the engineering contact I was working with at Intuit has not been responding to queries the past few weeks…
Kevin | Feb 4, 2010 | Reply
Charlie can you confirm that on Quickbooks Enterprise 10.0, PDF functions are working correctly on 64 bit Windows 7 machines?
Charlie | Feb 4, 2010 | Reply
Kevin, on MY Windows 7 x64 system, with the DLL patch, the PDF functions work correctly with Enterprise 10. This might not be true for ALL installations like this, but on mine it is working.
Bob | Feb 4, 2010 | Reply
I’m running Windows 7 and QB2009. The fix solved the email issue and everything seems to work just fine, except for one small issue: When I go to print a single Invoice, Purchase Order or Report the box that opens up no longer has the fields that allow me to choose how many copies I want to print. I end up just printing multiple copies one at a time. Anyone else have this issue?
Aaron | Feb 5, 2010 | Reply
Charlie, thanks for taking all these points and trying to disseminate them all.
I have QB2010 on Windows 7E 64bit, updated to REv5
I did the dll fix and reinstalled the printer and assigned it to port nul:, now when I try to email i get the same error inside quickbooks that it “Cannot Print to printer, etc…” but the Print driver host for 32bit applications crash error is no longer there, it just errors out in QB. I guess I should wait for Inuit to address this? No runtime error, btw.
Keith | Feb 5, 2010 | Reply
Charlie,
Thanks!!!! QB2010 Windows 7 64 updated to latest. Deleted QB PDF Converter, downloaded dll, renamed existing dll, copied downloaded dll, opened QB. Sending PDF invoices again.
Medical | Feb 6, 2010 | Reply
As expectet and like all intuit products, they hardly do what they are supposed to.
We called the support and went through this exact steps and still cannot generate a PDF.
Intuit blamed our hardware, we tried it on 12 different PCs, and to prove them they are wrong, we purchase 2 more with only the OS and Quickbooks on them and the same problem still happening. As of now Intuit did not provide any solution and our frustration with this incompetent company is growing by the minute.
Can anyone recommend another software that is compatible with Quickbooks?
charles857 | Feb 11, 2010 | Reply
I downloaded the new file qbwpr32.dll and replaced the old one. It works fine now to email documents. However, a new problem occured. Anytime you try to print any documents (invoice, purchase order), the printing window now is mostly blank, only right side buttons are showing. No drop-down window for you to choose different printer any more.
Charlie | Feb 12, 2010 | Reply
If you are using QuickBooks 2009, the R11 release has just come out, and it should fix the 64 bit PDF problem. See this article: http://qbblog.ccrsoftware.info/2010/02/quickbooks-2009-r11-update-fixes-pdf-printer-problems-with-64-bit-systems/
For QuickBooks 2010 users, Intuit says that they are still working on this issue. I’m hoping that something will come out soon…
Mary Johnson | Feb 12, 2010 | Reply
I have Windows 7 64-bit, running QuickBooks Premier 2010. I have narrowed down my .pdf print problem to the NUL: port. It gets setup properly when I reinstall the amyuni driver to recreate the QuickBooks PDF Converter 3.0, and printing works UNTIL I reboot. Then I find that the NUL: port is no longer there. How do I get this NUL: port to not get deleted when I reboot? This is very repeatable. I am convinced this is my problem.
Jason | Feb 12, 2010 | Reply
Does this most current update in any way address the winmail.dat issue that occurs when you click SEND FORMS>EMAIL to send many invoices or statements to customers?
Charlie | Feb 12, 2010 | Reply
Jason, I’m not familiar with that problem, but the article I wrote lists all of the bug fixes that they acknowledge in this release. I don’t see anything specifically addressing your comment unless it is an outgrowth of the PDF driver problem.
Jason | Feb 12, 2010 | Reply
Charlie, Ive been doing net research and its a fairly common problem it seems but seems to be somewhat illogical. When we make invoices, and click the ‘To Be E-mailed’ box and at the end of the day, we go to SEND FORMS and send all of the invoices we made via email. Some of the recipients do not receive a PDF as expected. Instead they get a winmail.dat file. It appears if we send via email from inside the invoice itself, at the time of creation, we dont have this problem. It has something to do with the mass email send.
Charlie | Feb 12, 2010 | Reply
Jason, I’ve not come across that myself, and none of my direct support clients have reported that, so I have no experience with that. It isn’t mentioned by Intuit in the list of bug fixes in the 2009 R11 release. However, sometimes they don’t always tell us all of the things that are fixed or changed in a release…
Vanda | Feb 15, 2010 | Reply
Charlie,
Thanks so much!! I’m using QB2009 Premier on a new laptop with Windows 7. I too was getting errors just tring to save a QB report as a PDF file to print or email later. Windows troubleshooting for the QB PDF Converter priner didn’t work. But your link to the QB site and their update patch worked perfectly for me! Was getting pretty frustrated but you’ve made my day better now!! Thanks.
Vanda | Feb 15, 2010 | Reply
You also saved me lots of time with QB talking to support. My last conversation was over an hour! You’re site is now saved in my “favorites”!!
Annette | Feb 17, 2010 | Reply
Charlie, I just updated my QB2009 64 Bit (using window 7 Professional) to the R11 update. I can print invoices but STILL CAN’T EMAIL! Arrrgh!
Still using the Virtual PC in XP mode with no problems and looks like it’s going to stay that way!
Thanks for all your help!
Charlie | Feb 17, 2010 | Reply
Annette, with R11 (not in XP Mode), can you try reconciling a bank account? See if that works.
Aaron | Feb 18, 2010 | Reply
Just updated to R11, and it fixed everything, I can reconcile, send emails, print to PDF, the whole kaboodle. Some of you people are a little impatient, I knew Inuit would fix it soon because their customer base is enormous, Not to say they are an amazing company or anything, but they’re not inept.
John | Feb 20, 2010 | Reply
Charlie, I just downloaded R11 for my QB Premier 2009 and all remaining 64-bit pdf issues seem to be resolved. Thanks so much for all your help and patience. You were a huge help in keeping me up and running during this ordeal. I heartily agree with the “shame on you, Intuit” comments above for putting us through such hassles for so long with no clear fixes. Thank heavens you were there for us!
Barry K | Feb 25, 2010 | Reply
Well Aaron…some of us are a little impatient. We have businesses to operate. Some of us feel that Intuit could have communicated with us during this ordeal. Thanks again to Charlie for at least trying to help us through this (alot more than Intuit did for us). So far, R11 has worked.
Keely | Feb 26, 2010 | Reply
Charlie, I have followed this entire thread & want to thank you for taking the time to do something that Intuit should be doing, namely offering support to its’ users.
I am so totally totally frustrated with my QB Pro 2010. I was on Pro 2008 but upgraded last month to Windows 7 64 bit, only to find it incompatible with Windows 7. So I upgraded & forked out for QB Pro 2010, only to start having issues e-mailing monthly bills & statements to my clients. None of the fixes published worked. I tried the dll fix, only to end up with worse problems so reverted back. Tried all the other fixes published in the knowledge articles, including the NUL port, spooling etc. None of these fixed the issues.
I am now at the point where it is end of the month, I need to send out multiple statements to customers on their monthly accounts & simply cannot. Nor can I save a statement as a PDF & send it via outlook as you cannot save statements as PDF attachments. Nor can I e-mail it to myself (as recommended in the Help section of Intuit on how to e-mail a statement as PDF) as I can’t e-mail via QB!
I cannot begin to express how disappointed I am in Intuit for not sorting this out nor can you call them without them charging me for their problem. If any senior Intuit employees are reading this you should be ashamed of yourselves for offering such shabby customer service.
Charlie | Feb 26, 2010 | Reply
Keely: I won’t comment on their support policies other than to say that isn’t how I run my software company.
I will say that they ARE sorting this out, they fixed it in the 2009 product and are working on the 2010 product. I don’t know why it is taking so long (although I have some guesses). I do know that it is of concern to them and they are working on it.
For the interim, you can get a PDF printer driver and print any statement or report to a PDF file, then attach it to an email manually. I use Adobe Acrobat myself. I’ve heard people talk about CutePDF, but I don’t have experience with that nor do I know if it works on 64 bit systems. I’m quite happy with Adobe.
Lisa | Feb 28, 2010 | Reply
I found this last night and read all of your experiences in growing anger. I have Windows 7 64 bit and QB Pro 2010.
Since getting this system set up in early January (my hubby has one too, but mine is the host), we have had a multitude of conflict issues. And this is the latest and greatest. Can’t save a PDF file, can print somethings sometimes but not always, on and on. I have tried most of the above fixes to no avail. This cannot go on Intuit must come up with an immediate fix. We have businesses to run. We purchased this product in good faith and expect a superior product in kind…….I have been running QB 2008 and before that 2005 with no problem. This is inexcusable!
Annette | Mar 1, 2010 | Reply
Charlie,
I uninstalled the extra PDF converters that I had previously installed while trying to fix the problem before I decided to do the Virtual PC in XP mode.
After deleting the PDF converters and re-booting, QB on my maching (Windows 7 Professional64 bit) is now working smoothly. Thank goodness for being able to operate this in a Virtual PC mode during the three months of invoices and emailings I had to get through. Not to mention TAX FORMS!
Thanks again to you Charlie and everyone here for Herculian efforts to try to resolve this.
Again, shame on you Intuit for causing this mess up. Granted, everyone makes mistakes, but you added insult to injury by demanding payment from us for customer service to fix it when we called you for help!
Mitch | Mar 1, 2010 | Reply
The winmail.dat issue seems to be related to a mapi send when using exchange or small business server as a mail server.
I found an article on EE that notes the problem:
Props to dave for the summary.
When Exchange sends RTF it uses a “standard” attachment to contain the MS-TNEF formatted content. Outlook silently decodes this – anyone using another mailer sees an attachement they can’t open.
Disallow RTF – it should fix the issue:
Here is more information from Microsoft:
http://support.microsoft.com/kb/138053
http://support.microsoft.com/kb/278061
Another writeup:
Mitch | Mar 1, 2010 | Reply
For what it’s worth though, after a little more reading I’d blame Intuit… It looks like MS defaults to RTF if the mode is not specified. Intuit isn’t reading the users preference and using it – it isn’t offering the user the choice… so it’s either specifying RTF OR that is just the default. It seems to be an easy fix though. And will fix all programs showing this issue I think.
Charlie | Mar 1, 2010 | Reply
Mitch, I had to remove a couple of the links you had in your message. The first one, the article, was a link to a service where you have to pay to see the answer. The last one was an invalid link, it gave a 4040 “not found” message.
Kevin | Mar 1, 2010 | Reply
I can confirm 4 machines are now working with PDF’s properly on Quickbooks Enterprise 10.0 R5 in Windows 7 64-bit environment.
I was able to get it to work using a combo of steps found all over the place. Forgive me if I am being repetitive. Just trying to help everyone who has helped me.
With Quickbooks closed…
1. Delete any existing Quickbooks PDF converter printer.
2. (Not sure if this is necessary but I did it on all my machines.) Check your other printers and delete any printer that is using the Nul: port to print. Check ports under properties. I had to delete a “One Note” printer that was using this port.
3. Find your installed QB folder and run the install.exe file that reinstalls the PDF printer driver.
4. In devices and printers, rename the new printer installed as “QuickBooks PDF Converter 3.0″.
5. Under printer properties of this new printer change the port to the “Nul:” port. If you don’t have this port look for instructions to create it. On the advanced tab change to “spool print documents so program…”. Uncheck “enable advanced printing features.” Then change previous setting back to “Print directly to printer.”
6. Download the updated .dll file from the links above.
7. Find your installed QB file folder again and change “qbwpr32.dll” to “qbwpr32.old”
6. Drop new .dll into the installed QB folder.
7. Reboot computer.
8. Open QB and try to email or create pdf. The FIRST TIME you will get the activated error. However, after that things should be back to normal.
Sorry if this appears to be a rip off of what’s above or elsewhere. I tried the above steps with no luck. I then tired various combos of Intuit suggestions, Charlie’s and others. Just wanted to help if I could.
Thanks Charlie!!
Keely | Mar 2, 2010 | Reply
Okay; I’ve got another one for ya! Now all of a sudden my payroll function has stoppped working. Worked fine last week when I cut the checks. I have 4 employess so subscribe to standard payroll service which has just been jacked up to $275 for the year. It’s now stopped working & by the looks of it I can’t call anyone unless I pay for it. This is disgraceful. By the way I have just run a manual update in case I was missing something & re-booted twice to no avail. In your opinion is this all to do with QB 2010 & windows 7 being incompatible Charlie?
Keely | Mar 2, 2010 | Reply
Sorry Charlie; I’ve managed to resolve by Payroll issue but I’m still wondering if it’s a bug. My updates are turned on automatically. When my payroll function suddenly stopped working I went & did a total system update through the help window in case it was my issue. When I had Pro 2008 my auto updates would not happen for some reason so I had to manually go & do them from time to time. This update I just did included payroll. The update downloaded okay & system got green light as updated. It didn’t fix the issue & still had problems with no deductions being calculated on payroll for employees.
I manually went in & created a paycheck with with-holding I separately calculated. When I tried to create the check QB told me that it could not create the check as my payroll data was not up to date. It suggested getting a payroll update via employees or renewing an expired payroll subscription (my payroll subscription is up to date). So I updated the payroll again through the employee function. It now works. Why? Why did it not work through the updates window? Any ideas anyone.
Charlie | Mar 2, 2010 | Reply
Kevin, there is a tremendous amount of variability in x64 systems. I’m seeing this in my own software on my own systems. It isn’t as steady or as stable as 32 bit systems yet. Because of this, everyone seems to have a slightly different experience. It isn’t entirely Intuit’s fault, although they did mess things up quite a bit with the R5 release. I didn’t have to go through all the steps you did to get it to work, but my system is different than yours. Thanks for posting what you found…
Charlie | Mar 2, 2010 | Reply
Keely, I don’t work with Payroll at all, so I can’t help much there. I thought that if you had a Payroll subscription you could get help from the Payroll support staff without having to pay for support? I think that you have to go through the Payroll support lines, although I’m not sure on that. That is the way it used to work a year or so ago, last time I had to deal with Payroll. Also – the payroll updates are a separate thing from the QuickBooks update. Updating your QB revision doesn’t address getting the latest payroll updates.
Keely | Mar 2, 2010 | Reply
Thanks for the feedback Charlie. I’m afraid payroll subscription only offers help if you pay extra for enhanced or total payroll. Standard subscription comes with no help. I did not realize that updates are separate on the help & payroll window. I figured, obviously stupidly, that if the updates on help window says it gets payroll updates it gets all the payroll updates. Obviously not! You live & learn. Wished they hurry up & fix this pdf problem. It’s making me paranoid!
Lisa | Mar 2, 2010 | Reply
I have learned to work around the fact that I cannot save to a PDF file in my QB Pro 2010 with my Windows 7 64 bit system. I export my report to Excel and then save the Excel. Don’t like it but at least it is something.
TODAY’S problem is that we cannot print checks. I have a call in to my QB consultant. Want her to contact her sources in AZ (not some foreign land that wants to charge you). See what answers they come up with. So absolutely inexcusable and frustrating. We should all get our $$$ back. But then what?
michael | Mar 8, 2010 | Reply
How about this folks i don,t do pdf stuff just print invoices Here,s what pop,s up out of the blue and the only fix is to shut down computer and restart then thell print, win vista qb2010 R5P so I get Error has occured in the script on this page line 7 char 0 error object expected code 0 url file://c:/ program data/lexmark%207600%20series/job%20status/scripts/jswxml How about that I wonder if I upgrade to Win7 afraid make it worse. put me down for a class action law sute
Joe | Mar 9, 2010 | Reply
Charlie, I have Win 7 Pro 64 & QB Pro 2010 R5. I have the e-mail .pdf problem and tried all the work arounds you have mentioned and the program behaves the same way. Still with the “Print driver host for 32 bit applications has stopped working” and then “could not print to printer, check your printer selection. Printing may have been cancelled from another program”. As stated above it is very frustrating. I have been printing out report then scanning them to .pdf files and attaching them to e-mails; very time consuming and a real pain. From your contacts at Intuit are they still trying to resolve this problem? (fingers crossed)
Charlie | Mar 9, 2010 | Reply
Michael: What you are describing is something different than what we are talking about here. That sounds like a faulty printer driver in Vista, or something similar.
Joe: Yes, definately they are working on the fix for QB 2010. At this point I’m under a non-disclosure agreement that concerns what is being done, all I can say is that things look very positive at this moment. More on this later.
michael | Mar 9, 2010 | Reply
Thanks Charlie I,ll screw around with your suggestions