Sign in
Microsoft.com
 
Microsoft
 
 
 

none
Unable to logon using custom domain

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    We are using email service on hotmail through custom domain ( i.e nautankifilms.com ). From last 4-5 days one the user is unable to login using webmail/Mobile. Here is the error:

    Email id : asheema#nautankifilms.com

    Please help us resolve the issue ASAP.

    Rgds,

    Nishant


    Request
    Url: https://outlook.live.com:444/owa/
    User host address: 25.164.147.26
    OWA version: 15.1.331.20

    Exception
    Exception type: Microsoft.Exchange.Data.Directory.CannotResolveTenantNameException
    Exception message: Failed to resolve tenant name from accepted domain 'nautankifilms.com'.

    Call stack
    Microsoft.Exchange.Data.Directory.ADAccountPartitionLocator.GetPartitionIdByAcceptedDomainName(String acceptedDomainName, String& tenantContainerCN, Guid& externalDirectoryOrganizationId, Boolean directGlsDbQuery)
    Microsoft.Exchange.Data.Directory.OrganizationId.FromAcceptedDomain(String acceptedDomain)
    Microsoft.Exchange.Data.Directory.ADSessionSettingsFactory.FromBusinessTenantAcceptedDomain(String domain)
    Microsoft.Exchange.Data.Directory.Diagnostics.ADScenarioLog.InvokeWithAPILog[T](DateTime whenUTC, String name, Guid activityId, String implementation, String caller, Func`1 action, Func`1 getDcFunc)
    Microsoft.Exchange.Data.Directory.ADSessionSettings.InvokeWithAPILogging[T](Func`1 action, String memberName)
    Microsoft.Exchange.Clients.Owa.Core.Utilities.CreateScopedADSessionSettings(String domain)
    Microsoft.Exchange.Clients.Owa.Core.OwaClientSecurityContextIdentity.InternalCreateExchangePrincipal()
    Microsoft.Exchange.Clients.Owa.Core.OwaIdentity.CreateExchangePrincipal()
    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.GetExchangePrincipal(OwaContext owaContext, ExchangePrincipal& exchangePrincipal)
    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.AcquireAndPreprocessUserContext(OwaContext owaContext, HttpRequest request)
    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
    Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object sender, EventArgs e)
    Microsoft.Exchange.Clients.Owa.Core.OwaModule.OnPostAuthorizeRequest(Object sender, EventArgs e)
    System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    Wednesday, December 2, 2015 6:52 AM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Have they tried deleting and then adding the account back to the device? If not, this may just be the continued undocumented deprecation of functionality from the Windows Live Custom Domains. I've had the same thing happen to my domain over the last couple of weeks as it was "upgraded" and the only solution I've found is IMAP or POP3 access since the exchange activesync does not work. 

    Also, make sure that the e-mail address you show above is NOT the e-mail address they are using, because above it shows asheema#nautankifilms.com instead of the correct e-mail which is asheema@nautankifilms.com .

    HTH

    -Scottker

    Saturday, February 11, 2017 7:56 PM
    |