Microsoft Exchange Connectivity MSX/MSJ - MS 2008 update

Hi experts.
We are running this integration szenario in an 32bit / Windoes 2003 environment,
Now we want to upgade to 64bit OS and MS Exchange 2008 version.
Where can I check the supported plattforms? The pam had nothing to say ...
Thanks in advance
jw

If I were you, I would create an OSS customer message for this.
Maybe a quick fix though... Have you installed Outlook 2003 on the same server as IIS is running on? Have you run outlook at least once and connected it to your Exchange server, setting it as the default mail client?
Also, there is a note about what to do for exchange transports when you do a portal patch. Applying those steps might be a good idea even if you have not done an upgrade.
Good Luck.
Regards,
Graham.

Similar Messages

Cannot install the Microsoft Exchange connectivity analysis tool

I am troubleshooting our new 2013 Exchange server because Outlook client cannot connect but OWA is working fine. The 2 new 2013 Exchange server as DAG were installed to co-exist with Exchange 2007.
I am trying to download and install Microsoft Exchange connectivity analysis tool BUT always got an error "Error attempting to install the Microsoft Exchange connectivity analysis tool" and in the log the error is "URLDownloadToCacheFile
failed with HRESULT '-2146697208'.
I am installing it in Windows 8 64b, Please help as we are troubleshooting the new Exchange without any success so far...If there is an full download link, please provide.
Thanks in advance...

Hi Teyob,
Did you try to use different browser to check if the issue persist?
This issue was occurred on browser. If you IE with this issue, we should check to clear the option "Warn if changing between secure and not secure mode" from your Internet Explorer(IE) Tools--Internet Options--- Advanced--Security.
If the setup URL of the ClickOnce application being installed is redirected from a non-secure to a secure site (or vice-versa), the installation would fail due to the Internet Explorer warning. Therefore, please make sure to remove the redirection completely
and point to the actual setup URL.
If the issue persists, we could perform Windows Update to install updates and then run the Desktop configuration again.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

MAPI_E_LOGON_FAILED(80040111) when testing Microsoft Exchange Connectivity

Hi everybody
I could really use some help on Microsoft Exchange Connectivity Architecture based on CDO. The documentation I have followed can be found here: http://help.sap.com/saphelp_nw70/helpdata/en/c9/b9182b06af714c89d7d39c76af22a1/frameset.htm.
Generally I have followed the documentation as much as possible, though the following two pieces of information might be the root cause to my agony:
1) The key HKEY_USERS.DefaultSoftwareMicrosoftWindows NTCurrentVersion Windows Messaging SubsystemProfiles from http://help.sap.com/saphelp_nw70/helpdata/en/43/5df14ef76130b4e10000000a11466f/frameset.htm cannot be found on the computer where I have my IIS installed (the IIS is installed on the portal server which resides in the same domain as the exchange server). How come this key is not present and what does it represent?
2) The version of CDO.dll on the IIS (portal server) is 1.2.1s (6.5.7233.48) and is installed together with Outlook 2003. The version of CDO.dll on the Exchange Server is 1.2.1 (6.5.7651.61) and is installed together with Exchange 2003 SP2. This might also be a issue?
I have read that there are potential problems with the 1.2.1s in a certain note, but the errors described in that note did not correspond to the one I'm getting.
The portal is running NW04s SPS 10.
When I use the test-tool (SAPPXchTest.exe) I get the following error in the log:
The information store could not be opened. [MAPI 1.0 - ]
6/4/2007 9:58:10 AM Closing logging for user [email protected]
Any (fast) help on this issue will be rewarded.
Kind regards,
Martin Søgaard

Hi Philipp
Yes, I did manage to solve this problem.
It was because the Exhange Server should be set up as the domain controller as well. This setup raises a lot of security issues though, which Im consulting SAP about at the moment.
Kind regards,
Martin Søgaard

Latest apple software update on Mac --cant view Microsoft exchange connected email on macbook pro. Loads but not viewable. Works fine on iPhone

