Kb:office 365 MX validation error &owa open after HTTP 404

Fault Descriptionthe MX record for Exchange online was not found

After you add a domain name, you have been waiting for a week and still cannot verify the MX record. However, the result of the Nslookup query is that the DNS record is already in effect.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/57/1E/wKioL1SSQvWiHfMzAAPjeMlewXs342.jpg "/>

when you sign in to Outlook Web app, white screen (HTTP 404)

When you click on the Outlook Calendar person above, Chrome jumps directly to a white screen page, ie is displayed as HTTP 404. However, when you log in using the [email protected] format, you can access the Outlook Web App smoothly.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/57/21/wKiom1SSQlPy2rKgAAHJdp9eWQ8738.jpg "/>

Diagnostic Methods

1. Open cmd, run the command, and replace the domain.name with the domain name that is bound to Office 365.

C:\USERS\ADMINISTRATOR>NSLOOKUP-QT=MX domain.name 202.96.134.133 server: ns.szptt.net.cnAddress: 202.96.134.133 non-authoritative answer: domain.name MX preference = 5, mail exchanger = domain-name.mail.protection.outlook.com

The query to the MX record does exist, so it should not be a DNS resolution issue.

1. Open PowerShell in Administrator mode, enter the following command (Set-executionpolicy unrestricted), enter Y and return to change PS execution policy to not strict

PS c:\windows\system32> set-executionpolicy Unrestricted execution policy change execution policy prevents you from executing untrusted scripts. Changing the execution policy may cause you to face the security risks described in the About_execution_policies Help topic. Do you want to change the execution policy? [Y] is (y) [n] No (n) [s] Hangs (s) [?] Help (default = "Y"): Y

2. Enter the following command, and then enter the Administrator account for Office 365 to temporarily save the credentials to the $livecred object

PS c:\windows\system32> $LiveCred = get-credential

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/57/1E/wKioL1SSQvXyOKv4AACd-E9j6Gw356.jpg "/>

3. Enter the following command to establish the session object

PS c:\windows\system32> $Session = new-pssession-configurationname Microsoft.exchange-connectionuri https:// ps.outlook.com/powershell/-credential $LiveCred-authentication Basic allowredirection

Warning: Your connection has been redirected to the following URI: "https://pod11111psh.outlook.com/powershell-liveid?PSVersion=2.0

4. Import session (Import-pssession $Session)

PS c:\users\l130115> import-pssession $Session Warning: The agent creation of the following command has been skipped: "Tabexpansion" because this overwrites the existing local command. If you want to overwrite an existing local command, use the Allowclobber parameter. Warning: Some imported command names contain unapproved verbs that may cause the command name to be difficult to find. Use the Verbose parameter for more information, or type Get-verb to view the list of approved verbs. Moduletype Name exportedcommands------------------------------Script tmp_1 e1131e9-1bdd-198a ... {get-hostedoutboundspamfilterpolicy, get-irmconfiguration, New-mailuser,...

5. Enter the following command to see if the user OWA is enabled and observe that all user OWA is enabled (the value of owaenabled is true)

PS c:\users\l130115> Get-casmailbox | Select name,owaenabled

Processing Methods

1. Login https://portal.office.com/admin/default.aspx

2. Click Service Request

3. Click on the + sign to submit a case to Microsoft

root Cause

Another eagle classmate of the company linked the domain name to the century-connected Office 365 at the time of the test, but after the test was finished, it did not release the domain name and the Internet of the century-connected Office 365 bindings. This caused the domain name supply conflict.

Workaround

Use the original test account (even if the subscription expires can be logged in, if not login can click on the bottom of the can ' t Access your accounts? Contact Office 365 Engineer for processing) The domain name binding was removed after landing Office 365. And the issue is resolved after the Microsoft daemon runs a full copy to re-associate the domain name.

something

Have a problem, find manufacturers!

This article is from the "Microsoft Technology Road" blog, make sure to keep this source http://autodiscover.blog.51cto.com/5759621/1591289

Kb:office 365 MX validation error &owa open after HTTP 404