I use Google's Internet calendar. Today I went to print my April calendar and received an error message from PDF XChange Viewer: Error opening document "C:\Documents and Setting... long file name... .htm"; Error [PDF Structure 40]:Invalid file format
Google's trying to lauch a PDF preview, so I switched back to Adobe as my default viewer. I still get the same message, even though when I click on a .pdf it brings up Adobe Reader.
I understand that PDF-XC Viewer doesn't want to read a .htm, but the Viewer shouldn't even be running during this operation.
I'm using free Viewer vs 2.0 Build 41.5 on Windows XP. Though I purchased PDF XChange Standard, it's not my default printer and nor did I select it.
The file listed in the message doesn't exist, nor does the folder. That's likely Google's problem. But why is PDF XChange Viewer executing? Any ideas anyone?
Thanks!
Elaine
P.S. I tried to attach the error message, but the forum wouldn't accept a .jpg or a .pdf.
PDF-XCV Error, Unable to Print Google Calendar
Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Paul - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange
-
squon
- User
- Posts: 4
- Joined: Thu Dec 28, 2006 4:42 am
-
Ivan - Tracker Software
- Site Admin
- Posts: 3603
- Joined: Thu Jul 08, 2004 10:36 pm
Re: PDF-XCV Error, Unable to Print Google Calendar
I see the same behaviour. As I see, print function on Google Calendar is oriented on Adobe Acrobat - they check if it is installed and use it.
By the way, will check why PDF-XChange viewer opened with .html file as an argument.
By the way, will check why PDF-XChange viewer opened with .html file as an argument.
PDF-XChange Co Ltd. (Project Director)
When attaching files to any message - please ensure they are archived and posted as a .ZIP, .RAR or .7z format - or they will not be posted - thanks.
When attaching files to any message - please ensure they are archived and posted as a .ZIP, .RAR or .7z format - or they will not be posted - thanks.
-
Cadillakin
- User
- Posts: 110
- Joined: Thu Apr 02, 2009 12:21 am
Re: PDF-XCV Error, Unable to Print Google Calendar
I get a different behavior on my setup... XP-SP3. When I click print within the Google Calendar page, I get a preview page, which offers me the options to save or print. If I print, it loads into my Xchange Viewer. From there, I can either save or print to my default Canon Printer.Ivan - Tracker Software wrote:I see the same behaviour. As I see, print function on Google Calendar is oriented on Adobe Acrobat - they check if it is installed and use it.
By the way, will check why PDF-XChange viewer opened with .html file as an argument.
In essence, the printing of the Calendar works somewhat normally for me.
-
Paul - PDF-XChange
- Site Admin
- Posts: 7447
- Joined: Wed Mar 25, 2009 10:37 pm
Re: PDF-XCV Error, Unable to Print Google Calendar
I find that in both FF and IE I have to choose 'Save As' after the preview page for PDF-XChange to open it.
Best regards
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
Paul O'Rorke
PDF-XChange Support
http://www.pdf-xchange.com
-
squon
- User
- Posts: 4
- Joined: Thu Dec 28, 2006 4:42 am
System hooks?
As paulororke mentioned, I used Save As as a workaround. Save As brought up PDF XChange Viewer (no longer my default viewer). This suggests that PDF XChange Viewer has hooks in the system besides default application for .pdfs. I'd like to know what these hooks are and have an easy way of turning them on and turning them off. This would allow me to continue to use XCV as my default, but know that I could easily turn it off if I ever have application problems again. (Could also save Tracker from some support problems.)
Today I successfully printed my calendar without using Save As. So either Google fixed their part of this or the Adobe 9.1 upgrade I installed yesterday fixed it. Perhaps Adobe uses the same hooks and reset them to Adobe Reader?
Elaine
Today I successfully printed my calendar without using Save As. So either Google fixed their part of this or the Adobe 9.1 upgrade I installed yesterday fixed it. Perhaps Adobe uses the same hooks and reset them to Adobe Reader?
Elaine