The administrator has made changes that requires Outlook to be restarted.

We are running on premise Exchange 2013 (Upgraded from Exchange 2010). Our Outlook anywhere clients (Me being one of them) are constantly getting this pop up, some more then others.
"The administrator has made changes that requires Outlook to be restarted."
I have looked around and there are a lot of references to corrupt OST files and recently mailbox moves. My mailbox has been moved for several months now, and I am not using cached mode, however I do have a 16MB OST file on this particular computer
(I get this message on the 3 computers I use regularly, all of them do not have cache mode)
We only seem to get this message on Outlook 2013, I have downgraded a computer to 2010 and I do not get the message. I believe that we started getting this message shortly after we removed the Exchange 2010 server from our organization, however I cannot
be certain
any thoughts?? I get the message at least every 30-60 minutes :)

Hello,
Normally, if you move a mailbox, the profile has to get updated somehow, and outlook is updated automatically, but it does require a restart.
I recommend you follow the NetoMeter's suggestion to check the result.
If you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Similar Messages

Random message "The microsoft exchange administrator has made changes that requires you quit and restart Outlook"

Hello everyone,
I have read a lot of subject on technet forums and others but I don't find the solution to my issue.
So I explain my problem:
I have 2 different clients with Exchange Server 2013 Standard installed on a Windows Server 2012 Standard that have the message that ask to restart outlook. I try to install SP1 on one of my client but without success. So I let the second one in CU3.
The message appears on Outlook 2013 and 2010. Some have cache enabled and other not.
I try to recreate profile, change different settings, delete OST file and recreate it, enable and disable cache,...
There is no cluster, no load balancing and no replication between different exchange servers.
This message appeared without I make changes. (It started approximately at the same time for the 2 clients).
I have other client in the same configuration that has not this message.
Thank you in advance
Quentin Liégeois

I am experiencing the same problem! And am looking for a solution for about 2 days now.
We have an Exchange 2013 DAG cluster with a hardware load balancer. We also have a mixed set of clients, Office 2010 and 2013.
We enabled the advanced logging option on an outlook client until the message appears, after that we disabled the logging.
The created ETL files can be viewed with Eventviewer but unfortunattly there is no usable data logged for troubleshooting.
The strange thing is, that it is completely random, sometimes users get a message the whole day, and sometimes it works for 2 days. We have tried several client types, VDI, Fat client, manual installation, all without any GPO except the default domain
gpo.
Marcel

"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

Exchange 2013 SP1 users randomly prompted with "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"

I got a call to check an issue with a Exchange Server 2013 SP1 environment recently. All server was upgraded from Exchange server 2013 CU2 to Exchange Server 2013 SP1. It was done successfully but many users were being randomly prompted with a popup in their outlook
client with the following message:-
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Although there wasn’t any changes of late in the environment there were random popups like these for multiple users. As the behaviour was not consistent and effecting the entire upgration population
Please suggest us how to resolve the issue.
Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Hi,
Does the issue happen to all Outlook 2013 users? Please create a new Outlook profile to have a try.
If it fails, please check the msExchHomePublicMDB value in ADSI Edit:
1. In Adsiedit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
2. Right-click the listed database > Properties.
3. Check whether the msExchHomePublicMDB value is set to an available value. Please change the value to <not set>.
4. Click OK.
Then check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

2013 SP1 problem - the microsoft exchange administrator has made a change that requires you quit and restart outlook

I've looked at other answers to this problem but they seem to relate to multi server environments or new migrations - neither apply here. The Exchange 2013 server was implemented last year as a migration from Exchange 2007. It has been running well since.
I upgraded to SP1 on Sunday night and since then all users, regardless of Outlook version, are continually being asked to "the microsoft exchange administrator has made a change that requires you quit and restart outlook". Clicking OK loads Outlook
normally (no restart). I can delete the Outlook profile and set up a new profile OK but the issue comes back again. Deleting the users roaming or local profile does not help either.
The CAS seems to be set correctly - when I run Get-MailboxDatabase | fl RpcClientAccessserver it returns the correct server.
There are no public folders set up.

Thanks for the update. It was the PF that caused the issue.
When I removed the old Exchange 2010 server it did not remove everything for AD. Had to manually remove the older sever.

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

