38 C
Dubai
Wednesday, August 17, 2022
spot_img

Outlook Cannot Logon System resources are critically Low

Microsoft Outlook 2016.

  • Outlook Cannot Log on. Verify you are connected to the network and are using the proper server and mailbox name . The Microsoft Exchange information service in your profile is missing required information.Modify your profile to ensure that you are using the correct Microsoft Exchange Information Service.

image

System Resources are Critically Low. Close Some Windows.

image

 

Why its happening all of a Sudden ?

While doing a Auto discover Test. Just Confirm its going to the Right Place .

Ideally most of the cases it should going to autodiscover.careexchange.in

But autodiscover tests the the root domain first .As Root domain listens on HTTPS by mistake and responds to autodiscover abnormally. It downloads the wrong XML file by mistake.

Its going to  https://www.azure365pro.com:443/Autodiscover/Autodiscover.xml

and downloading the wrong XML file

https://testconnectivity.microsoft.com/

image

Location –

C:\Users\sathesh\appdata\local\Microsoft\outlook\16

image

Now . Stop the domain from listening to HTTPS 443.

or delete the A record of domain.com and keep www.careexchange.in only.

Wrong / Abnormal XML File example –

<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
 <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
 <User>
 <DisplayName>sath@careexchange.in</DisplayName>
 </User>
 <Account>
 <AccountType>email</AccountType>
 <Action>settings</Action>
 <Protocol>
 <Type>IMAP</Type>
 <Server>careexchange.in</Server>
 <Port>993</Port>
 <DomainRequired>off</DomainRequired>
 <SPA>off</SPA>
 <SSL>on</SSL>
 <AuthRequired>on</AuthRequired>
 <LoginName>sath@careexchange.in</LoginName>
 </Protocol>
 <Protocol>
 <Type>SMTP</Type>
 <Server>careexchange.in</Server>
 <Port>465</Port>
 <DomainRequired>off</DomainRequired>
 <SPA>off</SPA>
 <SSL>on</SSL>
 <AuthRequired>on</AuthRequired>
 <LoginName>sath@careexchange.in</LoginName>
 </Protocol>
 </Account>
 </Response>
</Autodiscover>

Working XML File of Office 365 –

<?xml version="1.0" encoding="utf-8"?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
 <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
 <User>
 <DisplayName>Sath | CareExchange</DisplayName>
 <LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=a454655555980555598a83a-sathesh_758</LegacyDN>
 <AutoDiscoverSMTPAddress>sath@Careexchange.in</AutoDiscoverSMTPAddress>
 <DeploymentId>b787ddaf-ec3e-4ccf-965750e3849b</DeploymentId>
 </User>
 <Account>
 <AccountType>email</AccountType>
 <Action>settings</Action>
 <MicrosoftOnline>True</MicrosoftOnline>
 <ConsumerMailbox>False</ConsumerMailbox>
 <Protocol Type="mapiHttp" Version="1">
 <MailStore>
 <ExternalUrl>https://outlook.office365.com/mapi/emsmdb/?MailboxId=f26e24bc-5555-4544-0047-af993fbcbd43@careexchange.in</ExternalUrl>
 </MailStore>
 <AddressBook>
 <ExternalUrl>https://outlook.office365.com/mapi/nspi/?MailboxId=f26e24bc-5555-4544-0047-af993fbcbd43@careexchange.in</ExternalUrl>
 </AddressBook>
 </Protocol>
 <Protocol>
 <Type>WEB</Type>
 <Internal>
 <OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
 <Protocol>
 <Type>EXCH</Type>
 <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
 </Protocol>
 </Internal>
 <External>
 <OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/Careexchange.in/</OWAUrl>
 <Protocol>
 <Type>EXPR</Type>
 <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
 </Protocol>
 </External>
 </Protocol>
 <Protocol>
 <Type>EXHTTP</Type>
 <Server>outlook.office365.com</Server>
 <SSL>On</SSL>
 <AuthPackage>Basic</AuthPackage>
 <ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
 <EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
 <EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
 <SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
 <EcpUrl>https://outlook.office365.com/owa/</EcpUrl>
 <EcpUrl-um>?path=/options/callanswering</EcpUrl-um>
 <EcpUrl-aggr>?path=/options/connectedaccounts</EcpUrl-aggr>
 <EcpUrl-mt>options/ecp/PersonalSettings/DeliveryReport.aspx?rfr=olk&amp;exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;&amp;realm=Careexchange.in</EcpUrl-mt>
 <EcpUrl-ret>?path=/options/retentionpolicies</EcpUrl-ret>
 <EcpUrl-sms>?path=/options/textmessaging</EcpUrl-sms>
 <EcpUrl-publish>?path=/options/calendarpublishing/id/&lt;FldID&gt;</EcpUrl-publish>
 <EcpUrl-photo>?path=/options/myaccount/action/photo</EcpUrl-photo>
 <EcpUrl-connect>?path=/options/socialnetworks&amp;ignore1=&lt;Action&gt;&amp;ignore2=&lt;Provider&gt;</EcpUrl-connect>
 <EcpUrl-tm>options/ecp/?rfr=olk&amp;ftr=TeamMailbox&amp;exsvurl=1&amp;realm=Careexchange.in</EcpUrl-tm>
 <EcpUrl-tmCreating>options/ecp/?rfr=olk&amp;ftr=TeamMailboxCreating&amp;SPUrl=&lt;SPUrl&gt;&amp;Title=&lt;Title&gt;&amp;SPTMAppUrl=&lt;SPTMAppUrl&gt;&amp;exsvurl=1&amp;realm=Careexchange.in</EcpUrl-tmCreating>
 <EcpUrl-tmEditing>options/ecp/?rfr=olk&amp;ftr=TeamMailboxEditing&amp;Id=&lt;Id&gt;&amp;exsvurl=1&amp;realm=Careexchange.in</EcpUrl-tmEditing>
 <EcpUrl-extinstall>?path=/options/manageapps</EcpUrl-extinstall>
 <OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
 <UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
 <OABUrl>https://outlook.office365.com/OAB/e238e51d-463a-4dab-8387-85555395925/</OABUrl>
 <ServerExclusiveConnect>On</ServerExclusiveConnect>
 </Protocol>
 </Account>
 </Response>
</Autodiscover>

Quick Fix Available _

  1. Point Domain.com to a dummy ip or Point to Exchange Server itself.
  2. Point domain.com to loadbalancer or webserver and redirect to www.domain.com . So that it won’t respond with dummy autodiscover files  with wrong settings.
  3. Change MX records from local to remote (Doesn’t solve all the time.)

Make sure it doesn’t respond like below.

Satheshwaran Manoharan
Satheshwaran Manoharanhttps://www.azure365pro.com
Specialized in Microsoft Azure - Office 365 / Microsoft Exchange; conducted numerous projects worldwide in designing, supporting, and implementing messaging and virtualization infrastructure for medium-sized and large enterprises. Further, I am a Cloud Architect and Technical Advisor for various start-ups.

Related Articles

3 COMMENTS

LEAVE A REPLY

Please enter your comment!
Please enter your name here