Testing of Autodiscover for Exchange ActiveSync failed.

Hello Friends,
Attempting the Autodiscover and Exchange ActiveSync test (if requested). Testing of Autodiscover for Exchange ActiveSync failed.
Additional Details
Elapsed Time: 2573 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service couldn't be contacted successfully by any method.
Additional Details
Elapsed Time: 2573 ms.
Test Steps
Attempting to test potential Autodiscover URL https://domain.no/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Test Steps
Attempting to resolve the host name domain.no in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host domain.no to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Test Steps
Attempting to test potential Autodiscover URL https://autodiscover.domain.no/AutoDiscover/AutoDiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 1087 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.no in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 443 on host autodiscover.domain.no to ensure it's listening and open.
The port was opened successfully.
Additional Details
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 419 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.domain.no on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Validating the certificate name.
Certificate name validation failed.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl01_ctl02_ctl01_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
Attempting to contact the Autodiscover service using the HTTP redirect method.
The attempt to contact Autodiscover using the HTTP Redirect method failed.
Additional Details
Elapsed Time: 630 ms.
Test Steps
Attempting to resolve the host name autodiscover.domain.no in DNS.
The host name resolved successfully.
Additional Details
Testing TCP port 80 on host autodiscover.domain.no to ensure it's listening and open.
The port was opened successfully.
Additional Details
The Microsoft Connectivity Analyzer is checking the host autodiscover.domain.no for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.
Additional Details
Attempting to contact the Autodiscover service using the DNS SRV redirect method.
The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.
Additional Details
Elapsed Time: 195 ms.
Test Steps
Attempting to locate SRV record _autodiscover._tcp.domain.no in DNS.
The Autodiscover SRV record wasn't found in DNS.
<label for="testSelectWizard_ctl12_ctl06_ctl00_ctl03_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details

Hi,
Please type the url below in IE and access it, see if there is certificate error.
https://autodiscover.domain.com/AutoDiscover/AutoDiscover.xml
Thanks,
Rebecca Tu
TechNet Community Support

Similar Messages

Certificate based authentication for Exchange ActiveSync in Windows 8.* Mail app

I have a Surface Pro and want to setup access to my company's Exchange server that accepts only Exchange ActiveSync certificate-based authentication.
I've installed server certificates to trusted pool and my certificate as personal.
Then I can connect thru Internet Explorer, but this is not comfortable to use.
I don't have a password because of security politics of our company. When I'm setting up this account on my Android phone I'm using any digit for password and it works perfectly.
Can someone help to setup Windows 8 metro-style Mail application? Does it supports this type of auth? When I'm trying to add account with type Outlook, entering server name, domain name, username, 1 as a password then I've got a message like "Can't
connect. Check your settings."
Is there any plans to implement this feature?

For what it's worth we have CBA working with Windows 8.1 Pro. In our case we have a MobileIron Sentry server acting as an ActiveSync reverse-proxy, so it verifies the client cert then uses Kerberos Constrained Delegation back to the Exchange CAS, however
it should work exactly the same to the Exchange server directly. I just used the CA to issue a User Certificate, exported the cert, private key and root CA cert, copied to the WinPro8.1 device and into the Personal Store. Configured the Mail app
to point at the ActiveSync gateway, Mail asked if I would like to allow it access the certificate (it chose it automatically) and mail synced down immediately...
So it definitely works with Windows Pro 8.1.

SnapManager For exchange - backup failing due to VSS snapshot timeout