Updated the lastest apple software to my macbook pro and now I can no longer read my emails from my microsoft exchange email. The email arrives in my inbox and you can open it -- but when you try and read the content -- it says loading..... but never loads. It worked fine this weekend -- but after I udpate the last apple software update it stopped working. I can read the emails fine on my iphone (same email account) but not on my macbook pro.
I called Apple and they could not figure out a solution to the problem -- is anyone else having this trouble?

Concisely:
https://discussions.apple.com/community/iphone
https://discussions.apple.com/community/ipad
Try posting there.

Microsoft exchange connection

I have a new MacBook Pro with Mountain Lion (10.8.2) and Microsoft Office 2011 (14.3.0)
I have set up my Exchange account using username and password access. For the first 3 days, it worked perfectly and I had no issues connecting, sending, receiving or synching mail. Then, when I opened Outlook, it would not connect to the Exchange Server. My internet connection was fine and I could use everyhting else, but Outlook just wasn't connecting to the Exchange Server.
After a day or so of trying everything I knew (which was very little...lol), I decided to delete the account and start over. So I did that and immediately got connected to my Exchange Server again. It worked great, pulled in all of my mail off the server and worked for me perfectly all day today. Then, tonight, I fire my machine back up and open Outlook and it's not connecting to Exchange again for some reason?
To make sure it wasn't on the Exchange Server end, I sent myself a test email from another non-Exchange account TO the Exchange account and received that email immediately on both my iPhone and iPad. Yeah, that's the other thing...I have this exact same Exchange account set up on my iPad and iPhone and those both work without issue. It's only on my Macbook Pro...
Any suggesstions?

Ok, so what if I use Apple Mail? I can not get Outlook to work and have tried everything I know.
Apple Mail is also having a hard time connecting and I followed the advice of another Apple user here in the forums and set it up without the auto-discover feature disabled.
If I type in the Exchange server path it will not connect regardless of my other settings. The only way I can get ANY email is to type in the server name that is on my iPhone. The problem there is that it only pulled in a fraction of emails I have sitting on the Exchange server.
In Outlook, I have also noticed that I don't get the Exchange feature that syncs all of my devices. So, if I delete an email from my Mac, it does NOT delete them from my iPhone. If, however, I delete an email from my iPhone, it DOES delete it from Outlook on my Mac. I also get all of my (old) emails off the Exchange server when using the same server name as my iPhone.
In Apple Mail, the "synching" feature between devices does appear to work but, as I stated above, it does not pull in all the emails I have sitting out there.
So one mail client (Outlook) gets all of my emails off the server but doesn't sync automatically with all of my devices. The other mail client (Apple Mail) does sync automatically with my other devices, but doesn't pull all the mails off the Exchange server.

How to establish a Microsoft Exchange connection (Office 365)?

