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

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

  • Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f.

    PLease help, I've rstored from backup three times with no success I'm getting the following error
    "Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f. "
    It's LDap related but i have no idea why :-(
    Best Regards Bernhard

    IPv6 had been disabled for months on my SBS 2008 Server running Exchange 2007 SP1.  I ran 40 or so Windows Updates; subsequently, the next morning Exchange was no longer running; topology issues, event ID 2604, 2114 and 2601 were all over my Application
    Log.  After 12 hours of research I found this post; figured it was worth a shot and instantly all my services for Exchange fired up.  Thanks for the tip; I have no idea which update changed what in regards to needing IPv6 enabled, but that silly
    little check mark fixed it.  
    Thank you for sharing your solution! 
    Dan

  • RPC request to the Microsoft Exchange Information Store service for log truncation

    Hello all
    Running Exchange 2013 CU3 on Windows 2008R2 sp1 in a two node DAG. We are seeing the bellow warning when running a backup. How to resolve this?
    RPC request to the Microsoft Exchange Information Store service for log truncation failed for database CoramB3\Servername. Error: Failed to notify source server 'servername.coram.com' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find
    the file. Also log files are not being flushed
    Bulls on Parade

    Hello,
    Please verify backup software.
    Please use vssadmin list writers command to check the status of the VSS admin. If it is in a
    failed state, please restart the Exchange replication service and then check the status again.
    Please use Get-MailboxDatabaseCopyStatus cmdlet to view health and status information about mailbox database copies.
    Please use Get-DatabaseAvailabilityGroupNetwork “DAG Name” | fl cmdlet to view configuration and state information for a DAG network.
    Please use Get-DatabaseAvailabilityGroupNetwork DAG Name\MAPINetwork | fl cmdlet and Get-DatabaseAvailabilityGroupNetwork DAG Name\ReplicationNetwork | fl cmdlet to
    check configuration information for MAPI network and Replication Network.
    If the above configuration information is ok, please check if there are other related errors in application log.
    Cara Chen
    TechNet Community Support

  • #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error.

    Hi, 
    I created a mailbox few days before, everythign was working fine and suddenly when some one tried to send email on that mailbox it bounced back with following error:
    There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
    Sent by Microsoft Exchange Server 2007 
    Diagnostic information for administrators:
    Generating server: Mail01.abc.com
    [email protected]
    #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:9A000000, 17.27161:00000000CC000000000000000600000000000000,
    255.23226:00000000, 255.27962:FE000000, 255.17082:0F010480, 0.26937:94000000, 4.21921:0F010480, 255.27962:FA000000, 255.1494:00000000, 255.26426:FE000000, 4.7588:0F010480, 4.6564:0F010480, 2.17597:00000000, 2.25805:00000000, 4.8936:0F010480, 4.14312:0F010480,
    4.2199:0F010480, 2.25805:00000000, 4.8936:0F010480, 2.22957:00000000, 2.19693:00000000, 2.17917:00000000, 2.27341:00000000, 4.8936:0F010480, 4.17097:0F010480, 4.8620:0F010480, 255.1750:0F010480, 0.26849:0F010480, 255.21817:0F010480, 0.26297:0F010480, 4.16585:0F010480,
    0.32441:0F010480, 4.1706:0F010480, 0.24761:0F010480, 4.20665:0F010480, 0.25785:EC030000, 4.29881:0F010480". ##
    Original message headers:
    Received: from Mailbox.abc.com ([fe80::892d:93d6:b1ac:b70a]) by mail01
     ([10.72.0.95]) with mapi; Fri, 11 Jan 2013 14:04:55 +0500
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: Anwar Amjad <[email protected]>
    To: All-HEC <[email protected]>
    Date: Fri, 11 Jan 2013 14:04:53 +0500
    Subject: FW: Suggestions & New Arrival in HEC Library
    Thread-Topic: Suggestions & New Arrival in HEC Library
    Thread-Index: Ac3vHgwR50OLs2BnQuOzo9jWg4e1gQAvJtUw
    Message-ID: <[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <[email protected]>
    MIME-Version: 1.0
    X-Auto-Response-Suppress: DR, OOF, AutoReply
    After this error, i treid to send email again and there is no error and email was delivered. What was the cause of this error?
    Hasan

    Hi,
    I tried to start seeding again but it is at same status. I will try again and hopefully it will get resolved.
    But, yesterday i ran in to the most complex issue i have ever seen with Exchange.
    There was a unexpected power cut at our datacentre due to which both the nodes went down.
    After that both the nodes came up. But the all 3 databases were dismounted.
    Therefore, i ran Eseutil /mh resulting dirty shutdown.
    I was able to repair 2 databases.
    But the 3rd one was not mounting with below error.
    Microsoft Exchange Error
    Failed to mount database 'Mailbox Database'.
    Mailbox Database
    Failed
    Error:
    Exchange is unable to mount the database that you specified. Specified database: XXXXX\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216).
    I was able to mount database somehow. There are 7 User mailboxes (Tier 1) on this database.
    All emails sent to the users in this database are bouncing back with the below error.
    This storage groups holds the mailboxes of my Senior Managements. And their mailboxes are down for almost 20 Hrs. I am spinning my head since yesterday but not able to find any fix. Can you please guide me in this concern.
    Best Regards
    K2
    Kapil Kashyap

  • Microsoft Exchange Information Store Service Utilizing High Memory

    Hi All,
    i have 2 Mailbox role server in DAG, the DB mounter server always utilizing high memory up to 98% by store.exe services. currently i am running with 24GB Physical Memory.
    when ever it goes to high memory i need to restart the store.exe services then, it will come back to normal 50% later slowly it will move to 86% like that. anyway where we can restrict or manage store.exe to utilize available memory.
    i am running with exchange 2010 SP1.
    srini

    Hi Andy,
    yes, its working as per normal, but i wanted to understand why all of sudden its utilizing all RAM and there is not available memory to perform anything else. due to this its always trigger alert notification based on my monitoring.
    Thanks.
    srini
    What is the server not able to do? What is affected?
    You can limit mem usage, but generally its not generally needed or recommended.
    However, if you have technical requirement to do that, you can:
    https://social.technet.microsoft.com/Forums/exchange/en-US/b7b2f9d9-4370-4984-8713-dc1d52a68105/how-to-reduce-memory-utilization-of-exchange-server-2010?forum=exchangesvradminlegacy
    http://www.bursky.net/index.php/2012/05/limit-exchange-2010-memory-use/
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • 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. : Error: An Active Directory Constraint Violation error occurred

    Hello,
    We have a multi domain parent child AD domain infrastructure and now we upgraded our exchange from Exchange 2007 to Exchange 2013. Since last few days, we see the below error on the mailbox server event viewer.
    EVENT ID : 1121
    The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. 
    Request GUID: '93a7d1ca-68a1-4cd9-9edb-a4ce2f7bb4cd' 
    Database GUID: '83d028ec-439d-4904-a0e4-1d3bc0f58809' 
    Error: An Active Directory Constraint Violation error occurred on <domain controller FQDN>. Additional information: The name reference is invalid. 
    This may be caused by replication latency between Active Directory domain controllers. 
    Active directory response: 000020B5: AtrErr: DSID-0315286E, #1:
    Our Exchange setup is in parent domain, but we keep on getting this error for various domain controllers in each child domain in the same site. We then configured one of the parent domain domain controller on Exchange. Still we are getting this error for
    the configured parent domain DC.
    Verified the AD replication and there is no latency or pending stuffs.
    Any support  to resolve this issue will be highly appreciated. Thank you in advance.
    Regards,
    Jnana R Dash

    Hi,
    In addition to Ed's suggestion, I would like to clarify the following things for troubleshooting:
    1. Please restart IIS at first.
    2. If the issue persists, please ping your DC on your Exchange server to check if Exchange can communicate with DC.
    Hope it helps.
    Best regards,
    Amy Wang
    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?

  • Exchange information store service is not starting on exchange 2010

    i've run the updates on the exchange 2010 and restart the servers, after one week i've restart the 2003 dc and exchange 2010. now exchange information store service is not starting on exchange 2010 and the database are dismounted
    help pls

    I have just installed Exchange 2010 on my system and when trying to mount the database it fails.  The Information Store service will not start on my server.  Time is in sync with the DC and the initial install went fine.  I have the following
    from event viewer:
    Cmdlet failed. Cmdlet Mount-Database, parameters {Identity=dellstslab}.
    details
    System
    Provider
    Name]
    MSExchange
    CmdletLogs
    EventID
    6
    Qualifiers]
    49152
    Level
    2
    Task
    1
    Keywords
    0x80000000000000
    TimeCreated
    SystemTime]
    2014-02-18T16:43:34.000000000Z
    EventRecordID
    107
    Channel
    MSExchange
    Management
    Computer
    Exchange2010.dellstslab.com
    Security
    EventData
    Mount-Database
    {Identity=dellstslab}
    dellstslab.com/Users/Administrator
    S-1-5-21-2431095704-2869583948-1116897492-500
    S-1-5-21-2431095704-2869583948-1116897492-500
    ServerRemoteHost-EMC
    1412
    14
    00:00:01.1388073
    View Entire Forest:
    'True', Configuration Domain Controller: 'WIN-NVOVSE1R716.dellstslab.com',
    Preferred Global Catalog: 'WIN-NVOVSE1R716.dellstslab.com', Preferred Domain
    Controllers: '{ WIN-NVOVSE1R716.dellstslab.com }'
    System.InvalidOperationException:
    Couldn't mount the database that you specified. Specified database: dellstslab;
    Error code: An Active Manager operation failed with a transient error. Please
    retry the operation. Error: Database action failed with transient error. Error:
    A transient error occurred during a database operation. Error:
    MapiExceptionNetworkError: Unable to make admin interface connection to server.
    (hr=0x80040115, ec=-2147221227) Diagnostic context: ...... Lid: 12696 dwParam:
    0x6D9 Msg: EEInfo: Generation Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam:
    0x6D9 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x6D9 Msg:
    EEInfo: Status: 1753 Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location:
    501 Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9
    Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]:
    Unicode string: ncalrpc Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode
    string: Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 24060
    StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid:
    27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115 [Database:
    dellstslab, Server: EXCHANGE2010.dellstslab.com]. --->
    Microsoft.Exchange.Cluster.Replay.AmDbActionWrapperTransientException: An Active
    Manager operation failed with a transient error. Please retry the operation.
    Error: Database action failed with transient error. Error: A transient error
    occurred during a database operation. Error: MapiExceptionNetworkError: Unable
    to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
    Diagnostic context: ...... Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation
    Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating
    component: 2 Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753 Lid: 9624
    dwParam: 0x6D9 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x6D9
    Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters:
    4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc Lid:
    8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: Lid: 12952 dwParam:
    0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570 Lid: 12952 dwParam: 0x6D9 Msg:
    EEInfo: prm[3]: Long val: 382312662 Lid: 24060 StoreEc: 0x80040115 Lid: 23746
    Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid: 27842 StoreEc: 0x80040115 Lid:
    20866 Lid: 29058 StoreEc: 0x80040115 --->
    Microsoft.Exchange.Data.Storage.AmServerTransientException: An Active Manager
    operation failed with a transient error. Please retry the operation. Error:
    MapiExceptionNetworkError: Unable to make admin interface connection to server.
    (hr=0x80040115, ec=-2147221227) Diagnostic context: ...... Lid: 12696 dwParam:
    0x6D9 Msg: EEInfo: Generation Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam:
    0x6D9 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x6D9 Msg:
    EEInfo: Status: 1753 Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location:
    501 Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9
    Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]:
    Unicode string: ncalrpc Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode
    string: Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 24060
    StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid:
    27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115 --->
    Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to
    make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
    Diagnostic context: ...... Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation
    Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating
    component: 2 Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753 Lid: 9624
    dwParam: 0x6D9 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x6D9
    Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters:
    4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc Lid:
    8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: Lid: 12952 dwParam:
    0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570 Lid: 12952 dwParam: 0x6D9 Msg:
    EEInfo: prm[3]: Long val: 382312662 Lid: 24060 StoreEc: 0x80040115 Lid: 23746
    Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid: 27842 StoreEc: 0x80040115 Lid:
    20866 Lid: 29058 StoreEc: 0x80040115 at
    Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult,
    SafeExInterfaceHandle iUnknown, Exception innerException) at
    Microsoft.Mapi.ExRpcAdmin.Create(String server, String user, String domain,
    String password) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.Mount(Guid mdbGuid,
    MountFlags flags) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.<>c__DisplayClassb.<MountDatabaseDirect>b__2()
    at
    Microsoft.Exchange.Cluster.Replay.FailoverPerformanceTrackerBase`1.RunTimedOperation(TOpCode
    opCode, Action operation) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.MountDatabaseDirect(Guid
    mdbGuid, MountFlags storeFlags, AmMountFlags amMountFlags, AmDbActionCode
    actionCode) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmRpcServer.<>c__DisplayClass19.<MountDatabaseDirect>b__18()
    at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String
    databaseName, RpcServerOperation rpcOperation) --- End of inner exception stack
    trace (Microsoft.Mapi.MapiExceptionNetworkError) --- --- End of stack trace on
    server (Exchange2010.dellstslab.com) --- at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String
    databaseName, String serverName, RpcErrorExceptionInfo errorInfo) at
    Microsoft.Exchange.Data.Storage.ActiveManager.AmRpcClientHelper.RunRpcOperationWithAuth(AmRpcOperationHint
    rpcOperationHint, String serverName, String databaseName, NetworkCredential
    networkCredential, Nullable`1 timeoutMs, InternalRpcOperation rpcOperation) at
    Microsoft.Exchange.Data.Storage.ActiveManager.AmRpcClientHelper.MountDatabaseDirectEx(String
    serverToRpc, Guid dbGuid, AmMountArg mountArg) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmDbAction.MountDatabaseDirect(AmServerName
    serverName, AmServerName lastMountedServerName, Guid dbGuid, MountFlags
    storeFlags, AmMountFlags amFlags, AmDbActionCode actionCode) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmDbStandaloneAction.<>c__DisplayClass2.<MountInternal>b__0(Object
    , EventArgs ) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmHelper.HandleKnownExceptions(EventHandler
    ev) --- End of inner exception stack trace
    (Microsoft.Exchange.Data.Storage.AmServerTransientException) --- at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmDbOperation.Wait(TimeSpan
    timeout) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.MountDatabase(Guid
    mdbGuid, MountFlags storeFlags, AmMountFlags amMountFlags,
    DatabaseMountDialOverride mountDialOverride, AmDbActionCode actionCode) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmRpcServer.<>c__DisplayClass4.<MountDatabase>b__3()
    at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String
    databaseName, RpcServerOperation rpcOperation) --- End of stack trace on server
    (EXCHANGE2010.dellstslab.com) --- at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String
    databaseName, String serverName, RpcErrorExceptionInfo errorInfo) at
    Microsoft.Exchange.Data.Storage.ActiveManager.AmRpcClientHelper.RunDatabaseRpcWithReferral(AmRpcOperationHint
    rpcOperationHint, Database database, String targetServer, InternalRpcOperation
    rpcOperation) at
    Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase.RequestMount(MountFlags
    storeMountFlags) at
    Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase.InternalProcessRecord()
    --- End of inner exception stack trace ---
    7
    Microsoft.Exchange.Cluster.Replay.AmDbActionWrapperTransientException:
    An Active Manager operation failed with a transient error. Please retry the
    operation. Error: Database action failed with transient error. Error: A
    transient error occurred during a database operation. Error:
    MapiExceptionNetworkError: Unable to make admin interface connection to server.
    (hr=0x80040115, ec=-2147221227) Diagnostic context: ...... Lid: 12696 dwParam:
    0x6D9 Msg: EEInfo: Generation Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam:
    0x6D9 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x6D9 Msg:
    EEInfo: Status: 1753 Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location:
    501 Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9
    Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]:
    Unicode string: ncalrpc Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode
    string: Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 24060
    StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid:
    27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115 --->
    Microsoft.Exchange.Data.Storage.AmServerTransientException: An Active Manager
    operation failed with a transient error. Please retry the operation. Error:
    MapiExceptionNetworkError: Unable to make admin interface connection to server.
    (hr=0x80040115, ec=-2147221227) Diagnostic context: ...... Lid: 12696 dwParam:
    0x6D9 Msg: EEInfo: Generation Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam:
    0x6D9 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x6D9 Msg:
    EEInfo: Status: 1753 Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location:
    501 Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9
    Msg: EEInfo: NumberOfParameters: 4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]:
    Unicode string: ncalrpc Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode
    string: Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
    Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662 Lid: 24060
    StoreEc: 0x80040115 Lid: 23746 Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid:
    27842 StoreEc: 0x80040115 Lid: 20866 Lid: 29058 StoreEc: 0x80040115 --->
    Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to
    make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
    Diagnostic context: ...... Lid: 12696 dwParam: 0x6D9 Msg: EEInfo: Generation
    Time: 2014-02-18 16:43:34:389 Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating
    component: 2 Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753 Lid: 9624
    dwParam: 0x6D9 Msg: EEInfo: Detection location: 501 Lid: 13720 dwParam: 0x6D9
    Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters:
    4 Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncalrpc Lid:
    8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: Lid: 12952 dwParam:
    0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570 Lid: 12952 dwParam: 0x6D9 Msg:
    EEInfo: prm[3]: Long val: 382312662 Lid: 24060 StoreEc: 0x80040115 Lid: 23746
    Lid: 31938 StoreEc: 0x80040115 Lid: 19650 Lid: 27842 StoreEc: 0x80040115 Lid:
    20866 Lid: 29058 StoreEc: 0x80040115 at
    Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult,
    SafeExInterfaceHandle iUnknown, Exception innerException) at
    Microsoft.Mapi.ExRpcAdmin.Create(String server, String user, String domain,
    String password) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.Mount(Guid mdbGuid,
    MountFlags flags) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.<>c__DisplayClassb.<MountDatabaseDirect>b__2()
    at
    Microsoft.Exchange.Cluster.Replay.FailoverPerformanceTrackerBase`1.RunTimedOperation(TOpCode
    opCode, Action operation) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.MountDatabaseDirect(Guid
    mdbGuid, MountFlags storeFlags, AmMountFlags amMountFlags, AmDbActionCode
    actionCode) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmRpcServer.<>c__DisplayClass19.<MountDatabaseDirect>b__18()
    at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String
    databaseName, RpcServerOperation rpcOperation) --- End of inner exception stack
    trace (Microsoft.Mapi.MapiExceptionNetworkError) --- --- End of stack trace on
    server (Exchange2010.dellstslab.com) --- at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String
    databaseName, String serverName, RpcErrorExceptionInfo errorInfo) at
    Microsoft.Exchange.Data.Storage.ActiveManager.AmRpcClientHelper.RunRpcOperationWithAuth(AmRpcOperationHint
    rpcOperationHint, String serverName, String databaseName, NetworkCredential
    networkCredential, Nullable`1 timeoutMs, InternalRpcOperation rpcOperation) at
    Microsoft.Exchange.Data.Storage.ActiveManager.AmRpcClientHelper.MountDatabaseDirectEx(String
    serverToRpc, Guid dbGuid, AmMountArg mountArg) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmDbAction.MountDatabaseDirect(AmServerName
    serverName, AmServerName lastMountedServerName, Guid dbGuid, MountFlags
    storeFlags, AmMountFlags amFlags, AmDbActionCode actionCode) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmDbStandaloneAction.<>c__DisplayClass2.<MountInternal>b__0(Object
    , EventArgs ) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmHelper.HandleKnownExceptions(EventHandler
    ev) --- End of inner exception stack trace
    (Microsoft.Exchange.Data.Storage.AmServerTransientException) --- at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmDbOperation.Wait(TimeSpan
    timeout) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.MountDatabase(Guid
    mdbGuid, MountFlags storeFlags, AmMountFlags amMountFlags,
    DatabaseMountDialOverride mountDialOverride, AmDbActionCode actionCode) at
    Microsoft.Exchange.Cluster.ActiveManagerServer.AmRpcServer.<>c__DisplayClass4.<MountDatabase>b__3()
    at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String
    databaseName, RpcServerOperation rpcOperation) --- End of stack trace on server
    (EXCHANGE2010.dellstslab.com) --- at
    Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String
    databaseName, String serverName, RpcErrorExceptionInfo errorInfo) at
    Microsoft.Exchange.Data.Storage.ActiveManager.AmRpcClientHelper.RunDatabaseRpcWithReferral(AmRpcOperationHint
    rpcOperationHint, Database database, String targetServer, InternalRpcOperation
    rpcOperation) at
    Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase.RequestMount(MountFlags
    storeMountFlags) at
    Microsoft.Exchange.Management.SystemConfigurationTasks.MountDatabase.InternalProcessRecord()
    The system attendant service does not start either.  Any ideas?

  • "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 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

Maybe you are looking for