Hello, We back up an exchagne 2010 DAG with SnapManager for exchange running on VMware. Recently we've been encountering issues where the backup will fail and entries similar to the following are logged in the system log.The volumes are LUNs mounted with SnapDrive. The issues are being caused by a VSS snapshot timeout. I am new to SnapManager and NetApp in general, i am the exchange admin that took over management of an existing environment. Does anyone have any ideas on how to resolve this? Thank You!  Log Name: System
Source: volsnap
Date: 8/6/2015 6:34:52 PM
Event ID: 8
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mailboxserver1.domain.local
Description:
The flush and hold writes operation on volume M: timed out while waiting for a release writes command.
Log Name: Application
Source: Navssprv
Date: 8/6/2015 6:34:56 PM
Event ID: 4118
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: mailboxserver1.domain.local
Description:
Data ONTAP VSS hardware provider has completed CommitSnapshots for SnapshotSetId {71615b93-aa37-479c-aec9-0565f3b7d013} in 14633 milliseconds. Since it takes more than 10 seconds, this can fail the current shadow copy.  Log Name: Application
Source: Navssprv
Date: 8/6/2015 6:34:56 PM
Event ID: 4110
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: mailboxserver1.domain.local
Description:
Data ONTAP VSS hardware provider's AbortSnapshot method is called [SnapshotSetId={71615b93-aa37-479c-aec9-0565f3b7d013}]. VSS has failed the current shadow copy session because the previous errors are not continuable.

Hi Mike,Welcome to the NetApp community! I suggest opening a case with NetApp support. Could you please provide the following information: Windows OS version, i.e. Windows 2008 R2 SP1 / Windows 2012SnapDrive version, i.e. SnapDrive 7.1.1SME version, i.e. SME 7.1Are the LUNs RDMs or mapped via iSCSI from inside the guest?Does the backup fail every time or sporadically?Is this an existing backup job that used to work fine before? If yes, did someone perform any changes (software installation, patch/hotfix installation due to MS patch day)Best regardsDirk

No option to change email display name for exchange activesync account

Hi there - I have searched several forums and for some reason haven't been able to find the answer to my question. I have a business email account hosted through google apps, and my email is set up on my iPhone as an active-exchange account. Emails sent from my phone display my official first name instead of the one that I go by and want to display. Emails sent from the gmail interface and outlook display my correct name.
I don't have an option in my account information screen to change this, and I haven't been able to find where this is stored.
Can someone please help? Thanks in advance.

You need to ask Apple to reset your security questions. To do this, click here and pick a method; if that page doesn't list one for your country or you're unable to call, fill out and submit this form.
(125083)

Nokia E71 - support for multiple mail for exchange...

Does the Nokia E71 supports multiple mail for exchange accounts?
Thanks,
Tim

Unfortunately only one Mail for Exchange (ActiveSync) account is supported on Nokia E71.

Mail for Exchange/Asha 311 - how to reset

I want to use Mail for Exchange to sync contact data with gmail, as I did on the Nokia 700 (think it was called Active Exchange there). I configured it similarly, and it seemed hung in a loop trying to connect. So I reset it, and then it wouldn't restart. It flashes a screen of data (too fast to read - something about Synchronization service shutdown ... Removing databases .. Application will restart when complete?). I tried reinstalling over the app from the Nokia store - and get the same results. Rebooted a few times - same thing.
Is there any way to reset this and/or remove the app completely? I really need this to work since syncml doesn't work either.
Thanks,
Doug

Then it is getting complicated becuase I never tried alternatives A and B myself:
A) On a computer with MobiMB, access drive A » Menuapps » Mfe » and delete all files except the JAD and the JAR. More details …
B) Nokia » Menu » Sync and backup » Create backup (microSD required) » on a computer you extract this ZIP file and remove the Record-Management-Store files (.rms). Reset the whole phone and restore this modfied backup. More details …
C) With a computer, Nokia Software Recovery Tool
However, I am not sure whether Google still allows new devices for Exchange ActiveSync. Therefore, I do not think that app will ever work for you. Or do you have a ‘Google Apps for Business’ account?

Is ISA required for exchange deployment?

I just read the iphone exchange/enterprise pdfs on apple website and the documentation said that ISA is required for exchange activesync to work. Is this true? Why? What if my company uses another firewall technology? Anyone have any success without ISA?

Easy...port 80 and port 443. If you force SSL only, then you only need port 443. Open that port up on the firewall.
Otherwise, you can do port 80 to the OWA server via firewall rule. Although data is sent unencrypted.
You need a valid SSL cert from one of the major players for SSL to work correctly. People with self-signed internal SSL don't work often.
ActiveSync is just a Virtual Directory on the Windows Exchange Server under IIS and your Activesync on the phone knows which one it is to navigate to for mail sync and authentication.

Troubleshooting and Introduction for Exchange 2007/2010 AutoDiscover - Details about "Test E-mail AutoConfiguration"

