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

Similar Messages

Error while installing exchange2007 : Unable to initialize the Microsoft Exchange Information Store service. Failed to find the

Hi,
I am trying fresh install of exchange2007, everything gone well but, finally it thrown a error saying :
Unable to initialize the Microsoft Exchange Information Store service. Failed to find the working directory parameter from the registry - Error 0x80004005.
the installation log says
6/5/2007 3:14:05 PM] [1] Processing component 'Mailbox Service Control (Last)' (Starting mailbox services).
[6/5/2007 3:14:05 PM] [1] Executing 'start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"', handleError = False
[6/5/2007 3:14:05 PM] [2] Launching sub-task '$error.Clear(); start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"'.
[6/5/2007 3:14:05 PM] [2] Beginning processing.
[6/5/2007 3:14:05 PM] [2] The maximum wait for the operation is set to 'unlimited'.
[6/5/2007 3:14:05 PM] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.
[6/5/2007 3:14:05 PM] [2] Will wait '10000' milliseconds for the service 'MSExchangeIS' to reach status 'Running'.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to reach status 'Running' on this server after waiting for '10000' milliseconds.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] [ERROR] Unexpected Error
[6/5/2007 3:14:15 PM] [2] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] Ending processing.
[6/5/2007 3:14:15 PM] [1] The following 1 error(s) occurred during task execution:
[6/5/2007 3:14:15 PM] [1] 0. ErrorRecord: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceFailedToStartException: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
[6/5/2007 3:14:15 PM] [1] Finished executing component tasks.
[6/5/2007 3:14:15 PM] [1] Ending processing.
[6/5/2007 3:14:18 PM] [0] End of Setup
[6/5/2007 3:14:18 PM] [0] **********************************************
this I am trying on my test system please help me out in resolving the issue
thanks in advance,

Gary,
Open Registry Editor.
In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Create the following value (REG_SZ): Working Directory and give it a value that points to the new database folder.
Make sure you back up the registry before you do any changes on it.
Raj

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

The Microsoft Exchange Address Book was unable to log on to Exchange

I am currently migrating a exchange 2007 to exchange 2013.
Exchange 2013 is installed on a seperate Windows Server 2012 server.
Exhange 2007 is installed on a seperate Windows Server 2003 R2 server.
I have moved some mailboxes from exchange 2007 to exchange 2013 and also created some new mailboxes on the exchange 2013 server itself.
OWA, ActiveSync , IMAP are all working correctly for those mailboxes , but I am not able to connect to outlook with the exchange option (local connection).
Outlook 2013:
When I use autodiscover to connect to the exchange server step 1 & 2 are working correctly (establishing network connection & searching for mailbox settings) but on the 3th step (logging on to the mail server) I receive the following error
The name cannot be resolved. The Microsoft Exchange Address Book was unable to log on to Exchange. Contact you system administrator if the problem persists.
When I filll in the exchange server manually (using the normal servername server.hq.corp.domain.local not the guid version) the check name resolves correctly and the profile creation is finishing ok. But when I try to open outlook with that profile it gives
me the following errors :
with cached exchange mode selected:
Cannot start Microsoft Outlook. Cannot open the Outlook windows. The set of folders cannot be opened.
You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)
with cached exchange mode deselected:
Cannot start Microsoft Outlook. Cannot open the Outlook windows. The set of folders cannot be opened.
Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance
When I use the Microsoft Connectivity Analyzer it fails on the following step:
Testing the address book "Check Name" operation for user [email protected] against server [email protected]
An error occured while attempting to resolve the name. Elapsed Milliseconds: 91 Additional Details: The address book bind operation failed with status -2147221231. NSPI Status 2147746065

Hi,
Please run the following command in Exchange server to get Exchange GUID:
Get-Mailbox UserA | FL Identity,ExchangeGuid
Then open Outlook, click File > Account Settings > Account Settings > Change (If you can’t open Outlook, go to Control Pane > Mail to change it). In Server Settings, import the [email protected] into the Server box and click Check Name
to have a try.
If the name is checked successfully but also can’t open the profile, please close Outlook. In the Start menu, Run command (Windows key + R), type or paste
outlook.exe /resetnavpane (Note: Make sure there is a space between the words.)
Then press Enter (or OK button) to restart Outlook
Regards,
Winnie Liang
TechNet Community Support