My institution has just informed me that they are switching off IMAP and POP access from Monday. Email and calendaring are provided by Office 365. Alternative configuration instructions are available for mobile devices (iOS, Blackberry, Android etc.) but not for Thunderbird. Their only suggestion is a paid plugin which my school would have to pay for. This just ain't gonna happen. Moreover, I would prefer a free software option if at all possible. ('Free' as in 'freedom', though beer is important, too.)
Calendaring isn't important as I have that setup independently of my organisation's provision. Only email matters.
Searching rather urgently has turned up a few leads but they are generally quite old and almost all require IMAP and/or POP enabled on the server. Beyond that, I've come across the following possibilities:
davmail which apparently bridges between OWA and IMAP/POP, but I'm not clear if this would work with Office 365 as I've only found references to using it with older MS Exchange servers;
evolution with a plugin;
possibly KDE's mail programme, although I'm not clear from the information I've found whether this is really an option or not.
I'm running KDE. If possible, I'd prefer to avoid the Gnome dependencies of evolution. However, if that's the only option, so be it. An ideal solution will work on Fedora as well as Arch. (Obviously Fedora is off-topic here - I just thought I might as well mention it.) A really ideal solution would also let me continue using Thunderbird without relying on proprietary code, but I'm beginning to think this is probably a pipe dream.
The most attractive of the above options is currently davmail, if that is really an option. However, I get the impression that this could require considerable overhead.
I would greatly appreciate any advice or pointers anybody can offer me. So far, I've not found anything which even mentions Linux with Office 365. I'm not sure if this is because 'Office 365' is actually relying on something else (and that's what I need to search for), whether it is because the situation is hopeless or whether it is for some other reason.

brebs wrote:
cfr wrote:I'm not clear if this would work with Office 365
Well, 10 seconds of googling for "office 365 imap" shows encouraging davmail fixed bug report.
Thanks. Sorry. I did spend a lot of time searching but I did not find that. (Using IXQ for search.) But I was not trying 'imap' specifically - rather 'linux' - as I just wanted any way to access it. And the results I got tended to assume the Exchange server had imap enabled.
Some things I would raise:
* Check the IT policy regarding whether Linux is supported/accepted. And if not, why not.
* Push for clarification regarding the supposed security risk, or whatever is being used as justification.
As Trilby pointed out, this is useless.
Linux is not supported except on a 'best effort' basis. I run Linux on my office PC. I'm entirely responsible for it. Local IT will help if they possibly can. Central IT will say that Linux is supported sufficiently because you can use web mail.
They do not need to justify this. There does not need to be an answer to 'why not?'
No justification has been offered for switching off the support. Trilby's IT invoke security to justify not turning it on. My IT offer no reason for turning it off. It is just a fact that it is being switched off.
[For some reason, it has not yet been switched off, although they said it would be yesterday.]
The suggestion of raising these issues may sound perfectly reasonable, but it is a suggestion based on ignorance of reality.
In a sane world, it would make perfect sense. But this is academia in 2015. (Not just academia, I know.) Sanity is an irrelevant standard.
Last edited by cfr (2015-06-09 15:31:28)

Outlook 2011 for Mac with Microsoft Exchange 2007/2010

Hi,
For already a fews days I am troubleshooting a Mac Outlook 2011 <> Exchange sync issue. I've got exact the same symptoms in two totally different environments.
- Environment one:
Exchange 2007 SP3 RU 14 (8.3.379.2)
Outlook 2011 14.4.7
- Environment two:
Exchange 2010 SP1 RU 8 (14.1.438.0)
Outlook 2011 14.4.7
Problem:
Autodiscover and EWS synchronisation test from Microsoft Exchange Connectivity Analyzer is succesfull. Configuring an new (Exchange) e-mail account with Outlook2007/2010/2013 fully based on autodiscover works with no errors.
Configure Outlook 2011 based on autodiscover when connected to the internal LAN works. Configure Outlook 2011 based on autodiscover or by hand doesn't work from WAN.
I am unable to synchronize Outlook 2011 with Exchange when WAN connected (No error in logging). I am able to synchronize OS X Mail (Default OSX Mail client) with the same Exchange server.
Conclusion: the autodiscover function that Outlook 2011 uses does not work from WAN, the autodiscover function that Outlook 2007/2010/2013 and Exchange Connectivity Analyzer is using does work from WAN. Do I need to configure something special for synchronization
with Outlook 2011 other than explained above when working from WAN?
When testing EWS with 3th party tooling(EWS Editor) and Exchange Connectivity Analyzer everything is working as it should be. (all mailbox data is shown). If you need any more information about the context I am happy to provide.
Regards,
Mikkie van Falier

Hey hpujary.
Welcome to the BlackBerry Support Community Forums.
At this time, only contacts can be synchronized with BlackBerry Link software and a BlackBerry 10 Smartphones. The functionality to provide more options for PIM synchronization may be added in the future. I cannot say for certain that the issue outlined in KB27248 is resolved for BlackBerry 10 Smartphones as the functionality does not exist to confirm.
Cheers.
-Sawks
Come follow your BlackBerry Technical Team on Twitter !@BlackBerryHelp
Be sure to click Like! for those who have helped you.
Click Accept as Solution for posts that have solved your issue(s)

Microsoft Excahnge connection status in Outlook

Hi,
I tried to search but unable to find so if any one knows how can I get detail of every column of "Microsoft Exchange Connection Status" when we check from Outlook connection status
Thanks
SMF

Hi,
I find some significant columns in Outlook connection status, for your reference:
SMTP Address: this column indicates the account that is associated with a given connection.
Proxy Server: This indicates which proxy server Outlook is connecting to.
Server name: it specifies the actual server name which is outlook connect to.
Status: you can use this column to review information about the current connections Outlook has established to the Exchange server or not.
Protocol: it specifies which protocol is used for this connection.
Authn: it indicates the autentication type the connection is actually using.
Protocol: it specifies which protocol is used for this connection.
Req/Fail: it notice that how many requests were made and how many failed for that particular connection.
Avg Resp: it specified the average amount of time it took to respond to those requests.
Sess type: it specifies whether Outlook is connected to the Exchange mailbox in Cached Exchange Mode or online mode.
More details about Connection Status dialog, please refer to:
https://support.microsoft.com/kb/2737188?wa=wsignin1.0
http://blogs.technet.com/b/labrat/archive/2005/10/10/412288.aspx
Best regards,
Allen Wang

After lion 10.7.3 update messed my mac had to restore from time machine now Outlook won't connect with microsoft exchange, any idea?

after lion 10.7.3 update messed my mac had to restore from time machine now Outlook won't connect with microsoft exchange, any idea?

I've had a similar problem. On my first boot up after installing 10.7.4, Firefox would not open. Crashed every time. Safari was not affected. I have no idea if it was related to the flash plugin, but I did install a the latest version of that a couple of weeks ago.
Here's what fixed it: a second boot up.

Hi i m using 4s and its updated but i cant configure with microsoft exchange for my gmail account. Anytime i tried to configure it the message comes connection to the server failed. Pls help me out.

Hi i m using 4s and its updated but i cant configure with microsoft exchange for my gmail account. Anytime i tried to configure it the message comes connection to the server failed. Pls help me out.
<Email Edited by Host>

Discontinued by Google. Read here:
http://googlesystem.blogspot.com/2012/12/google-sync-discontinued-for-gmail.html

The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete - Cant add Outlook accounts

Hi have recently started getting the following error message when setting up new accounts with Outlook 2007:
The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Outlook then prompts me to enter the username and password, i do so and get message again. This happens on Windows XP Professional and Vista, i cannot setup any accounts for new machines.
Points to note are that OWA works fine, and previous users who are already setup work fine also. It seems to be limited to setting up new Outlook 2007 accounts.
It can find the username fine. It comes up with green ticks underr the Online Search for your server settings:
Establish Network connection
Search for [email protected] server settings
Long on to server ---------- then it fails with a big red cross at this point
Recently i did add a second mail server to the network but it was not configured to talk to the other main mail server which was handling all the functions of mail box, CAS, hub transport. I had installed all the same roles on the second server with a view to move it across and retire the old server, the second machine is a different machine name from the main mail server. In summay my servers are:
svr001              Server 2003 R2 Enterprise x64 domain controller
mail                 Server 2003 R2 Enterprise x64 non-domain controller with exchange 2007 SP1
mail001            Windows 2008 Enterprise x64 non-domain controller with exchange 2007 SP1
The main box "mail" has been fine until i recently introduced this new server "mail001" into the network.
I am really stuck now and would really appreciate any pointers or steps to debug the above.
Many thanks,
Chris

The FIX IT here
http://support.microsoft.com/?kbid=319206 works, but only for a user who's already logged in (if you just run the fix it program and do nothing else). To make it work for all users you'll need to manually edit the registry as it says in the article.
To force Outlook to use a pre-defined global catalog server, use the following steps to set the following special registry parameter to point to the Fully Qualified Domain Name (FQDN). Doing this over-rides any setting in the MAPI profile.
Click Start, and then click Run.
In the Open box, type regedit.exe, and then click
OK.
Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
Note You may have to create the registry path.
On the Edit menu, click Add Value, and then add the following registry value:
Value name: DS Server
Data type: REG_SZ (string)
Value data: FQDN of the global catalog server
This allowed me to roll out a bunch of laptops and not have to worry about running the Fix It for each user.
update: Sysprep seemed to remove fix. Each time a new user logged into a newly imaged laptop (on domain) same error about Outlook 2007 cannot connect to Exchange. Have tried just about everything, but all I seem to be able to do is run this stupid
Fix it each time. Luckily I don't have 1000 machines to setup because then I'd be screwed.

"The Connection to Microsoft Exchange is unavailable" when adding second Exchange account to Outlook 2013

I have a problem that I've found to be typical, just haven't found anything that describes my exact problem.
I'm having trouble adding a second Exchange 2010 server account to Outlook 2013 in one of the computers of the domain. Outlook 2013 will complain with "The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete
this action".
I've Googled and found many threads with the same error... however most of those seem to be either a problem with the server, or the Global Catalog in Active Directory, or the "connection method" (I've tried all found solutions to no avail).
This is not the case, since the first account is added with absolutely no problem. It can send and receive and I can delete the outlook profile and recreate it and it'll give no problems. I have this problem only when adding a second account.
This is a fresh Windows 8.1 install with an up-to-date Outlook 2013. I have other computers in the same domain and network, with the same setup (Win 8.1 + Outlook 2013) configured with two exchange accounts with no problem.
There are no connectivity problems, I can access that same account through OWA and in other computers on the network... the Global Catalog seems to be fine (shows two active DCs, which is correct).
I've tried deleting and recreating the outlook profiles, repairing the outlook installation, even deleting all outlook files in AppData and letting it recreate them, with no success.
Any hints of what could be going on?
Before I speak, I have something important to say.