Hi
We have 2 separate Exchange 2013 organisations in Our Company. All mail comes in on the first server registered With domain1.com and if it is mail Connected to the second server it is forwarded to server 2 which is registered With domain2.com.
When the users Connected to server 2 sends out mail they have default mail address firstname.lastnameATdomain1.com so the default address policy points to an email address registered on server 1. We have added a GPO for the domain2 users so that
Autodiscovery updates with the right domain name.
The problem is that every time a user With Outlook 2013 starts Outlook he gets an error saying "The Exchange administrator has made a change that requires you quit and restart outlook". This Message shows about every 10 minutes in Outlook. I think
this has to do With the autodiscover settings, but I'm not sure.
Any Idea how to remove this Message?
Regards
Anders

Hi,
From your description, I recommend you follow the steps below to repair the Exchange email account and check the result.
1. Start Outlook. Click File, Account Settings, and then click Account Settings.
2. With the Exchange email account selected, click Repair. In the Repair Account dialog box, click Next.
3. After the configuration finishes, restart Outlook.
After you restart Outlook, the status bar may show your status as Working Offline. To connect it, click the Send/Receive tab, and then click Work Offline to turn off this feature.
Hope this can be helpful to you.
Best regards,
Amy Wang
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

The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook. plus more!!!!

We just migrated our 2010 exchange running off a sbs to exchange 2013 running on server 2012 standard. The issues we are having is if you shutdown the old sbs server mail flow stops completly. The other issues is that clients using outlook 2013 get the
popup message "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook." We have remade their profiles on the local computer, uninstsalled Office and reinstalled it... tried almost everything. The exchagne
server is on CU5 and no changes have been made in the last two months.

... if you shutdown the old sbs server mail flow stops completely.
If the inbound flow is affected, check the firewall (or antispam/andivirus device/server) configuration. Most probably, it is still forwarding the inbound email to the SBS.
In case the outbound email stops, check the Internet Send connectors. It's quite possible that you don't have an Internet Send connector with the Exchange 2013 specified as a source server. If this is not the case, check again the firewall - it might be
blocking outbound traffic on port 25 from the Exchange 2013 internal IP address.
... clients using outlook 2013 get the popup message "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook."
Are the clients fully updated, or at least, running
Office 2013 SP1
Step by Step Screencasts and Video Tutorials

The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook - error message

I applied Exchange Server 2013 SP1 and since then some users are getting error message:
'The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook' on their MS Outlook.
Have tried a number of options including repairing the affected user accounts to no avail.
Any idea on how to resolve this will be appreciated.
NB: This error was not there before applying SP1.

kindly need help. i have same message "'The Microsoft Exchange Administrator has made a change that requires
you quit and restart Outlook' on their MS Outlook"
this is comes after applying 2013 sp1

Error: "The search cannot be executed because the table has pending changes that would be lost."

Hello,
I'm working a developing an OA page that will displays the contents of an Oracle table and allows the user to update records in a table as needed.
When I hit submit button to save the changes in the update page, the control goes back to main page (where all the table records are displayed). It displays the updated record with the new information.However when I hit "Go" button on the mainPG, I get the error "The search cannot be executed because the table has pending changes that would be lost. and the changes are not committed.
ANy suggestions on where I should look will be greatly appreciated.
Posting code for my controller
=======================
          if ( pageContext.getParameter("saveRate") != null )
          personam.invokeMethod("saveRateToDatabase");
Code from my AM
=============
    public void saveRateToDatabase()
      getOADBTransaction().commit();
      System.out.println("40--After commit has been executed");
