{"id":444,"date":"2012-09-19T14:13:44","date_gmt":"2012-09-19T19:13:44","guid":{"rendered":"http:\/\/www.exchangedefender.com\/blog\/2012\/09\/action-cannot-be-completed-name-cannot-be-resolved\/"},"modified":"2012-09-19T14:13:44","modified_gmt":"2012-09-19T19:13:44","slug":"action-cannot-be-completed-name-cannot-be-resolved","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2012\/09\/action-cannot-be-completed-name-cannot-be-resolved\/","title":{"rendered":"Action Cannot Be Completed. Name Cannot Be Resolved."},"content":{"rendered":"<p>Every week we get at least 5-10 support tickets created by partners who receive the error \u201cAction cannot be completed. Name cannot be resolved.\u201d A lot of the times partners may be setting up an additional mailbox for a user, but sometimes it can happen when resetting up the users profile. In this blog I hope to provide some insight on why this occurs.  <\/p>\n<p>First and foremost, if you do not receive a credential window prompt then you either have a credential conflict or an invalid outlook configuration. I would like to make it very clear\u2026<em>you should always, <u>always<\/u> see the credential window.<\/em>  <\/p>\n<p>When you hit \u201cCheck Name\u201d, Outlook does a user lookup to resolve the input username to a mailbox. Outlook will first attempt to use the users local credentials to authenticate, then any cached credentials (Windows Credential Manager), finally, if no credential entries authenticate then Outlook will prompt the user for credentials.  <\/p>\n<p><a href=\"http:\/\/www.exchangedefender.com\/blog\/media\/Action-Cannot-Be-Completed.-Name-Cannot_D2B0\/clip_image002.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto; padding-top: 0px\" title=\"clip_image002\" border=\"0\" alt=\"clip_image002\" src=\"http:\/\/www.exchangedefender.com\/blog\/media\/Action-Cannot-Be-Completed.-Name-Cannot_D2B0\/clip_image002_thumb.jpg\" width=\"551\" height=\"140\"><\/a>  <\/p>\n<p>If a user does not receive the credential prompt and receives the error \u201cAction cannot be completed\u201d a quick fix is to go to More Settings, Security, and then enable the checkbox to \u201cAlways prompt for logon credentials.\u201d  <\/p>\n<p>When user\u2019s select \u201cRemember my credentials\u201d Outlook then creates a cached credential for windows in the credential manager  <\/p>\n<p><a href=\"http:\/\/www.exchangedefender.com\/blog\/media\/Action-Cannot-Be-Completed.-Name-Cannot_D2B0\/clip_image003.png\"><img loading=\"lazy\" decoding=\"async\" style=\"background-image: none; border-right-width: 0px; padding-left: 0px; padding-right: 0px; display: block; float: none; border-top-width: 0px; border-bottom-width: 0px; margin-left: auto; border-left-width: 0px; margin-right: auto; padding-top: 0px\" title=\"clip_image003\" border=\"0\" alt=\"clip_image003\" src=\"http:\/\/www.exchangedefender.com\/blog\/media\/Action-Cannot-Be-Completed.-Name-Cannot_D2B0\/clip_image003_thumb.png\" width=\"572\" height=\"119\"><\/a>  <\/p>\n<p>Normally, this works as expected.. the next time Outlook launches it will try the cached credential which would authenticate.  <\/p>\n<p>But imagine if you were trying to add a second mailbox to the users profile (Let\u2019s say the CEO has two mailboxes for \u2018two different companies\u2019) .. how is Outlook to know that the cached credential for <a href=\"mailto:servertest@louie.exchangedefender.com\">servertest@louie.exchangedefender.com<\/a> on \u201ccas.louie.exchangedefender.com\u201d isn\u2019t for the second mailbox (Let\u2019s say <a href=\"mailto:servertest2@louie.exchangedefender.com\">servertest2@louie.exchangedefender.com<\/a>)? The answer is..Outlook won\u2019t be able to tell the difference.. The server will respond to Outlook with the message \u201cAccess denied\u201d because the cached credentials for mailbox1 does not have permission to access mailbox2 (Think of it as trying to access mailbox2 via OWA, but using the credentials for mailbox1) and then receives the error \u201cAction cannot be completed. Name cannot be resolved\u201d when trying to resolve the mailbox name for mailbox2..the key point is that this failure will instantly occur and there will be no prompt for the user to provide credentials because the error \u201cAccess denied\u201d mean \u201cYou have a valid account here, but it does not have access to this resource\u201d.  <\/p>\n<p>Now let us imagine the inverse where a user gets prompted for credentials every time no matter how many times they select \u201cRemember my credentials\u201d or if they follow our help article \u201c<a href=\"http:\/\/www.exchangedefender.com\/help\/2010\/07\/27\/my-windows-os-wont-hold-the-outlook-authentication-info\/\">My Windows OS won\u2019t hold the Outlook authentication info!<\/a>\u201d and manually add \u201c*.exchangedefender.com\u201d to the credential manager.. This is because Outlook is passing off a valid \u201cAccount\u201d that has access to the resource (Mailbox), however, the credentials being passed off are incorrect. If Outlook tries to authenticate with invalid credentials the server will respond back with \u201cInvalid credentials\u201d..notice how this isn\u2019t the same error as \u201cAccess Denied\u201d which is why Outlook will then prompt the user for credentials. To solve this we tell users to delete all references to any exchangedefender servers in credential manager and then manually add the credentials (following the above blog post) and then adding *.exchangedefender.com to the \u201cLocal Intranet\u201d zone in Internet Explorer. This should allow Outlook to trust our servers to hand off the credentials.  <\/p>\n<p>Finally, the last common scenario for the two failures (either no credential prompt or reoccurring credential prompts) is if the local users login name matches a username on the server. Remember, Outlook will first try the local logged on users credentials. Now imagine if my local login name was <a href=\"mailto:servertest@louie.exchangedefender.com\">servertest@louie.exchangedefender.com<\/a>&#8230; then any time I attempted to add an Outlook profile I would either instantly authenticate or I would always get the credential prompt. Can you guess why? Its because either the local users credentials (Either their local computer user name or an active directory account) match the servers credentials.  <\/p>\n<blockquote>\n<p><strong>Active Directory:<\/strong>  <\/p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp; \u00b7 Username: <a href=\"mailto:servertest@louie.exchangedefender.com\">servertest@louie.exchangedefender.com<\/a>  <\/p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp; \u00b7 NT Username: servertest  <\/p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp; \u00b7 Password: 123456  <\/p>\n<p><strong>Exchange:<\/strong>  <\/p>\n<p>&nbsp;&nbsp;&nbsp; \u00b7 Username: <a href=\"mailto:servertest@louie.exchangedefender.com\">servertest@louie.exchangedefender.com<\/a>  <\/p>\n<p>&nbsp;&nbsp;&nbsp; \u00b7 NT Username: servertest  <\/p>\n<p>&nbsp;&nbsp;&nbsp; \u00b7 Password: abcdefg <\/p>\n<\/blockquote>\n<p>In the above, the server would always prompt for login credentials because the credentials are mismatched. But let\u2019s think back to our first example of adding the users second mailbox to their profile and imagine we had the same credential conflict as above, except the exchange user is servertest2&#8230; Outlook would again instantly fail because the local login credentials does match an exchange account, but does not have access to the resource (The second mailbox, servertest2).  <\/p>\n<p>In the case of opening multiple mailboxes in one profile the only way to get Outlook to not prompt for credentials for each mailbox is to grant full access permission from one user to another\u2026so if you cached the credentials for one mailbox (ie., servertest) and then granted servertest full access credentials to servertest2 (second mailbox) then outlook wouldn\u2019t receive the \u201cAccess Denied\u201d error when trying to access servertest2 with the cached credentials of servertest.<\/p>\n<p>Travis Sheldon<br \/>VP, Network Operations, ExchangeDefender<br \/>(877) 546-0316 x757<br \/>travis@ownwebnow.com  <\/p>\n","protected":false},"excerpt":{"rendered":"<p> [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-444","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/444","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=444"}],"version-history":[{"count":0,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/444\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}