Hi Javier,
Thank you for the update.
I have tested on my lab and get following result.
Lab: Exchange 2010, CAS Array (CAS01+CAS02), MBX01, DC
Type Server Field
Check name result
Changed Server Field
CAS01.domain.com
Yes
CASArray.domain.com
CASArray.domain.com
Yes
CASArray.domain.com
DC.domain.com
Yes
CASArray.domain.com
MBX01.domain.com
No
"The Connection to Microsoft Exchange is unavailable"
Based on my knowledge, the reason why inputing DC FQDN in the Server Field fixes this issue is that Outlook performs AD Lookup and finds the account configuration from AD, then back the CAS Array FQDN in the Server Field instead of DC FQDN.
Exchange 2010 is different from Exchange 2013, if you are using Exchange 2013, we need to input MailboxServerGUID.domain.com into Server Field.
If there is anything I’ve misunderstood, please don’t hesitate to let me know.
Thanks,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action. Error while connecting to exchange through Outlook 2010

Hi,
I have set up Exchange Server 2013 on Windows Server 2008 R2. Everything is working fine except I am unable to configure Exchange account in Outlook 2010 or any other version. It says
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
Error screenshot is attached. Even, I am able to configure exchange active sync on my adroid and ipad which is working perfect. Please let me know if any body have any idea about it. Searched many blog and forum but still now solution till now.
Thanks in advance
Regards,
Manoj