AutoDiscover is a new feature in Exchange 2007, to provide access to Microsoft Exchange features (OAB, Availability service, UM) for Outlook 2007
clients or later.
We can determine whether problems related to AutoDiscover via OWA.
For example:
OOF is not working in Outlook Client but it is working in OWA.
When we realized this issue is not related to Outlook Client side and network side after performing some troubleshooting steps, it should be something
abnormal on AutoDiscover.
There is a common tool to check AutoDiscover in Outlook, Test E-mail AutoConfiguration.
Today, we will introduce AutoDisocver and “Test E-mail AutoConfiguration” in details. Hope it is helpful for AutoDiscover troubleshooting and self-learning.
1. Differences between “Test E-mail AutoConfiguration” and other tools
The “Test-OutlookWebServices” cmdlet allows us to test the functionality of the following services:
Autodisocver
Exchange Web Services
Availability Service
Offline Address Book
When we run “Test-OutlookWebServices”, it returns all the web services’ states.
However, some information are useless for some scenarios.
For example:
We just want our Exchange 2010 Server working internally. So it is unnecessary to enable Outlook Anywhere.
However, when we run “Test-OutlookWebServices”, it returns Outlook Anywhere errors because the Outlook Anywhere does not need to been enabled.
In contrast, using “Test E-mail Autodiscover” is more intuitive.
If there is any problems, it will return error code from the test result, like 0x8004010F etc. We can do some research from TechNet articles or MS
KBs.
Although it is difficult to say where the specific problem is just via the error codes, we can combine with IIS logs to perform troubleshooting and
find the root of problem.
2. How to use “Test E-mail AutoConfiguration” Tool
a. Open Outlook, we can find there is an Outlook Icon at the right bottom of System tray. Holding down “Ctrl” button and right click the Outlook Icon, we will see “Test E-mail
AutoConfiguration” option. Please see Figure 01.
Figure 01
b. Click “Test E-mail AutoCofiguration” and input user name, uncheck the “Use Guessmart” and “Secure Guessmart Authentication” checkboxes, then click “Test”. Please see
Figure 02.
Figure 02
c. “Test E-mail AutoConfiguration” result panel and log panel. Please see Figure 03 and Figure 04.
Figure 03
Figure 04
3. How to understand “Test E-mail AutoConfiguration” result
According to the Figure 03, we found there are many URLs in the “Test E-mail AutoConfiguration” result panel. Let us understand the details of these
URLs.
If we these URLs are not the correct ones, we can re-setting or re-creating them via commands.
- Internal OWA URL:
https://vamwan310.vamwan.com/owa/
OWA internal access.
- External OWA URL:
https://mail.vamwan.com/owa/
OWA external access.
- Availability service URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Free/Busy, OOF and meeting suggestions.
- OOF URL:
https://vamwan310.vamwan.com/EWS/Exchange.asmx
Out of Office access.
- OAB URL:
https://vamwan310.vamwan.com/OAB/023ef307-b18a-4911-a52c-de26700f6173/
OAB access.
- Exchange Control Panel URL:
https://vamwan310.vamwan.com/ecp/
ECP access.
4. AutoDiscover Tips
- AutoDiscover Service itself is a web application running on the AutoDiscover virtual directory (not a server service) designed to provide connection information to various
clients.
- The AutoDiscover service is automatically installed and configured when CAS role is added to any Exchange Server.
- AutoDisocver virtual directory is created in IIS within the Default Web Site.
- A Sercive-Connection-Point (SCP) object is created in AD.
- The SCP contains a URL to the AutoDiscover service. This is for intranet clients so they do not have to use DNS to locate the AutoDiscover service.
- In AD this object is located at the following location:
DC=<domain>, CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Administrative Groups, CN=Exchange Administrative
Group, CN=Servers, CN=<CAS Name>, CN=Protocols, CN=AutoDiscover, CN=<CAS Name>
- Setup creates the AutoDiscover URL based on the following structure:
<CASNetbiosName>.domain.com/AutoDiscover/AutoDiscover.xml
If a PKI certificate is not already present, a self-signed certificate is installed on the Default Web Site.
To help allow this certificate pass the Issues to test it is set up with a Subject Alternative Name containing urls.
If a PKI certificate is present, that certificate is utilized and configured for use in IIS.
The Outlook Provider is used to configure separate settings for the Exchange PRC protocol (internal to network), Outlook Anywhere (Exchange HTTP protocol), and WEB:
EXCH, EXPR, WEB
The
EXCH and EXPR setting are vital for the proper configuration of Outlook.
5. AutoDiscover Workflow
General Process flow:
There are various components surrounding the AutoDiscover Service and all are necessary to complete a request. Including IIS, AutoDiscover service
itself, the provider, and AD.
a.
Client constructs service URL and submits Autodiscover Request. First attempt to locate the SCP object in AD. So, DNS is not needed.
b.
IIS Authenticates User.
c.
Is the Autodiscover service in the appropriate forest?
+ If YES.
    1)