Code from my VORowImpl
===================
package cggv.oracle.apps.gl.server;
import oracle.apps.fnd.framework.server.OAViewRowImpl;
import oracle.jbo.domain.Date;
import oracle.jbo.domain.Number;
import oracle.jbo.server.AttributeDefImpl;
// ---    File generated by Oracle ADF Business Components Design Time.
// ---    Custom code may be added to this class.
// ---    Warning: Do not modify method signatures of generated methods.
public class xxCggGlRatesVORowImpl extends OAViewRowImpl {
    public static final int RATEID = 0;
    public static final int FROMCURRENCY = 1;
    public static final int TOCURRENCY = 2;
    public static final int FROMCONVERSIONDATE = 3;
    public static final int TOCONVERSIONDATE = 4;
    public static final int USERCONVERSIONTYPE = 5;
    public static final int CONVERSIONRATE = 6;
    public static final int MODEFLAG = 7;
    /**This is the default constructor (do not remove)
    public xxCggGlRatesVORowImpl() {
    /**Gets the attribute value for the calculated attribute RateId
    public Number getRateId() {
        return (Number) getAttributeInternal(RATEID);
    /**Sets <code>value</code> as the attribute value for the calculated attribute RateId
    public void setRateId(Number value) {
        setAttributeInternal(RATEID, value);
        //populateAttribute(RATEID, value);
    /**Gets the attribute value for the calculated attribute FromCurrency
    public String getFromCurrency() {
        return (String) getAttributeInternal(FROMCURRENCY);
    /**Sets <code>value</code> as the attribute value for the calculated attribute FromCurrency
    public void setFromCurrency(String value) {
        setAttributeInternal(FROMCURRENCY, value);
    /**Gets the attribute value for the calculated attribute ToCurrency
    public String getToCurrency() {
        return (String) getAttributeInternal(TOCURRENCY);
    /**Sets <code>value</code> as the attribute value for the calculated attribute ToCurrency
    public void setToCurrency(String value) {
        setAttributeInternal(TOCURRENCY, value);
    /**Gets the attribute value for the calculated attribute FromConversionDate
    public Date getFromConversionDate() {
        return (Date) getAttributeInternal(FROMCONVERSIONDATE);
    /**Sets <code>value</code> as the attribute value for the calculated attribute FromConversionDate
    public void setFromConversionDate(Date value) {
        setAttributeInternal(FROMCONVERSIONDATE, value);
    /**Gets the attribute value for the calculated attribute ToConversionDate
    public Date getToConversionDate() {
        return (Date) getAttributeInternal(TOCONVERSIONDATE);
    /**Sets <code>value</code> as the attribute value for the calculated attribute ToConversionDate
    public void setToConversionDate(Date value) {
        setAttributeInternal(TOCONVERSIONDATE, value);
    /**Gets the attribute value for the calculated attribute UserConversionType
    public String getUserConversionType() {
        return (String) getAttributeInternal(USERCONVERSIONTYPE);
    /**Sets <code>value</code> as the attribute value for the calculated attribute UserConversionType
    public void setUserConversionType(String value) {
        setAttributeInternal(USERCONVERSIONTYPE, value);
    /**Gets the attribute value for the calculated attribute ConversionRate
    public Number getConversionRate() {
        return (Number) getAttributeInternal(CONVERSIONRATE);
    /**Sets <code>value</code> as the attribute value for the calculated attribute ConversionRate
    public void setConversionRate(Number value) {
        setAttributeInternal(CONVERSIONRATE, value);
    /**Gets the attribute value for the calculated attribute ModeFlag
    public String getModeFlag() {
        return (String) getAttributeInternal(MODEFLAG);
    /**Sets <code>value</code> as the attribute value for the calculated attribute ModeFlag
    public void setModeFlag(String value) {
        setAttributeInternal(MODEFLAG, value);
    /**getAttrInvokeAccessor: generated method. Do not modify.
    protected Object getAttrInvokeAccessor(int index,
                                           AttributeDefImpl attrDef) throws Exception {
        switch (index) {
        case RATEID:
            return getRateId();
        case FROMCURRENCY:
            return getFromCurrency();
        case TOCURRENCY:
            return getToCurrency();
        case FROMCONVERSIONDATE:
            return getFromConversionDate();
        case TOCONVERSIONDATE:
            return getToConversionDate();
        case USERCONVERSIONTYPE:
            return getUserConversionType();
        case CONVERSIONRATE:
            return getConversionRate();
        case MODEFLAG:
            return getModeFlag();
        default:
            return super.getAttrInvokeAccessor(index, attrDef);
    /**setAttrInvokeAccessor: generated method. Do not modify.
    protected void setAttrInvokeAccessor(int index, Object value,
                                         AttributeDefImpl attrDef) throws Exception {
        switch (index) {
        case RATEID:
            setRateId((Number)value);
            return;
        case FROMCURRENCY:
            setFromCurrency((String)value);
            return;
        case TOCURRENCY:
            setToCurrency((String)value);
            return;
        case FROMCONVERSIONDATE:
            setFromConversionDate((Date)value);
            return;
        case TOCONVERSIONDATE:
            setToConversionDate((Date)value);
            return;
        case USERCONVERSIONTYPE:
            setUserConversionType((String)value);
            return;
        case CONVERSIONRATE:
            setConversionRate((Number)value);
            return;
        case MODEFLAG:
            setModeFlag((String)value);
            return;
        default:
            super.setAttrInvokeAccessor(index, value, attrDef);
            return;
    /**Gets xxCggGlRatesEO entity object.
    public xxCggGlRatesEOImpl getxxCggGlRatesEO() {
        return (xxCggGlRatesEOImpl)getEntity(0);

Hi,
Check these links:
Oracle Apps: Search cannot be executed because the table has pending changes that would be lost
Re: Getting error in search page search cannot be executed
http://jneelmani.blogspot.in/2009/11/oaf-search-cannot-be-executed-because.html
--Sushant

"Error:The search cannot be executed because the table has pending changes that would be lost", after DELETE

Good day,
On Search Page, I have searched for the record(s) then deleted a record and got confirmation message i.e. Record has deleted. Next when I search for any record I'm getting below error.
Error
The search cannot be executed because the table has pending changes that would be lost.
Could you please help me to fix this issue. Your response is highly appreciated.
Item properties:
Item Style : Image
Action Type: Fire Action
Event : delete
Below is the code using in CO and AM
Controller (processFormRequest):
if ("delete".equals(pageContext.getParameter(EVENT_PARAM)))
          // The user has clicked a "Delete" icon so we want to display a "Warning"
          // dialog asking if she really wants to delete the employee. Note that we
          // configure the dialog so that pressing the "Yes" button submits to
          // this page so we can handle the action in this processFormRequest( ) method.
          String visit_id = pageContext.getParameter("visit_id");
          String employeeName = pageContext.getParameter("last_name") + ", " + pageContext.getParameter("first_name");
          MessageToken[] tokens = { new MessageToken("EMP_NAME", employeeName)};
          OAException mainMessage = new OAException("FND", "XXXX_EMP_DELETE_WARN", tokens);
          // Note that even though we're going to make our Yes/No buttons submit a
          // form, we still need some non-null value in the constructor's Yes/No
          // URL parameters for the buttons to render, so we just pass empty
          // Strings for this.
          OADialogPage dialogPage = new OADialogPage(OAException.WARNING,
            mainMessage, null, "", "");
          // Always use Message Dictionary for any Strings you want to display.
          String yes = pageContext.getMessage("AK", "FWK_TBX_T_YES", null);
          String no = pageContext.getMessage("AK", "FWK_TBX_T_NO", null);
          // We set this value so the code that handles this button press is
          // descriptive.
dialogPage.setOkButtonItemName("DeleteYesButton");
          // The following configures the Yes/No buttons to be submit buttons,
          // and makes sure that we handle the form submit in the originating
          // page (the "Employee" summary) so we can handle the "Yes"
          // button selection in this controller.
dialogPage.setOkButtonToPost(true);
dialogPage.setNoButtonToPost(true);
dialogPage.setPostToCallingPage(true);
          // Now set our Yes/No labels instead of the default OK/Cancel.
dialogPage.setOkButtonLabel(yes);
dialogPage.setNoButtonLabel(no);
          // We need to keep hold of the employeeNumber and employeeName.
          // The OADialogPage gives us a convenient means
          // of doing this. Note that the use of the Hashtable is
          // most appropriate for passing multiple parameters. See the OADialogPage
          // javadoc for an alternative when dealing with a single parameter.
          java.util.Hashtable formParams = new java.util.Hashtable(1);
formParams.put("visit_id", visit_id);
formParams.put("empName", employeeName);
dialogPage.setFormParameters(formParams);
          pageContext.redirectToDialogPage(dialogPage);
    else if (pageContext.getParameter("DeleteYesButton") != null)
          // User has confirmed that she wants to delete this employee.
          // Invoke a method on the AM to set the current row in the VO and
          // call remove() on this row.
          String employeeNumber = pageContext.getParameter("visit_id");
          String employeeName = pageContext.getParameter("empName");
          Serializable[] parameters = { employeeNumber };
         // OAApplicationModule am = pageContext.getApplicationModule(webBean);
am.invokeMethod("deleteEmployee", parameters);
          // Now, redisplay the page with a confirmation message at the top. Note
          // that the deleteEmployee() method in the AM commits, and our code
          // won't get this far if any exceptions are thrown.
          MessageToken[] tokens = { new MessageToken("EMP_NAME", employeeName) };
          OAException message = new OAException("FND",
            "XXXX_EMP_DELETE_CONFIRM", tokens, OAException.CONFIRMATION, null);
pageContext.putDialogMessage(message);
Application Module:
public void deleteEmployee(String visit_id)
        // First, we need to find the selected employee in our VO.
        // When we find it, we call remove( ) on the row which in turn
        // calls remove on the associated EmployeeEOImpl object.
        int empToDelete = Integer.parseInt(visit_id);
          OAViewObject vo = (OAViewObject)getNonEmployeesSummaryVO1();
    NonEmployeesSummaryVORowImpl row = null;
        // This tells us the number of rows that have been fetched in the
        // row set, and will not pull additional rows in like some of the
        // other "get count" methods.
       int fetchedRowCount = vo.getFetchedRowCount();
        // We use a separate iterator -- even though we could step through the
        // rows without it -- because we don't want to affect row currency.
        RowSetIterator deleteIter = vo.createRowSetIterator("deleteIter");
if (fetchedRowCount > 0)
          deleteIter.setRangeStart(0);
          deleteIter.setRangeSize(fetchedRowCount);
          for (int i = 0; i < fetchedRowCount; i++)
            row = (NonEmployeesSummaryVORowImpl)deleteIter.getRowAtRangeIndex(i);
            // For performance reasons, we generate ViewRowImpls for all
            // View Objects. When we need to obtain an attribute value,
            // we use the named accessors instead of a generic String lookup.
            // Number primaryKey = (Number)row.getAttribute("EmployeeId");
            Number primaryKey = row.getVisitId();
            if (primaryKey.compareTo(empToDelete) == 0)
              // This performs the actual delete.
              row.remove();
                getTransaction().commit();
              break; // only one possible selected row in this case
        // Always close the iterator when you're done.
        deleteIter.closeRowSetIterator();
      } // end deleteEmployee
Thanks,
Ravi

Hi
Check this link Getting error in search page search cannot be executed
Regards,
Dilip

The Administrator has made a change

Hi!
We are running Exchange 2013 together with Outlook 2013.
After installing Exchange SP1, the following messages appears on all clients:
"The Exchange admin has made a change that requires you to restart Oulook"
This appears when starting Outlook, and also at random intervals when Outlook is running. I have tested to recreate a profile on the client, but this doesn't help. And the message did not apear before Exchange 2013 SP1.
What can I to to make this disapear?
Regards,
Lennart

Hi Lennart,
Is this a pure Exchange 2013 environment or con-existence with Exchange 2010/2007 servers? Did you do any other changes besides the SP1 update?
Please check in ADSIEdit > Configuration >CN=Services > CN=Microsoft Exchange > CN=your ORG name > CN=Administrative Groups > CN=Exchange Administrative Group >
CN=Databases, please check the attribute “MSEXCHHomePublicMDB” of your databases, if they are pointing towards the deleted Objects, please delete the entries.
You can also check the RPC Client Access logs (Exchange Server\V15\Logging\RPC Client Access) to find if any errors happened.
Best Regards,
Tracy Liang

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

I've looked and looked again and cannot find any solution to this issue...There are plenty of posts related to this error message however none of the resolutions work for me.
We have a cluster of 3 MS Exchange Server 2010 SP2 RU2 machines with CAS, HT and Mailbox roles installed on all 3. Those 3 machines form a DAG and are behind a CAS Array. This is done using a pair of Riverbed
Stingray Traffic Manager appliances.
The above error message keeps popping up randomly on my users' workstations running Outlook 2010 with cache mode enabled (Outllok 2007 users do not have this issue). It pops up when nothing is being done to the platform...i.e. I'm not moving any mailboxes,
not activating nor suspending any mailbox databases, not updating the rpcclientaccessserver attribute on any databases (that property is configured correctly on all my databases...). We have SP2 RU2 installed which means that the message should only pop up
if the conditions in
THIS ARTICLE are observed and none of them are when our users see the message...
Next thing on my elimination process is the load balancers...I've read about some admins having this issue when using Barracuda LBs for their CAS array (see
this thread). I thought about session persistence settings not working properly but after some testing I figured out it doesn't make any difference if I use 'Source IP' or 'Cookie Based' as my persistence method for various services (OWA, MAPI, etc). The
end users still see the message popping up randomly. Can anyone confirm Source IP is better? Or shall I stick with Cookie based for OWA services? Also I'm offloading SSL on the load balancers but I fail to see how this would be a problem. It's configured OK
as per MS' SSL offloading guidance.
Those users use Public Folders and my PF store reside on one of our servers only (as we are in a DAG). Because we have all 3 roles installed on all 3 servers, users can potentially connect to either 3 (if we assume that session persistence is not working
properly). Could this be an issue?
The pop ups are so random that I'm running out of ideas on how to troubleshoot this...
Has anyone got any idea at all?
Other things I've tried or checked:
- tested Outlook connectivity OK
- modified pool and service settings on my load balancers to check if those triggered the pop up, to no avail (only when I switch the main virtual IP from one traffic manager to the other the message pops up, but that is to be expected!)
- tried disabling the 'show Exchange messages' option on the client side (which is obviously not ideal...but the pop up still occurs anyway)
Regards, Raphael

I have left a laptop on for a number of days with a test account logged in to Outlook 2010 (with modified hosts file to bypass the load balancers, e.g. always hit the same node). The message never popped up. This can certainly be a clue however unfortunately
it doesn't 100% mean that the issue comes from the LBs as some users get the message randomly with sometimes more than 2 weeks apart...
Another thing that we thought maybe a problem is we have noticed that this problem occurs more for people with laptops with both Ethernet and Wifi adapters plugged in at the same time. Those users un-dock their laptop to go to a meeting for example, and
the wireless connection kicks in, then dock it back in to their docking station and the wireless connections stays on, as well as their Ethernet one. This sometimes changes the state of their Outlook connection status from TCP/IP to HTTPS and vice versa. This
also depends on if the office LAN is running slow or not at the time. But surely I would have thought switching client IP address all the time may be an issue? Does anyone know if this could be a problem when connecting to a CAS Array/DAG Exchange platform?
On the other hand I have tested having both connections on on that test laptop and the message never popped up. But yet again I was bypassing the load balancers.
Their RPC over HTTPS Exchange Proxy Settings are all set with:
- On fast networks connect using HTTP first then TCP/IP - disabled
- On slow networks connect using HTTP first then TCP/IP - enabled
I have a case open with our load balancer vendor and their Exchange expert is supposed to get in touch with me to review all the settings and Exchange config. I'll update this ticket if we can find more clues, or ideally, a solution to this issue!
Hi Greg,
I do face the same problem - running two node E14 SP2 RU2 DAG after moving 2600 mailboxes last weekend. We bypass the F5 already - still the same issue using Outlook 2003/2007/2010 clients where randomly choosen ones do get the restart outlook message (at
least we couldn't find a pattern). Also clients with mailboxes moved three weeks ago are affected. Both E14 multirole (C/H/M) have a replica for PF. There is one Exchange 2003 two cluster node left with around 350 mailboxes. Could it be caused by some sort
of Outlook Add-In?
many thanks
tiZ.A: Thanks for giving me some sanity back :-) I'm not the only one to whom this happens! do you know that moving mailboxes between databases is one of the legitimate reasons why this message would pop up for? (ref: http://blogs.technet.com/b/exchange/archive/2011/01/24/3411868.aspx)
The strange thing is that for you it doesn't seem to happen for ALL your mailbox users, but just random ones? Also we only have noticed this issue with Outlook 2010 clients ONLY. No 2003/2007 ones.
Regards, Raphael

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

One Exchang 2013 user gets "The Microsoft Administrator has made a change that requires you to quit and restart Outlook" each time his desktop is rebooted.

I recently migrated all of my users from Exchange 2007 to 2013. One Outlook user gets this prompt each time he opens Outlook after rebooting his desktop. He gets it after every reboot.
I tried re-creating his Outlook profile and that did not resolve the issue. I also tried to create an Outlook profile for him on a different desktop and got the same message.

any help from:
http://social.technet.microsoft.com/Forums/exchange/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

The administrator has made changes that requires Outlook to be restarted.

Similar Messages

Maybe you are looking for