[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2017
  • Last Modified:

No Default Client for Adobe Reader 11.0.3 With Outlook 2013 64bit

Whenever we open Adobe Reader or any pdf file, we get a Microsoft Office Outlook dialog window as follows:

"Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client."

We can still open any pdf files. However this dialog window is a nuisance.

I have made sure that Outlook 2013 64bit is checked for Default Mail Client.
I have also implemented an Experts Exchange registry solution changing the Mail key default to Outlook64Bridge and created a key of Outlook64Bridge with key DLLPath and DLLPathEx with defaults  of C:\Windows\System32\mapi32.dll.

What else can I do?

S.I.T.
0
SIT-SR
Asked:
SIT-SR
  • 3
1 Solution
 
dec0mpileCommented:
Try the solution on the following page: http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/error-when-launching-outlook-in-windows-8/82f8588e-e8d9-4230-8559-0429982a378c




I created a solution for this problem for 64 bit Windows 8 where Outlook 2013 was installed as Click-To-Run installation as a desktop application. Although I have not tested the solution with Office 2013 64 bit that was installed as part of Office 365, I adapted the registry edit from an Office 365 solution that I discuss at the bottom of this post. This registry edit is part of the solution to resolve 64 bit installations of Outlook, regardless of whether they are 365 or desktop versions. The problem that is resolved for both versions is that Click to Run installations of Office 2013 cannot be set as the default mail client. This registry edit fixes the Microsoft registry problem associated with Click to Run installations and enables Outlook to be set as the default mail client.

The following Link provides instructions on how to determine if Office is a click to run installation.

http://webcache.googleusercontent.com/search?q=cache:LTHzx4nXBm4J:msdn.microsoft.com/en-us/library/office/ff864733.aspx+&cd=1&hl=en&ct=clnk&gl=us

The following link indicates it is well documented that click to run version of Outlook can't be as the default mail client and that instead an Outlook version that is downloaded and installed in the traditional manner is required. That discussion at the below link is consistent with the description of click to run at the above link.

http://answers.microsoft.com/en-us/office/forum/office_2010-outlook/how-to-set-outlook-2010-as-my-default-email-client/2b8ddd10-1d30-4da1-a3f1-60dca071524b

A registry edit will fix the problem with Outlook 2013 click to run installations and enable Outlook to be set as the default mail client. This registry edit will for many third party programs eliminate the error "Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client." It worked to resolve the problem where Adobe Acrobat was generating this error.

The registry edit is here for Office 2013 64 bit click to run installations that will enable Outlook 2013 to be recognized by third party applications:

1. Create registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\15.0\Outlook

2. Create String value:

Bitness

3. Set the String value for Bitness to:

x64
This registry edit is an essential element necessary to resolve the click to run problem that prevents Outlook 2013 from being set as the default mail client. Although it worked with Adobe Acrobat, it will not completely resolve the problem for some third party applications like Kerio Outlook Connecter where the software developer has a web site that includes extra steps necessary for a full resolution for the Kerio product. The Kerio web site includes this registry edit in the context of resolving the Office 365 problem. However, the registry edit works with Office 2013 desktop as well. A similar register edit could likely be made for 32 bit versions but the registry path would not include Wow6432Node. I do not have a 32 bit machine and cannot test a 32 bit solution.
0
 
SIT-SRAuthor Commented:
Thank you for getting back to me. I will have to wait until tonight to remote in when I won't be interupting the Receptionist. I'll let you know how it works out.
0
 
SIT-SRAuthor Commented:
See attached Word Document with picture of the Registry. I followed instructions.
However it didn't change anything.

Any more suggestions are welcome.
Verification-and-New-Key.docx
0
 
ashcreekee1Commented:
I too have the same issue.
I have been rearching, and tried the same fix - it did not resolve the issue.
Running windows 7 pro 64, with Office 2013 Home and Business 64.
Please let me know if anyone has any further updates on this issue.
0
 
SIT-SRAuthor Commented:
I finally had to uninstall Office 64 bit and reinstall as Office 32 bit.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now