Parse/Validate Request
    2)
Is there a provider that can service the Request?
++ If YES
      a)
Config provider processes request and returns config settings.
      b)
Return config setting to client
++ If NO
Inform client we cannot process request
+ If NO.
Redirect client to Autodiscover service in the appropriate forest.
Methods to find Autodiscover services: SCP and DNS
Domain-joined
a. Find SCP first.
The SCP contains the URL to the AutoDiscover service.
URL: https://CAS01.contoso.com(CAS’ FQDN)/AutoDiscover/AutoDiscover.xml
If more than one SCP object is found in AD (it means there are multiple CAS servers in the Exchange organization), Outlook client will choose one of the SCP entries that
are in the same site to obtain the AutoDisocover URL.
b. If we cannot find SCP object, then Outlook client will use DNS to locate AutoDiscover.
Outlook parses out the domain (SMTP suffix) via your EmaiAddress, then attempts to connect to the predetermined order of URLs via the suffix.
For example: If my email address is
[email protected]
Outlook tries POST commands to the following order of URLs:
https://contoso.com/autodiscover/autodiscover.xml
https://autodiscover.contoso.com/autodiscover/autodiscover.xml
NOTE: The URLs above is by design, hardcode
and cannot be changed.
c.
If those fail, Outlook tries a simple redirect to another URLs in IIS:
http://contoso.com/autodiscover/autodiscover.xml
http://autodiscover.contoso.com/autodiscover/autodiscover.xml
If none of these URLs work then DNS is most likely not set up correctly.
We can test that by pinging one of the above URLs.
If that is successful, we must ensure the URLs contoso.com or autodiscover.contoso.com are actually pointing to the CAS server.
If the ping fails then there is a chance that DNS is not set up correctly so be sure to check that the URLs are even registered.
NOTE: If contoso.com is a non-CAS server,
we should add a Host record with just AutoDiscover. And point that entry to your CAS server that is running AutoDiscover.
d.
If still failed, we can use DNS SRV lookup for _autodiscover._tcp.contoso.com, then “CAS01.contoso.com” returned. Outlook will ask permission from the user to continue
with AutoDiscover to post to https://CAS01.contoso.com/autodiscover/autodiscover.xml
Non-Domain-joined
It first tries to locate the Autodiscover service by looking up the SCP object in AD. However the client is unable to contact AD, it tries to locate
the Autodiscover service by using DNS.
Then, same as step b, c, d in
Domain-joined scenario.
6. How to change the AutoDiscover
service location order forcibly?
By default, Outlook client locates AutoDiscover service in that order above.
We can also change the order forcibly.
a.
If we want to locate AutoDiscover service via one of the autodiscover URLs, please running following command in EMS:
Set-ClientAccessServer -identity <servername> -AutodiscoverServiceInternalUri https://autodiscover.contoso.com/autodiscover/autodiscover.xml(URL
that you want)
b. If we want to locate AutoDiscover service via
SRV record, please follows this KB to set up SRV:
http://support.microsoft.com/kb/940881
7. How to check AutoDiscover Healthy
a. We should make sure the AutoDiscover
is healthy before using AutoDiscover to perform troubleshooting.
b.
We can browse following URL in IE explorer:
https://autodiscover.vamwan.com/autodiscover/autodiscover.xml
If it returns “code 600”, that means AutoDiscover is healthy.
Screenshot as below:
c. AutoDiscover itself returns errors to the requesting client if the incoming request does not contain the appropriate information to complete a
request.
The following table explains the possible errors that could be returned.
Error Value
Description
600
Mailbox not found and a referral could not be generated.
601
Address supplied is not a mailbox. The provided email address is not something a client can connect to. It could
be a group or public folder.
602
Active Directory error.
603
Others.
The 600 “Invalid Request” error is returned because a user name was not passed to the service. That is OK for this test because this does confirm
the service is running and accepting requests.
d.
If AutoDiscover service is not working well, I suggest re-building the AutoDiscover Virtual Directory for testing.
Steps as below:
1) Running following command in EMS to remove the AutoDiscover VD (we cannot delete it via EMC):
Remove-AutodiscoverVirtualDirectory -Identity "CAS01\autodiscover(autodiscover.contoso.com)"
Please refer:
http://technet.microsoft.com/en-us/library/bb124113(v=exchg.141).aspx
2)
Running following command in EMS to verify whether we have removed the AutoDisocver VD successfully:
Get-AutodiscoverVirtualDirectory | FL
Please refer:
http://technet.microsoft.com/en-us/library/aa996819(v=exchg.141).aspx
3)
Running following command in EMS to re-creating a new AutoDiscover VD:
New-AutodiscoverVirtualDirectory -Websitename <websitename> -BasicAuthentication:$true -WindowsAuthentication:$true
Please refer:
http://technet.microsoft.com/en-us/library/aa996418(v=exchg.141).aspx
8. Common issues
a. Outlook Disconnection
Issue and Troubleshooting
Issue:
Sometimes the Outlook clients cannot connect to the Exchange server after migrating to a new Exchange server or changing to new CAS. The Outlook clients
always connect to the old CAS server.
Troubleshooting:
To solve this issue, we should change the SCP via following command:
Set-ClientAccessServer -Identity
<var>CAS_Server_Name</var> -AutodiscoverServiceInternalUri
https://mail.contoso.com(newCAS’FQDN)/autodiscover/autodiscover.xml
b. Autodiscover
Certificate issue
Tips on Certificate:
Exchange requires a certificate to run an SSL protocol such as HTTPS. We can use the certificate that supports subject alternate names (SAN) in Exchange.
This is to allow the certificate to support resources that have different names, such as Outlook Anywhere and the Autodisocver Web application.
Issue and Troubleshooting
Issue:
We receiver the Certificate Principal Mismatch error when we use a SAN certificate.
Troubleshooting:
1) Please determine the FQDN that the client
uses to access the resource. Steps as below:
OutlookàToolsàAccount
SettingsàE-mailàclick
the Exchange accountàChangeàMore
SettingsàConnectionàExchange
Proxy Settingsànote the FQND that list in the
Only connect to proxy servers that have this principal name in their certificate box.
2)
Please using EMS to determine the value for the CerPrincipalName attribute: Get-OutlookProvider
This command returns the result for the EXPR name.
3)
Please re-setting the CertPrincipalName attribute to match the FQDN via following command:
Set-OutlookProvider EXPR –CertPrincipalName: “msstd:<FQDN the certificate is issued to>”
9. Resource for reference:
Autodiscover and Exchange 2007
http://technet.microsoft.com/en-us/library/bb232838(v=exchg.80).aspx
White Paper: Understanding the Exchange 2010 Autodiscover Service
http://technet.microsoft.com/en-us/library/jj591328(v=exchg.141).aspx
Certificate Principal Mismatch
http://technet.microsoft.com/en-us/library/aa998424(v=exchg.80).aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

