We have an Outlook Module Manifest that worked two weeks ago against Office 365 (never against Exchange 2013).
When we tried to remove it and add it again today, we got the following error message:
Value cannot be null. Parameter name: recipient
We then tried to add the Outlook Module Manifest sample from here, but that throws the same error message.
Any idea what we may be missing? Or did Microsoft change their Office 365 infrastructure, breaking their own sample?
This error message may just want to tell you that your account does not have an Exchange Online license assigned right now. The account used to upload an extension for the organization requires a valid Exchange Online license.
Related
We have a VSTO add-in for Outlook, that supports booking of resources managed by our cloud system.
In addition we support resources that are also available in Exchange as rooms to support integration with other systems.
When we perform a booking of such a room, the add-in adds the corresponding Exchange email address for the room to recipients, so it will also be booked in Exchange.
This used to work fine, but now we have received a report from a customer that they can no longer create bookings for resources with Exchange integration. The error they receive is completely unhelpful:
System.ArgumentException: Der gik desværre noget galt. Du kan prøve igen.
ved Microsoft.Office.Interop.Outlook._AppointmentItem.Save()
(in English: "Something went wrong. You can try again")
This happens when add-in attempts to save the item after adding some custom properties. I think the error is triggered by the add-in adding the Exchange rooms to recipients, since it does not happen for resources without Exchange integration.
Here is the code we use to add recipients:
var rec = ...; // custom DTO with recipient info
string recipientInfo = string.IsNullOrEmpty(rec.Email)
? rec.OutlookName
: rec.Email;
var recRecip = appointment.Recipients.Add(recipientInfo);
recRecip.Type = rec.RecipientType;
if (Current.Settings.IsEnabled(FeatureFlag.ResolveAddedRecipients))
{
using (LogHelper.TimedTask($"resolving recipient [{rec}]", Log))
{
recRecip.Resolve();
}
}
I can see from the logs, that the room recipient has email address, so above code will add by email. Also, the feature flag to resolve recipients is enabled, so the code will call resolve afterwards.
What could be going wrong here?
EDIT: Their Outlook version is 16.0.0.5071.
If the problem is isolated to the user's computer, we always recommend our IT staff to share the O365 Outlook Diagnostics Tool which analyses the outlook install, data files, plugins, cache and performs checks to identify source of issues on client computers.
This issue is difficult to reproduce because it seems to happen intermittently.
I'm using Microsoft Dynamics 365. I'm generating emails using the default Email Message entity by populating the description with the required content.
The problem I'm having is that sometimes, after saving and closing the edit window, the spaces between some words seem to get removed. When I open the editor again I see there are lots of spaces missing through seemingly random parts of the email's body.
I know there are third party tools available for sending and generating emails using Dynamics or Azure but unfortunately in this particular case I'm unable to utilize them. The solution is restricted to functionality built into Dynamics 365.
Example email before save:
Hi {Contact(Full Name)},
Welcome to the team!
Example email after save:
Hi {Contact(Full Name)},
Welcome tothe team!
in my organization we have a mailbox that receives email from different sources (about 5) everyday, set to track all incoming emails in the CRM.
All the mails are correctly tracked on the CRM every day, except for one that always fails (same source, similar content every day).
If I send the exact same email from another address, the mail is correctly synchronized with the CRM, so I think it could be something related with Exchange.
This is the message I get if I open the mailbox record:
An unknown error occurred while receiving email through the mailbox "xxxxxx".
The owner of the associated email server profile xxxxx has been notified. The system will try to receive email again later.
Email Server Error Code: Exchange server returned UnknownIncomingEmailIntegrationError -2147220970 exception
Looking for this specific message didn't get me any result, while just searching the error code I found out it could be something related to plugins.
Unfortunately there is no plugin that fires on email creation, same for workflows and so on. By the way, sending the email from another address just works fine.
Has anyone ever had such a problem? Is there some place where I can find other logs and dig deeper in the problem?
Thanks in advance.
For anyone else experiencing this issue: I received the error code -2147218683, which is different, but it turns out this was due to the user in question not having the right security role. Gave the account sys admin and the error went away.
The Microsoft bot framework channel "Email" is not working. I tried to add different emails including Office 365, #outlook.com , #gmail.com, none of them working, The screen showing an error status "Unable to save email".
It seems this was working earlier. My email is accessible via email/password and office 365 enabled , but from bot framework email channel - its returning an error "Unable to save email". Could anyone please help on this.
Email channel can only be used with Office 365 accounts as described in the documentation here:
The Email channel currently works with Office 365 only. Other email
services are not currently supported.
So it will not work with #gmail.com accounts.
I checked again 2 minutes ago and from my side I also have the problem of getting Unable to save error during registration of the email (with an email that was previously working).
When having a look to the console of my navigator, I see that there is an internal server error (error 500) for POST https://dev.botframework.com/api/bots/myBotName/channels/email
=> I will log an issue on Github Bot framework's project
The hosting company that my employer uses upgraded to Exchange 2010 over the weekend. This caused a service we use that access a mailbox to break. The hosting company said our mailboxes were still 2007. When trying to access them now using the Exchange 2007 Webservice, I get the following error:
The Client Access server version doesn't match the Mailbox server version of the resource that was being accessed. To determine the correct URL to use to access the resource, use Autodiscover with the address of the resource.
I have done some Googling on this error, and have found some posts about using AutoDiscover to get around this. I tried the Microsoft Example I found here, but I am unclear as to what the output from the console is telling me or how I use it.
It looks like it tries hitting some URLs and then reports on what it found. I either have Exceptions, "The e-mail address cannot be found", or "Site mismatch"
Edit: I got the sample application to return some information. Now my question is, how do I translate what this output is into accessing the mailbox I need?
Here is a list of properties that is returned with their actual values omitted.
=? Trying 'Email#myDomain.com' at 'https://myDomain.net/Autodiscover/Autodiscover.xml'
User/DisplayName=
User/LegacyDN=
User/DeploymentId=
Account/AccountType=
Account/Action=
Account/Protocol/Type=
Account/Protocol/ASUrl=
Account/Protocol/DirectoryPort=
Account/Protocol/MdbDN=
Account/Protocol/OABUrl=
Account/Protocol/OOFUrl=
Account/Protocol/Port=
Account/Protocol/ReferralPort=
Account/Protocol/Server=
Account/Protocol/ServerDN=
Account/Protocol/ServerVersion=
Account/Protocol/UMUrl=
Account/Protocol/PublicFolderServer=
Account/Protocol/AD=
Account/Protocol/EwsUrl=
Account/Protocol/Type=
Account/Protocol/AuthPackage=
Account/Protocol/CertPincipalName=
Account/Protocol/DirectoryPort=
Account/Protocol/OABUrl=
Account/Protocol/Port=
Account/Protocol/ReferralPort=
Account/Protocol/Server=
Account/Protocol/SSL=
Account/Protocol/Type=
Account/Protocol/DirectoryPort=
Account/Protocol/Port=
Account/Protocol/ReferralPort=
Account/Protocol/External/OWAUrl[#AuthenticationMethod="Fba"]=
Account/Protocol/External/OWAUrl[#AuthenticationMethod="Fba"]=
Account/Protocol/Internal/OWAUrl[#AuthenticationMethod="Basic, Fba"]=
Account/Protocol/Internal/OWAUrl[#AuthenticationMethod="Basic, Fba"]=
Account/Protocol/Internal/OWAUrl[#AuthenticationMethod="Basic, Fba"]=
Account/Protocol/Internal/Protocol/Type=
Account/Protocol/Internal/Protocol/ASUrl=
Can someone point me in the right direction toward solving this problem?
Also, I do not have access to make any changes on the Exchange Server itself.
I found the answer with a bit more of googling. The URL being returned from the "Account/Protocol/EwsUrl=" property gave me the value I wanted to point my webservice at.
I had the same error:
The Client Access server version doesn't match the Mailbox server
version of the resource that was being accessed
..but the EwsUrl was correct
The server platform had been upgraded to 2013, but the target mailbox was still in 2007 mode.
The fix was to migrate the mailbox to 2013 and it started working again.
So it was an environmental rather than code fix.