Hi Manoj,
Can you ping your Exchange server? It would hlep us isolate the fault from network releated issue.
Is there a trusted certificate installed on Exchange 2013 server?
If you run the test of RPC over HTTP in
https://www.testexchangeconnectivity.com/, is there any error returned?
For more information, please refer to :
http://technet.microsoft.com/en-us/library/bb123741(v=exchg.150).aspx
http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/1b4dc21c-c745-4699-8eee-423105608dcd/
Thanks.
Fiona Liao
TechNet Community Support

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Microsoft Exchange link won't sync, doesn't receive email since updating 5s to iOS 8.0. Is there a solution to this?

iPhone 5s stopped receiving Exchange email a couple of days after updating to iOS 8.0. Initially there were no problems. Microsoft Exchange account now connects but won't sync.Other email accounts, Safari and Apps work with no problems. Have tried removing and re-entering the Exchange account, and done a Network Reset. Still get 'No Mail' on Exchange email screen. Is this a common occurrence and does anyone have a solution?

We had about 10 iPhones (4S, 5, 5S) which did not receive any mail or other things over Exchange. After some research, we did an iisreset on our Exchange OWA. This was our solution. Everything is working fine now.

Microsoft Exchange Connectivity MSX/MSJ - MS 2008 update

Similar Messages

Maybe you are looking for