HI,
I get following? when run the test? user is login to Domain A but accessing exchange in Domain B?

Exchange 2010-2013 co-existence - need for OWA/ActiveSync legacy namespace?

Hi all
Straight to the point: how to I update units that were set up manually with Exchange ActiveSync (pointing to owa.domain.com) with a temporary legacy namespace owa-legacy.domain.com, and then back to owa.domain.com?
Background: I did a test run of migrating a single-server installation from Exchange 2010 to Exchange 2013. As expected, after moving a user's mailbox to the new Exchange 2013 CAS with owa.domain.com still pointing to Exchange 2010, the user
was unable to log in at the Exchange 2010 OWA, and the ActiveSync unit was unable to fetch mail.
So I created a legacy namespace (owa-legacy.domain.com) and set this as the URL on the Exchange 2010 server, and waited for it to populate, then switched owa.domain.com to Exchange 2013. But the URL on ActiveSync units was still pointing to the wrong URL.
What did I overlook or not understand, or am I making migration more complex than needed?
Thanks for reading and best regards
/Maurice
PS: here were some of my pre-post readings:
Exchange 2003-2013 co-existence, even better
Exchange 2003-2013 co-existence,
Exchange 2010-2013 co-existence slides,
Upgrading ActiveSync to Exchange 2010,