MS Outlook 2013 Error message "The microsoft exchange administrator had made a change that requires you to quit and restart outlook"

I am currently running 2 HP Servers, SAN Storage. I have Exchange 2013 installed and MS Outlook 2013 randomly appears with the message
"The Microsoft exchange administrator has made a change that requires you to quit and restart outlook" It is happening very frequently and is appearing every few seconds on a lot of users.

Hi WeeMac22,
If you migrated from Exchange 2010 to Exchange 2013, I found a KB for your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
http://support.microsoft.com/kb/2934750/en-us
If not, I suggest using OWA to verify whether this issue remains.
1. If everything works well in OWA, it seems an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
I suggest re-install the Outlook if all methods above not working.
2. If this issue remains in OWA, please verify whether all users on the Exchange 2013 have this isse.
If only one user has this issue, I suggest create a test user to check whether the test user has this issue.
If the test user works well, I suggest try to re-create the specific user account.
Please make a full back up before re-creating.
Thanks
Mavis
Mavis Huang
TechNet Community Support

The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook in Exchange 2010.

Hi,
We have 2 Exchange 2010 servers with multiple roles installed ,also we have setup cas array on the same with help of Kemp load balancer. Both have 1 public folder on each node.
There are few accounts(including mine) those are recently migrated from Exchange 2003 to Exchange 2010 and they are getting intermittantly an error pop "The Microsoft Exchange administrator has made a change that requires you quit and restart
Outlook"
this generally happens when i switch the network for my laptop but not every time 2-3 times in a week.
i already gone through this link but didn't get any solution. Any help is appreciated.
http://blogs.technet.com/b/aljackie/archive/2013/11/14/outlook-rpc-end-point-and-pf-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx
Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

Hi,
I recommend you check if any Public Folder on one member of a CAS array.
If yes, it will cause the issue.
I had encountered a similar issue.
The Problem exists when an Outlook client connects into a CAS array initial if
it connects to the CAS array member that contains the PF role, then Outlook
Converges all connections and displays both the Public and Private logons as one
single conneciton to Mail.company.com (the CAS array name) When the Clients IP
address changes, and it Re-connects, if it gets connected to a CAS array member
that does not have the PF server, then we get an ECwrong server Response from
Exchange, Outlook in it's reconnect logic Cannot follow the Redirection Result
that contains the correct PF server name, and displays the Error "the Admin has
made a change that requires you restart Outlook"
Finally, move PF to separate server as a workaround.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
Thanks !
As i started this question saying i have already read these things . If this is the case i am wonder why microsoft didn't release a technet article where it must discussed about CAS array and Public folder confliction.
However, you said
"if it gets connected to a CAS array member
that does not have the PF server, then we get an ECwrong server Response from Exchange, "
I do have PF on both node then why this pop up.. i do understand if only one node has PF and new connection intiated by outlook connecting to other node which doesn't have PF then it will redirect to the node having PF and while doing so there is
the message.
FYI..
I hve two node server having CAS array and DAG configured on it. keep one thing in mind i am using kemp load balancer for CAS array.
I will appreciate all your help if you elaborate in depth.
Amit Rawat | MCITP - Exchange 2007/2010| CCNA |MCSE- 2003| Lync 2010|http://blog.amitrawat.net

TCP packet out of state: First packet isn't SYN & Outlook is trying to retrieve data from the Microsoft Exchange Server [CAS-ARray]

