Home/ Questions/Q 8988617
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T22:02:35+00:00

I am following the Microsoft tutorial for creating my first sharepoint 2013 app. (http://msdn.microsoft.com/en-us/library/fp142379.aspx

  • 0

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.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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)

    • 0