Hi
Is that because External URL on Internet facing CAS servers were set to Blank，and Users are not able to get Updated URL
Please try to Add the External URL and made sure that all the required configurations are set Appropriately.
Also I suggest posting on Exchange ActiveSync Forum as well
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

SMTP test to Exchange 2013 failing

I have an Exchange 2013 server set up for testing which I am trying to have the internal servers relay off of to EarthLink (My ISP).
The Receive Connector is set up as a FrontEnd Transport, Anonymous and Externally Secured authentication. It accepts all addresses from my internal subnet.
The Send Connector is set up using a Smart connector to smtpauth.earthlink.net. It is set to use port 587 ( which is what EarthLink apparently uses). It uses basic authentication with my credentials to EarthLink. The address space is set
to '*'.
When I am on one of the member servers, I telnet 25 to the Exchange 2013 server and testing it:
220 exchange.home.com Microsoft ESMTP MAIL Service ready at Sun, 23 Nov 201
4 08:41:40 -0500
ehlo home.com
250-home.cave.com Hello [172.16.200.20]
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH
250-8BITMIME
250-BINARYMIME
250 CHUNKING
mail from:[email protected]
250 2.1.0 Sender OK
rcpt to:[email protected]
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Hello
Goodbye
451 4.7.0 Temporary server error. Please try again later. PRX3
I have been searching all over for some insights what this 451 4.7.0 .... PRX3 error is. There are a number of posts about PRX2, PRX4 and so forth. I have already found the information about verifying all DNS servers and creating a record in
the host file. None of that changed anything.
I disabled Symantec thinking it was causing the problem. Nope.
Any suggestions are GREATLY appreciated!

Hi Dolbert
Thank you for your question.
Did you can receive/send email?
If not, you can give me some error in your log or event?
“451 4.7.0 Temporary server error. Please try again later. PRX3” encoded SMTP response for when proxy fails because of connection failures to the destination. It happened at the send connector cannot resolve the correct destination. You can refer to the
following link to set configure internal reply:
http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
If there are any questions, please let me know.
Best Regard,
Jim

Security Update for exchange 2013 SP1 (KB3040856) failed mid-way / power problem mailbox server disconnected

While applying todays security update for exchange 2013 (KB3040856) there was a power issue (sad story) and the update was interrupted halfway through. A bunch of service were left deactivated and I beleive I brought them back.
At this point the exchange admin center brings me to the login and when I do login, I get an enable to display page msg after the login.
I have an ActiveSync error log "cannot access the mailbox because the mail box server is disconnected" translated from french.
I also have ASP.NET 4.0 error "MapiExceptionMdbOffline"
What could be the next step in fixing this if it is at all possible ? I am not an expert in cmdlet but can manage if pointed in the right direction.
Any help would be greatly appreciated.
Thank you.

I ran update KB3040856, and it disabled all Exchange services, and a few others besides (IIS and filtering). I ran the test-servicehealth cmdlet and eventually got all the services set to automatic and all running.
This is really a stupid thing for an update to do, what is going on? Exchange 2013 is trouble enough already, we really do not need this sort of agro.

Exchange ActiveSync testing and setup with BB10