We are transitioning from Exchange 2003 to Exchange 2010. We found Outlook online mode (non-cached mode) have many warning "Outlook is trying to retrieve data from the Microsoft Exchange Server [CAS-ARray]", usually happen when users tried to open
address book but sometimes even normal operation like click the Send button. The problem does not affect OWA and extremely rare when Outlook is running in cached mode. Check the firewall logs, we notice a lot of "TCP Packet Out of State" drops.
We have a lot from the CAS/HT to DC/GC on TCP_3268 and LDAP. And the errors are "TCP packet out of state: First packet isn't SYN" with tcp_flags FIN-ACK, PUSH-ACK.
We also have a lot from CAS/HT to the Outlook Clients on the static RPC port (TCP_59933). And the errors are "TCP packet out of state: First packet isn't SYN" with tcp_flags FIN-ACK, PUSH-ACK and RST-ACK, ACK.
This happens even on Outlook 2010 which I though it has TCP Keep Alive implmented to keep the session active within 1 hour.
Can somebody tell me if these out-of-state are the cause of our problem? And how to fix it?
THANK 1,000,000

Hello AndyHWC,
I did some consulting with our CAS team and received the following feedback to your post:
It is difficult to determine what is causing resets without seeing the captures first hand however, the concern is that you are seeing dropped packets on the firewall logs. Where is this firewall located?
Based on the description "Check the firewall logs, we notice a lot of "TCP Packet Out of State" drops." and "We have a lot from the CAS/HT to DC/GC on TCP_3268 and
LDAP." indicates to me that the firewall is between CAS and GC. This not supported under any circumstances and would explain the issue they are seeing with clients trying to "retrieve data from the GC".
If there is not a firewall between the GC and CAS then a Microsoft support engineer would need to have concurrent Netmon Captures from client, CAS, GC during the
issue to analyze. If only one GC exists consider adding another GC to handle the client requests and for fault tolerance.
Also verify that all NIC card drivers are updated to the latest driver version
More information about firewalls with Exchange 2007/2010
http://msexchangeteam.com/archive/2009/10/21/452929.aspx
http://technet.microsoft.com/en-us/library/bb232184(EXCHG.80).aspx
You can install the Client Access server role on an Exchange 2007 computer that is running any other server roles except for the Edge Transport server role. You
cannot install the Client Access server role on a computer that is installed in a cluster. Installation of a Client Access server in a perimeter network is not supported.
http://technet.microsoft.com/en-us/library/dd577077(EXCHG.80).aspx
“The Installation of a Client Access Server in a Perimeter Network Is Not Supported
Issue You may want to install an Exchange 2007 Client Access server in a perimeter network. However, this type of installation is not supported in Exchange
2007.
Cause The Exchange 2007 Client Access server role is not supported in any configuration in which a firewall is located between the Client Access server
and a Mailbox server or a domain controller. This includes firewall devices, firewall programs, or any program or device that is designed to restrict traffic between two network locations.
For correct operation, Client Access servers require typical domain connectivity to domain controllers and global catalog servers. Because any devices
or programs that restrict or reduce access to domain controllers or global catalog servers may affect the correct operation of the Client Access server, we do not support this type of configuration.
Resolution To resolve this issue, move the Client Access servers to the internal network. For more information about the ports that Exchange 2007 uses
for various services, see Data Path Security Reference.”
Thanks,
Kevin Ca - MSFT
Kevin Ca - MSFT

"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" in Exchange 2013

In Exchange 2013, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address. This change makes
it much less likely that users will see the dreaded message “Your administrator has made a change to your mailbox.”
http://technet.microsoft.com/en-us/library/dd298114(v=exchg.150).aspx
Although the error message in the topic has been already improved a lot in Exchange 2013, the users may still encounter them in some specific scenarios. We have collected them and let’s discuss them in this thread.
Symptom
=======================================
Consider the following scenario:
Exchange 2013 was installed for a migration from Exchange 2007/2010.
The legacy Exchange server is removed after successful migration.
Exchange 2013 may be updated to Exchange 2013 SP1.
Some users were being randomly prompted with a popup in their outlook client with the following message when connecting with Exchange 2013 server:
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Cause
=======================================
The issue may be caused due to Public Folders.
The msExchHomePublicMDB attribute on Exchange 2013 databases was set to deleted legacy public folder object.
Solution
=======================================
Removed the Public Folder from all the Exchange
2013 Databases. To do it, we can use ADSIedit.msc and remove the arrtibute - msExchHomePublicMDB from all the Databases:
1. Open ADSIEdit.
2. Connect to the Configuration container.3.
Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange
Administrative Group -> CN=Databases.5. In the right hand pane you will see a list of databases.6.
Right-click the listed database object -> Properties.7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database,
please clear the value.8. Click OK.9. Check the rest of the databases to make sure
that they are not populated in the same way.
References:
https://social.technet.microsoft.com/Forums/en-US/2f736bdd-1c00-4a22-97a5-95faeadf1495/exchange-2013-sp1-users-randomly-prompted-with-the-microsoft-exchange-administrator-has-made-a?forum=exchange2010
https://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
https://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This one? http://support.microsoft.com/kb/2934750

