PDF Faxing Problems, please help

[JimmyHoffa]

Hi All, Hoping someone can help here as I've tried everything I can
think so far and exhausted my knowledge of these problems..

We have a client(on Vista) who has been happily faxing PDF's through
outlook(2003 SP3) until he upgraded adobe reader to version 9.

So first thing I did was revert back to version 8.1 of reader and
still no luck.. I get the "not all attachments could be rendered"
message.

So things I've tried are,
1. ensuring there is a correct printto verb present in the registry,
I can print ok with right click on a pdf.
2. Creating a new Outlook profile, in case of profile corruption..
3. uninstalling/reinstalling Windows Fax & Scan package.
4. Reverting even further back to Adobe reader 7.
5. Disabling all Outlook Add-ins/ Com- Add-ins.
6. Enabling Outlook Logging (but with no output whatsoever)
7. Removing and Reapplying the Fax Transport into outlook...

So What quite else I can do, I'm not sure so if anyone can give me any
suggestions on what to try next it would be greatly appreciated...

Thanks

 

[Russ Valentine]

Not an Outlook or WFS issue. Rendering is the sole purview of the
originating application for the image file. The only thing you can do is
make sure all file associations are correct for the file type in question.
Printto verbs are no longer used in WFS.

 

[JimmyHoffa]

Do you know if there's anyway to at least determine if outlook is
making the call to adobe, as it seems that is where the problem lies.
I think if it was making the call then I would be seeing Adobe
'appear' as I've removed the flags in the printto verb that request
adobe is hidden...

Rgds

 

[Russ Valentine]

Outlook does not make the call to Adobe. WFS does. The error message is
telling you that WFS is unable to do so. Since the problem arose after a
change in Adobe version, that's most likely where the problem lies. If Adobe
were invoked, you'd at least see a temp file created here:
%userprofile%\appdata\local\temp
How is the printto verb defined?
--
Russ Valentine
Do you know if there's anyway to at least determine if outlook is
making the call to adobe, as it seems that is where the problem lies.
I think if it was making the call then I would be seeing Adobe
'appear' as I've removed the flags in the printto verb that request
adobe is hidden...

Rgds

 

[JimmyHoffa]

Outlook does not make the call to Adobe. WFS does. The error message is
telling you that WFS is unable to do so. Since the problem arose after a
change in Adobe version, that's most likely where the problem lies. If Adobe
were invoked, you'd at least see a temp file created here:
%userprofile%\appdata\local\temp
How is the printto verb defined?
--

Do you know if there's anyway to at least determine if outlook is
making the call to adobe, as it seems that is where the problem lies.
I think if it was making the call then I would be seeing Adobe
'appear' as I've removed the flags in the printto verb that request
adobe is hidden...

Rgds

Hi Russ,

I'll look for the temp files next time I access the clients machine
and see if it's getting that far at least.

My printto verb is just the regular <path to acrord32.exe> /t /h "%1"
"%2" "%3" "%4" , this path I'm certain works as the printing from a
right click context menu is functional. I also tried removing the /t /
h so that I could see if adobe was appearing at all, but its not.

Rgds,

 

[Russ Valentine]

FWIW, I've never seen WFS able to render a PDF file as an attachment in
Outlook. PDF files have no printto verb defined in Vista.
You can, however, send a PDF file as an attachment from the Fax Console,
which is a new feature with WFS. Should work just as well since WFS will use
Outlook Contacts for recipient selection.
You should also be able to print to fax from Adobe.
--
Russ Valentine

Outlook does not make the call to Adobe. WFS does. The error message is
telling you that WFS is unable to do so. Since the problem arose after a
change in Adobe version, that's most likely where the problem lies. If
Adobe
were invoked, you'd at least see a temp file created here:
%userprofile%\appdata\local\temp
How is the printto verb defined?
--

Do you know if there's anyway to at least determine if outlook is
making the call to adobe, as it seems that is where the problem lies.
I think if it was making the call then I would be seeing Adobe
'appear' as I've removed the flags in the printto verb that request
adobe is hidden...

Rgds

Hi Russ,

I'll look for the temp files next time I access the clients machine
and see if it's getting that far at least.

My printto verb is just the regular <path to acrord32.exe> /t /h "%1"
"%2" "%3" "%4" , this path I'm certain works as the printing from a
right click context menu is functional. I also tried removing the /t /
h so that I could see if adobe was appearing at all, but its not.

Rgds,