Here are a few of my favorite links for testing EAS issues and getting a BB10 device to connect to an Exchange server with Active Sync
How to use Outlook Web Access to log Exchange ActiveSync activity for a single mailbox http://www.blackberry.com/btsc/KB34552
How to test Microsoft ActiveSync connectivity
http://www.blackberry.com/btsc/KB34024
Supported Microsoft ActiveSync Features and Policies for use with BlackBerry 10
http://www.blackberry.com/btsc/KB33619
How to add a Microsoft Exchange ActiveSync email account on the BlackBerry 10 smartphone
http://www.blackberry.com/btsc/KB33940
How to whitelist BlackBerry 10 smartphones and BlackBerry PlayBook tablets for use with Exchange Active Sync Gatekeeping
http://www.blackberry.com/btsc/KB33531
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

This could be very helpful! Thanks.

Can Exchange activesync be used for calendar and contacts without BES?

I thought it could- just got a Z10 and am having trouble syncing with a cloud service that uses EAS Tech support just told me that I have to be on BES for that? Wasn't what I thought. Knowledge base article KB34208 "Sync time frame for calendar events when using a Microsoft Exchange ActiveSync connection " Says nothing about BES in the Environment section? http://btsc.webapps.blackberry.com/btsc/viewdocument.do?externalId=KB34208&sliceId=2&cmd=displayKC&d... Hoping guy was wrong- I really need to be able to get my desktop info onto phone and this is convoluted enough- syncing to cloud and then to phone but want to keep the phone (4th BB and a PB). Help please.

you dont need BES10. you can do EAS directly from the device to the Exchange Server.
zeki

Best Practice - Hardware requirements for exchange test environment

Hi Experts,
I'm new to exchange and I want to have a test environment for learning, testing ,batches and updates.
In our environment we have co-existence 2010 and 2013 and I need to have a close scenario on my test environment.
I was thinking of having an isolated (not domain joined) high end workstation laptop with (quad core i7, 32GB RAM, 1T SSD) to implement the environment on it, but the management refused and replied "do it on one of the free servers within the live production
environment at the Data Center"... !
I'm afraid of doing so not to corrupt the production environment with any mistake by my configuration "I'm not that exchange expert who could revert back if something wrong happened".
Is there a documented Microsoft recommendation on how to do it and where to do so to be able to send it to them ??
OR/ Could someone help with the best practice on where to have my test environment and how to set it up??
Many Thanks
Mohamed Ibrahim

I think this may be useful:
It's their official test lab set up guide.
http://social.technet.microsoft.com/wiki/contents/articles/15392.test-lab-guide-install-exchange-server-2013.aspx
Also, your spec should be fine as long as you run the VMs within their means.

Exchange / ActiveSync - Works for a day or so, then stops

I've had my iPhone 3G since launch and have configured it to work with my Exchange 2003 server utilizing activesync at work. It will connect and sync fine for a day or so, however then it will start giving me a "cannot get mail" "cannot connect to server" error message. The phone has plenty of signal and can reach the net, the exchange box is online and functioning properly. If i delete and recreate the account on the iPhone it starts syncing properly again, however it's only a matter of 24-48 hours before i have to repeat this process...any suggestions?

Same here since beta. I'm an Exchange admin and we've been seeing this since the last 2 beta releases before iPhone OS 2.0. Running Exchange 2003 SP2. We set up ActiveSync from scratch, just for iPhone use. Windows mobile phones work without a hiccup on the same system. Problem happens with either the original iPhones or 3G. And it's totally random for different users. Works fine for a couple days, then stops. The best routine we found to get back up and running is: turn off 3G and wifi. Delete account settings on the iPhone. Re-enter Exchange account info and reboot the phone. This will usually re-sync everything. I'm leaving my phone in this non-3G, non wifi mode, and it seems the most stable. The following things seem to cause it to break for me: opening emails with large attachments, switching to wifi, or just wait long enough and it breaks. Once it's broke, I usually have to do the whole "delete account setting" routine to get it back. I tried reconfiguring our internet-facing front end to use ISA server as is required for Exchange 2007, with delegated kerberos authentication . When ISA server was in place, we had 2 out of 10 iPhones able to function. I had to switch back, because I was getting yelled at We have a line of people at my work asking when this will be fixed. And a bunch of admins running around and trying different settings on their phones. We can't make it an "officially supported" email device until this works.

Testing of Autodiscover for Exchange ActiveSync failed.

Similar Messages

Maybe you are looking for