The Microsoft Exchange administrator has made a change that requires you to quit and restart outlook.

Then I get this once outlook is open:
Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The operation cannot be performed because the connection to the server is offline".
Outlook 2013 client
Exchange 2010 SBS
I have recreated the profile, doesn't work. Recreating the OST doesn't work. Starting Outlook in any safe mode doesn't work. Disabling hardware acceleration and add-ins does not work.
repair account does not work - I get the Congratulations message, confirming it was able to get everything from the server... and when I restart Outlook:
"The Microsoft Exchange Administrator has made a change that requires you to quit and restart Outlook".
BJN
Also the user in question is not getting new mail.
And I have tried this
outlook /resetnavpane to no avail.

Hi,
Please confirm if the issue happens to all users in your Exchange server.
In client side, please check the Connection Status when the issue occurs:
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection.
Please notice the Server name, status, protocol and Type information.
In Exchange server, please check whether all Exchange services are started and running in Exchange 2010. Also check whether there is any error information in Event Viewer.
If the issue only happens to one user, please update the Outlook client with the latest patches and service packs to have a try.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%).
The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
configured threshold.”
There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20).
From what I can tell, all of the IP addresses are from Taiwan.
The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014).
From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening.
The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
The Error reads:
The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
Recent changes to the system:
About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

Hi,
Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
Thanks,
Simon Wu
TechNet Community Support

"Windows cannot find the microsoft software license terms" Windows 8.1 Installation Error - Parallels

I'm trying to install Windows 8.1 via Parallels on my Macbook Pro.
I create a new VM and use the .ISO file and get the error: "Windows cannot find the microsoft software license terms. Make sure the installation sources are valid and restart the installation."
I found this question was answered here: http://social.technet.microsoft.com/Forums/windows/en-US/b1021d66-9774-4b5b-b50b-ad860c5ecc89/windows-8-enterprise-rtm-installation-error?forum=w8itproinstall
However, following the steps of the solution did not work for me. I created a blank VM and chose Windows 8.1. After this, it asks me to insert the installation disc. I cannot figure out how to use the .ISO as the source at this point. I tried copying and
pasting the path to the file and dragging the file to the VM, but no luck.
If there is a way I can install this without this error message or by somehow getting the path to the .ISO that'd be perfect.

Hi,
According to your description, I would like to confirm if you have unchecked the Express installation box.
Be sure to uncheck 'Express Installation' when installing, otherwise Windows setup will fail with an error "cannot find license terms" and get stuck in a reboot cycle.
I suggest you refer to the following link to use Parallels Desktop to install Windows 8.1.
Using Parallels Desktop to install Windows and the dev tools on your Mac:
http://msdn.microsoft.com/en-us/library/windows/apps/jj945424.aspx
Regards,
Kelvin hsu
TechNet Community Support

Double prompts for Exchange 2013 migrated users: "The microsoft exchange administrator has made a change that requires you to restart outlook"

I have Exchange 2010 SP3 in my environment and am migrating to Exchange 2013. Whenever a mailbox is migrated, the Outlook 2013 client will prompt the user with a "the exchange administrator has made a change that requires you to restart
Outlook". When the user does so, he or she is prompted again. After he or she closes and reopens Outlook for the second time, the issue is gone permanently.
I've seen a number of other posts about repeated prompts like this but I haven't yet found one or someone gets exactly 2 prompts for each client and no more.
A couple of pieces of information that may be relevant:
1. On exchange 2013, the authentication method for the internal host name is NTLM
2. I have not yet migrated public folders from Exchange 2010. I plan to do that after the mailbox migration is complete.
Thanks in advance for your help.

