I am getting an error "Either there is no default email client or the current mail client cannot fulfill the messaging request" and "The Microsoft Exchange MAPI subsystem is not installed." I have installed the ExchangeMAPICdo and have also tried repairing the outlook installation after deleting the registry outlook key(based on a technet suggestion that the key may have been corrupted). I am unable to proceed with the installation. I am using Outlook 2013 Professional. Please help.
I solved this by deleting the registry entry for Outlook, installing the MAPI subsystem and CRM Email router in that order. Once the email router is installed, you may run Outlook repair to restore the deleted keys.
Related
I am trying to read and send email using Microsoft exchange webservice API. I tried to run this code for Outlook version 2010 and 2016 in my VMs its showing
The request was aborted: Could not create SSL/TLS secure channel
where as same code for office 365 its working fine. I even tried manual accessing outlook mails with URL and credentials and I am able to do it but through code.
Hi, we are receiving attached error also, it seems to be relates with your issue. We have started receiving this today by the morning. Could it be like a Windows update or something? We are still investigating this issue.
I’ll try upgrading the .net environment and replacing the web.config currently 4.5.2 with the 4.6.1
EDIT:
Yes, we have solved that issue. We used IIS Crypto 2.0 software to revert all tls settings to it's server defaults on Day-1. Then don't forget to restart the server of course. I think that Windows updates messed up with the TLS settings on Windows servers. Hope this will fix your issue.
I just Use AJAX Library from WebDAV library to start WebDAV in browsers other than IE with your information from
http://www.webdavsystem.com/ajax/programming/opening_ms_office_docs/
And This is result:
Microsoft Office 2013
IE:Protocol ext ==> ok
Chrome:Protocol ext ==>ok
FF:Protocol ext ==> ok
Microsoft Office 2010
IE:ActiveX ==> ok
Chrome:Plugin2 ==>fault
FF:Add-on ==>ok
Microsoft Office 2007 and earlier
IE:ActiveX ==>ok
Chrome:Java applet2 ==> fault
FF:Java applet ==>ok
I can not run editing document when run in chrome (version 45) from Microsoft Office 2010, Microsoft Office 2007 and earlier.
please support us to run on Chrome.
I have attached my demo, please help me solve this problem:
http://www.mediafire.com/download/6kv2d8zcq47w9fj/TestWebDavHtml.rar
Thank you very much!
First of all make sure you are using the IT Hit WebDAV Ajax Library v5 or later.
Regarding MS Office 2010:
Make sure you have Microsoft Office 2010 SP2 or later installed. Also verify that you have all Windows updates installed. WebDAV components are updated rapidly and may fix some issues.
Regrding MS Office 2007:
In general MS Office 2007 and earlier are not supported any more by Microsoft. However you still can open documents using it:
Make sure you have all MS Office and Windows updates installed.
Make sure you have a latest WebDAV Ajax Library v5 or later, client protocol application installed and web browser extension enabled.
We have Window XP where Outlook for CRM-11 is installed.
I developed a Outlook Addin and installed on this system.
Setup could not be installed due to "Microsoft.IdentityModel" is not found as it does not support in XP.
Then how Outlook(With CRM) is installed in this system??
Do we have any alternate solution for this to be work in XP?
Any help will will be greatly appreciated.
Thanks in advance.
The outlook client doesn't require Windows Identity Foundation to run but any ISV development against the Organization Service does i.e your Add-in.
There's nothing stopping you from installing Microsoft.IdentityModel.dll to the GAC on the client XP machines but this is an unsupported solution both in terms of the desktop build and CRM 2011. The alternative is to rewrite your add-in to use the WSDL based CRM service instead or upgrade the client OS! I appreciate the latter is unlikely hence your question.
I am following the Microsoft tutorial for creating my first sharepoint 2013 app.
(http://msdn.microsoft.com/en-us/library/fp142379.aspx )
I have installed on a windows 2008 R2 Server Sharepoint 2013 RTM, done all the farm config stuff RTM, and installed all of Visual Studio 2012 ultimate and update 1 and restarted the server.
I have also followed the instructions for "How to: Set up an on-premises development environment for apps for SharePoint" which is at http://msdn.microsoft.com/en-us/library/fp179923.aspx (I have to do this as our dev environment has no internet access)
I have got to the point where running Visual Studio as an Administrator I have named it and chosen "sharepoint-hosted" and validated the server and clicked finish (Step 5).
Instead of getting the next step where I open the AppManifest.xml file I get a message saying "An error occurred whilst trying to load some required components, Please ensure the following prerequisite components are installed. Microsoft Web Developer Tools and Microsoft Exchange Web Services"
I have checked VS setup and web developer tools is definetely installed (the only option I have would be to remove it)
Any help would be greatly appreciated. I know Im a noob here (this is my first post) but I have googled this and searched stack exchange and found nothing that helps me.
Got it after a few trial and errors
With an offline install you have to download the Exchange Web Services component. I had downloaded "EwsManageApi" and installed that.
As the error message specifically refers to Exchange Web services, I looked at other versions and tried the older 1.1 and the 32 bit version, but they didn't work either, ** until ** I relised in my haste that I installed using the default settings (which is for the current user) and not for all users of the machine.
So installing EwsManagedApi32 for all users on a 64 bit server does the trick (for me)
I tried reinstalling the EWS Managed API for All Users, but that didn't solve it for me. In the end the solution was simple:
Just uninstall BOTH the EWS Managed API and the Microsoft Office Developer Tools for Visual Studio 2012. After that reinstall ONLY the Office Developer Tools. This time the Web Platform Installer will ensure the correct EWS Managed API is also installed.
I also wrote a small blog about this problem:
https://leonzandman.com/2013/02/07/prerequisite-components-error-when-creating-a-visual-studio-2012-sharepoint-2013-app-project/
Answer for the year of 2014:
Install Microsoft Exchange Web Services Managed API 2.1 (the latest version I can find at this time).
I need to have all the documents in Sharepoint opens in client applications. I set the appropriate setting in the admin page, but it doesn't work for all users. Also I tried to set this in library settings, result was similar.
I think the reason may be on a client side, but I haven't found it. All users with this trouble have IE7 and MS Office 2003.
Does anybody know, how i could handle this?
I would think that the server is checking if the user has Office installed locally. This is achieved by trying to activate an object from the ActiveX control installed by Office locally. You can find this DLL under c:\program files\microsoft office\office12[14]\OWSSUPP.dll. If this dll fails to load, for instance, missing or not registered probably, SharePoint assumes that no local client software is installed. You can register the DLL or run repair on the Office installation, that should fix the problem