I am trying to organize work with meetings (appointments) through a site on asp.net mvc 5 using EWS Managed api 2. It is necessary that the user can create a meeting on his own behalf via the web. In VS, when debugging with UseDefaultCredentials = true executes and creates. After deploying to ISS:

"No mailbox with such guid" or "The response received from the service did not contain valid XML"

With specific Credentials = new WebCredentials("usename", "pass", "domain") on the ISS works, but then all the events will be on behalf of one person. winsows authorization on the site is enabled. local site, all domain users. either somehow substitute appointment.Organizer , if you leave specific Credentials .

    2 answers 2

    I encountered the same problem as in the following forum: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/thread/e54c217f-28ff-4626-8ce8-a1242081f4d1/

    (Essentially, additional characters were previously set aside and added to the returned XML address, causing the error above.)

    If any assistance — deleting and re-creating the EWS virtual directory did not alleviate the problem.

    I believe that perhaps our F5 load balancer or some intermediate device inserts additional characters at the beginning or end of XML.

    When I changed my code to: service.Url = new Uri ("https: //192.168.xx/EWS/Exchange.asmx");

    (Essentially, using the internal IP address of our exchange server), the request worked just fine. So something outside of sharing is a distortion of XML.

    • corrected the link. "No mailbox with such guid" has not gone anywhere. - Ivan Fateev pm

    No mailbox with such guid

    This error is usually caused by an unlicensed mailbox account. Make sure all migration mailboxes are licensed in Office 365.

    If a mailbox account has been assigned a license, and the error persists, it is usually caused by a value other than Null in the msExchMailboxGuid attribute of the mailbox account.

    By default, when you synchronize a user from the local environment, in which there is a mailbox assigned to him, the value of the msExchMailboxGuid attribute will also be synchronized. Assigning an Office 365 license in this case will not lead to the creation of a mailbox.

    Follow these steps to confirm this problem in Office 365:

    Log in to the Office 365 tenant office with a global administrator account and go to the admin page. On the Active Users panel, find the email address of the affected user. Click on the username and look in the Mail settings. The message associated with the mailbox will be as follows: “The internal mailbox of this user was not transferred to Exchange Online. An Exchange Online mailbox will be available after the migration is complete. ”

    • uh I have exchange 2016. and the console application with ews works on the server as well. does not work via web with default credentials - Ivan Fateev