Hi,
From your description, after mailboxes are moved from Exchange 2010 to Exchange 2013, users receive the following prompt when opening Outlook.
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
In order to solve this issue, you need to apply the Outlook update that is described in KB 2863911.
For your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
https://support.microsoft.com/kb/2934750?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. Event 1121

Hello all,
We migrated our Exchange server from 2003 to 2010. After the mailbox move requests were finished we had one that was stuck. We basically skipped it as we had a lot of other things to finish over the weekend. Here we are a year later, the old exchange server
is gone and so is an old DC. I am receiving an error every four minutes in event viewer.
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '3e46b7cb-2ac0-42c1-98e8-57517a19ee40'
Database GUID: '5c6c573b-4f45-4ce3-b296-11cf69c2e2b6'
Error: Unable to find 'OLD Domain Controller' computer information in domain controller 'OLD Domain Controller' to perform the suitability check. Verify the fully qualified domain name..
I have checked in EMC for move requests. None are listed. I have checked the DCs listed in EMC properties. Old DC is not listed.
I also ran these commands in shell to attempt to cancel the stuck request.
Get-MoveRequest -MoveStatus Completed;Pending;InProgress;Failed;CompletedWithWarning;Suspended;Queued;CompletionWithProgress : Remove-MoveRequest
NO changes. Still throwing error. Any suggestions? I also tried using the guid and shell to look at the move request. Systems replies no such request.

Hello,
Please try to restart iis services to check the result.
If the issue persists, I recommend you ping you DC server on your exchange server to check if your exchange server can communicate with your DC server.
If there are other DCs, please try to use set-adserversettings cmdlet to specify a DC for your exchange server.
Set-AdServerSettings
http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
Besides, please install the lasted rollup to check the result.
Cara Chen
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs. I had a similar problem which I solved by removing some old migration batches, now I have a problem
with the Microsoft Exchange Mailbox Replication service.
The event logged is:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
configured incorrectly DNS server.
The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring. When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
How can I stop these events occurring and is it likely to be causing something else not to work correctly.
We are running Exchange 2013 CU1

No, that didn't work. Here are more details:
Source: MSExchange ADAccess (EventID: 2130)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
incorrectly DNS server.
Source: MSExchange ADAccess (EventID: 2119)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
Common causes of this error include the following:
- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
at set intervals. This computer is configured to use DNS servers with following IP addresses:
10.59.100.7
10.59.100.8
fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
- One or more of the following zones do not include delegation to its child zone:
admin.riddlesdown.local
riddlesdown.local
local
. (the root zone)
Source: MSExchange Mailbox Replication Service (EventID: 1121)
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
--> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Something is cause the Exchange server to go looking for our old domain, but what and why?

Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed

Each time I restart this exchange server, the Information Store and System Attendant don't start. If It try to manually start the services, I get the follow errors:
Event ID 5003:
Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online.
Event ID 1005:
Unexpected error The clocks on the client and server machines are skewed. ID no: 80090324 Microsoft Exchange System Attendant occurred.
The clocks on the domain controllers and the exchange server are set to the same time zones. As well, all three clocks are in sync down to the second. Any ideas on what's causing this and how to fix it?

Run this Command from the Exchange Server
Net time \\ADServerName /Set
and confirm the action,
and then you need to restart the service
Microsoft Exchange Active Directory Topology Service
and confirm you are not getting the Error 4001 in the event Viewer.
Thank you, it resolved my issue after being sweating looking for solution.
How can I prevent this from happening? I cannot restart services on each server reboot nor lose 5 years of my life!!!
Sokratis Laskaridis MCP, MCTS, MCITP, Small Business Specialist Netapp ASAP, Symantec STS

Cannot install the Microsoft Exchange connectivity analysis tool

Similar Messages

Maybe you are looking for