Problems with Outlook 2013 on a 64 bit machine

[mawallace]

I get the following message when I send an email from the viewer:-

Either there is no default mail client of the current mail client cannot fulfill the messaging request

I am using Outlook 365 Premium, which is 32 bit, and the Pro version of the Viewer.

It is annoying, to say the least?

Any ideas how to resolve this?

[Stefan - PDF-XChange]

Hello mawallace,

We released a new build of the Viewer last night. Could you please update to build 2.5.211 and check whether this problem still exists?

Also please do let us know which version of windows (Vista, 7 or 8 ) you are running.

Regards,
Stefan

[mawallace]

I have done this and the problem still exists!

It happens the first time that I try to send a document via Email.

I click send to, get the message, click ok, and then Outlook opens!!

It is then ok for that session that I use PDF viewer - then it reoccurs next time I open ot close PDF Viwer

[Stefan - PDF-XChange]

Thanks for confirming that mawallace!

I will check with one of my colleagues from the dev team now.

Regards,
Stefan

[Willy Van Nuffel]

I don't know if it may help:

In MS Internet Explorer 8, in the Tools > Internet Options > Programs-tab, there is normally a possibility to set the default Mail program. Is this set at your pc ?

In MS Windows 7 environment (with IE10) you can go via the Start-button > Default programs > to "Set your default programs".
Now select "Outlook 365" or "Outlook 2013" (if they are in this list) > then click "Choose defaults for this program" > check/activate "MAILTO" in the "Protocols" group.

At my own portable pc, I'm using "Windows Live Mail" as my default mail client, and it does not seem to make a problem to automatically start and generate an e-mail, after having clicked in PDF-XChange PDF Viewer Pro on the File-menu > Send by E-mail... > Send by E-mail.

[Will - Tracker Supp]

Thanks for that Willy,

However, I believe that this may be a 32-bit/64-bit compatibility issue.

mawallace, could you please advise as to whether the Portable version of the Viewer works?
Download link: https://www.pdf-xchange.com/PDFX_Vwr_Port.zip

If you have a 64-bit OS Architecture, the Viewer *.exe installer will automatically detect the system architecture and will install according to that architecture i.e. 64-bit OS, 64-bit installation of the Viewer. If Outlook is 32-bit, then the Viewer cannot call on this when using the "Send Via Email" function.

The solutions here are to a) Install a 64-bit version of Outlook or b) use the Portable Version.

Let me know how this goes!

[mawallace]

Thanks for that Willy,

However, I believe that this may be a 32-bit/64-bit compatibility issue.

mawallace, could you please advise as to whether the Portable version of the Viewer works?
Download link: https://www.pdf-xchange.com/PDFX_Vwr_Port.zip

If you have a 64-bit OS Architecture, the Viewer *.exe installer will automatically detect the system architecture and will install according to that architecture i.e. 64-bit OS, 64-bit installation of the Viewer. If Outlook is 32-bit, then the Viewer cannot call on this when using the "Send Via Email" function.

The solutions here are to a) Install a 64-bit version of Outlook or b) use the Portable Version.

Let me know how this goes!

This seems to be the solution - thanks

Is there going to be an upgrade to clear the issue on pdf viewer!?

[Will - Tracker Supp]

Hi mawallace,

Having spoken to the Devs. about this, they feel that we'd need a remote session to ascertain whether or not this is an issue with us or Outlook, or neither. At the moment, it's not clear why this happens and none of us here have actually experienced the issue ourselves.

Is a remote session something that you would be willing to work with us on? If so, please see this link, and send the Indemnity form, along with TeamViewer credentials to support@pdf-xchange.com, with a link back to this forum topic as a reference.

If it's not something that you're willing to go ahead with, then we completely understand, just please be aware that we likely won't be able to determine the cause if we don't have access to a system experiencing the issue.

Cheers, let me know if that's acceptable to you.