Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

ActiveSync and OWA issues with Exchange 2010

$
0
0

I am having problems with one of the sites that I manage. I cannot get our iPads and iPhones to sync with our Exchange 2010 server. This is a migration from 2003 SBS.

 

OWA sort of works, users are able to access it but if you try to delete a message or move a message, I receive the following error;

A server configuration problem is preventing access to your account. If the problem continues, contact your helpdesk.

The entire error report is listed below:

A server configuration problem is preventing access to your account. If the problem continues, contact your helpdesk.

 

When I look at the server event log, this shows up;

Outlook Web App couldn't connect Exchange Web Services due to a configuration error. Response code = "503".

 

Activesync looks like it's running properly but I can't sync the iPads or iPhones to it. The error that I get on the iPad is;

Cannot Get Mail.

The connection to the server failed

 

I have just regenerated the certificate through RapidSSL today.

New-ExchangeCertificate -FriendlyName 'SERVER2 Mail Certificate 2012-1001' -GenerateRequest -PrivateKeyExportable $true -KeySize '2048' -SubjectName 'C=CA,S="Prov",L="City",O="Our Company Name",OU="IT",CN=mail.ourdomain.ca' -DomainName 'server2.intdomain.local','mail.ourdomain.ca','ourdomain.ca','autodiscover.intdomain.local','autodiscover.ourdomain.ca','anywhere.ourdomain.ca','intdomain.local','server2' -Server 'SERVER2'

 

I assigned IIS and SMTP services to the certificate but after I did that, both IMAP and POP show up in the list too. I tried to remove them but they keep showing up

 

When I run the Exchange Connectivity Analyzer shows the following errors;

Validating the certificate name.

Host name autodiscover.ourdomain.ca doesn't match any name found on the server certificate CN=mail. ourdomain.ca, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)12, OU=GT80191907, SERIALNUMBER=Al/Ha8Woui36IBL4iNk4HfZzoSPLpGRX.

 

ExRCA failed to contact the Autodiscover service using the DNS SRV redirect method.

Attempting to locate SRV record _autodiscover._tcp.ourdomain.ca in DNS.

The Autodiscover SRV record wasn't found in DNS.

 

I have sent an email to our DNS provider to ask them to put in an SRV record with the following;

Service: _autodiscover

Protocol: _tcp

Port: 443

Weight: 0

Priority: 0

TTL: 3600

Target: mail.ourdomain.ca

 

It was also suggested that we reapply Exhcnage 2010 SP2 but when I try to run that, it fails with the following error;

 

Summary: 8 item(s). 4 succeeded, 1 failed.

Elapsed time: 01:32:29

Language Files

Completed

Elapsed Time: 00:05:17

Restoring services

Completed

Elapsed Time: 00:00:01

Languages

Completed

Elapsed Time: 00:00:30

Hub Transport Role

Completed

Elapsed Time: 01:00:15

Client Access Role

Failed

Error:

The following error was generated when "$error.Clear();

          $InternalOwaUrl="https://" + $RoleFqdnOrName + "/owa";

          new-OwaVirtualDirectory -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;

        " was run: "The virtual directory 'owa' already exists under 'SERVER2.intdomain.local/Default Web Site'.

Parameter name: VirtualDirectoryName".

 

The virtual directory 'owa' already exists under 'SERVER2.intdomain.local/Default Web Site'.

Parameter name: VirtualDirectoryName

Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.247.1&e=ms.exch.err.Ex88D115&l=0&cl=cp

 

Elapsed Time: 00:26:24

Mailbox Role

Cancelled

Management Tools

Cancelled

Finalizing Setup

Cancelled

 

I thought about blowing those directories away and then rerunning the SP2 but with all this happening, I figured I better wait until I get more advice on the issue.

 


Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>