Microsoft exchange console critical error "RunspaceServerSettingsPresentationObject"

Hi All,
Running Exchange 2010 SP3  with Rollup Update 8V2. (Role –HT ; certificate - self
signed)
When use EMC giving an error. But I can do all the stuff using EMS. Even getting same
error when  connect the server from local system EMC. I have not found any valid logs in Event viewer.
Below is the error snapshot. Please share you suggestions to fix this issue.

Hi Amjath,
The only thing I can think of right now is to simply check every single eventlog on both client and server whether it's running full. And since that's a bit bothersome, here's a script that will do so (run on both machines locally, if they are multiple machines):
$col = @{ }
get-eventlog "*" | %{ $col[$_.Log] = New-Object PSObject -Property @{ Log = $_.Log; Entries = $_.Entries.Count; Overflow = $_.OverflowAction; Retain = $_.MinimumRetentionDays; MaxSize = $_.MaximumKilobytes * 1024; CurrentSize = 0 } }
Get-WmiObject Win32_NTEventlogFile | %{ $col[$_.LogFileName].CurrentSize = $_.FileSize }
$res = $col.Keys | %{ $col[$_] }
$res | ft -AutoSize
If you don't find a log that's capped ... well, that's as far as I know where to look.
Cheers,
Fred
There's no place like 127.0.0.1

Similar Messages

  • Microsoft exchange console critical error

    Hi All,
    Running Exchange 2010 SP3  with Rollup Update 8V2. (Role –HT ; certificate - self signed)
    When use EMC giving an error. But I can do all the stuff using EMS. Even getting same error when  connect the server from local system EMC. I have not found any valid logs
    in Event viewer.
    Below is the error snapshot. Please share you suggestions to fix this issue.
    Thanks.

    Hi Amjath,
    Thank you for your question.
    By your state: Running Exchange 2010 SP3  with Rollup Update 8V2. (Role –HT ; certificate - self signed)
    This is my understanding: there is a CA in organization. If I misunderstand,  please be free to let me know.
    I suggest we rebuild the certificate for Exchange by the following link:
    http://blogs.technet.com/b/danielkenyon-smith/archive/2010/05/13/the-name-on-the-certificate-is-invalid-or-does-not-match-the-name-of-the-site-part-1.aspx
    If there are any questions regarding this issue, please be free to let me know.
    Best Regard,
    Jim

  • Microsoft Office 2013 Outlook errors due to it wants to connect to MS exchange

    Every time I try to load Outlook 2013 it gives me an error: The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action and when I click on it, it keeps going in a loop. What to do to correct it will
    not launch without exchange server and I have it. Any suggestions? And I download MS Exchange 2010 SP1x64 still nothing

    Same issue here.  I have the Surface Pro and only one Outlook Exchange Server account will connect.  They other one gives the same Microsoft Exchange is unavailable error.  The funny part is that these are both work email accounts that connect
    to the same server, but one works and the other does not.  I can ping the server no problem.  
    I have spent probably a total of 15 hours on the phone with Microsoft Office CS.  There's 15 hours I will never get back.  To say they were useless would be an understatement.  Half the time they just took down the issues and then said I had
    reached the wrong department and transferred me.  I got transferred 11 times on one phone call.  No one even tried to help.
    So unless Microsoft can come up with a solution to this I am taking the Surface Pro back.  This is really disappointing.  I was really hoping that Microsoft could be an alternative the Apple Universe.  Seems like they chose gimickery over
    functionality.  Windows 8 looks pretty and does some neat stuff, but sending and receiving emails is the most basic of the basics you expect from your PC.
    If anyone has a solution from Microsoft please post it here.  

  • Exchange 2013 "Server Error in '/owa' Application" - System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1

    Out of nowhere...literally this started happening to our standalone Exchange server / Domain Controller
    Operating System: Microsoft Windows Server 2012 Standard
    Problem Child: Microsoft Exchange Server 2013
    Error: When i try to login to the OWA or ECP i receive the listed errors above.
    OS and Exchange installed on C:\
    Mailbox Databases installed on D:\
    Mailbox Logs on E:\
    Outlook is still working for the end-user, but Outlook Web Access, ECP and all other features required to make this server manageable are failing. I can access the login screen, though at:
    https://<servername>/owa
    or
    https://<servername>/ecp
    I have tried reset of virtual directories. Tried IISRESET /NOFORCE after this, but no success.

    Hi MRXennix,
    Base on my research, the issue is caused by corrupted Killbit.xml file on "ClientAccess\owa\15.0.xxx.x\owa2\ext\killbit".
    I recommend you refer to the following method to solved the issue:
    1. Remove the Killbit.xml file and restart IIS
    2. Install the latest CU builds of the exchange 2013.
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Microsoft Exchange Critical Error: Requested Value 'TeamMailbox' was not found.

    Hi
    Microsoft Online Services Tech Center Team,
    Did anyone can help me on this error and found a solution?
    Background:
    We have successfully deployed (I think) a Office 365 hybrid configuration, we can migrate users from on premise to cloud O365 and back. But, every
    time we opened the EMC on our Exchange 2010 upgraded to SP 3, this error message pops out.
    <o:p></o:p>
    <o:p></o:p>
    This happens when we open the EMC >> Microsoft Exchange >> O365 >> Recipient configuration.
    Hope somebody can help us.
    Thanks.
    Mark Josef
    Mark Josef

    We are having the same problem and would like to find a fix - only does it when clicking on our O365 Online Recipient Configuration section on our Hybrid exchange server management console.
    Not sure if this is part of our intermittent issues with migrating users to O365 through management console or not but I don't like errors coming up anywhere - want to fix it!  <Bump>

  • Spam Protection for Email showing Critical for Exchange Server 2007 after installing Symantec Mail Security for Microsoft Exchange

    Hi there,
    I have SBS 2008, and I have recently installed Symantec Mail Security for Microsoft Exchange  version 7.5 but when I take a look on Windows SBS Console under Security, it shows "Spam Protection for Email Critical Exchange Server 2007" However,
    when I open the SMSME it shows running well with no problem..
    Any Suggestions???
    Thanks

    Hi,
    Would you please let me confirm whether all functions (which are related to Exchange Server) run as normal? Just
    a confirmation, thanks for your understanding.
    Please run
    SBS BPA and check if find relevant issues. In addition, please refer to GaryD9’s suggestion in following thread and check if can help you.
    SBS
    2008 & Forefront Protection 2010 for Exchange - SBS Console Error
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • 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

  • Get-mailboxdatabasecopystatus -identity DBNAME | fl gives errors "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for". DB is mounted and the DB copies are in healthy status.

    We are getting a SCOM alert " Database copy isn''''t keeping up with the changes on the active database copy and has failed."
    When we go to the mailbox server and check we found all the Mailbox DB's are mounted properly and their copies are in healthy state. Further digging to this problem we found that there are no critical events to this DB in the eventviewer.
    When we runt he get-mailboxdatabasecopystatus -identity DBNAME | Fl then in the ErrorMessage section we get error "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for . If the copy doesn't
    recover automatically, administrator intervention may be necessary. Error: The directory is not empty."
    ErrorEventID : 4126
    In the event viewer we get a Information event 4114 saying the DB redundancy health check passed and in the details section we get the same error message mentioned above.
    Also we observed that the "MSExchange Replication" counter "Failed" is set to 1 for this perticular DB but is is set to 0 for the other DB's. Tried restarting the MSEXChange replication service but still the "Failed" counter
    is 1 and the SCOM alert is still active.
    The version is Exchange 2010 SP3 UR5
    Any clues???

    Hi,
    From your description, this issue only affect one mailbox datatabase.
    Please use the Update-MailboxDatabaseCopy command to check result.
    If it doesn't work, please dismount your active database copy and check if this is Clean Shutdown, if it's dirty shutdown, please bring to clean shutdown and mount this database copy. Then run the Update-MailboxDatabaseCopy command again to check result.
    Best regards,
    Belinda Ma
    TechNet Community Support

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

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

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

  • Exchange ActiveSync has shut down because an unexpected critical error occurred

    Hi, 
    At one point all phones stopped syncing and when checking event log i came to this error:
    Exchange ActiveSync has shut down because an unexpected critical error occurred.
    URL=
    --- Exception start ---
    Exception type: System.OutOfMemoryException
    Exception message: Insufficient memory to continue the execution of the program.
    Exception level: 0
    Exception stack trace:    at Microsoft.Exchange.Data.Storage.GenericListData`2.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool)
       at Microsoft.Exchange.AirSync.DeviceBehaviorData.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool)
       at Microsoft.Exchange.Data.Storage.DerivedData`1.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool)
       at Microsoft.Exchange.Data.Storage.GenericListData`1.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool)
       at Microsoft.Exchange.Data.Storage.GenericDictionaryData`3.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool)
       at Microsoft.Exchange.Data.Storage.SyncState.DeserializeSyncStateTable(Int64 idxTable)
       at Microsoft.Exchange.Data.Storage.SyncState.Deserialize(PropertyDefinition property)
       at Microsoft.Exchange.Data.Storage.SyncState.Load(Boolean reloadFromBackend, PropertyDefinition[] additionalPropsToLoad)
       at Microsoft.Exchange.Data.Storage.SyncState..ctor(SyncStateStorage syncStateStorage, StoreObject storeObject, SyncStateInfo syncStateInfo, Boolean syncStateIsNew)
       at Microsoft.Exchange.Data.Storage.CustomSyncState.GetSyncState(SyncStateStorage syncStateStorage, Folder syncStateParentFolder, SyncStateInfo syncStateInfo, StoreObjectId storeObjectId)
       at Microsoft.Exchange.Data.Storage.SyncStateStorage.GetCustomSyncState(SyncStateInfo syncStateInfo)
       at Microsoft.Exchange.AirSync.GlobalInfo.LoadFromMailbox(MailboxSession mailboxSession, SyncStateStorage syncStateStorage, ProtocolLogger protocolLogger)
       at Microsoft.Exchange.AirSync.Command.OpenSyncStorage(Boolean shouldOpenGlobalSyncState, Boolean shouldUseBudget)
       at Microsoft.Exchange.AirSync.Command.WorkerThread()
    --- Exception end ---
    mail server has 35GBs of Ram, plenty of disk space, no extra transaction logs adding or anything like that. Right now phones work, but every other minute that error pops up and after sometime event 1013 is logged saying that Exchange activesync has been
    loaded.
    Thanks

    Hi Luksharp
    Is it happening only for Iphones or is it for all types of phones as well ?
    What version of Exchange server you are running ?
    Are you experiencing this issue after any recent upgrade or changes in CAS server ?
    Just check the sync state policy refer below article
    http://blog.chrislehr.com/2012/02/difference-in-policy-versions.html
    Looks like Sync State Policy is loaded for user's mailbox from latest version of CAS server and it was contacted the lower version of CAS for mailbox access.
    Just ensure all of your CAS servers are up to date with all mailbox and hub in correct versions.
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

    Hi Board,
    i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
    we drive a 2 node DAG (Location1-Ex1-mb1 
    Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
    Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          28.09.2012 00:37:17
    Event ID:      2112
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Location1-Exc1-MB1
    Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
    Followed by
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:         
    01.10.2012 03:33:06
    Event ID:      2024
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:         
    N/A
    Computer:      Location1-Exc1-MB1
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
    The backup Application - Symantec Backup Exec 2010 R3 – states, this error
    Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
    Check the Windows Event Viewer for details.
    Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
    Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
    to restart the MS Exchange Replication Service – BUT the mentioned eventID
    8229 isn´t present on any of the both Mailboxservers.
    The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
    This confuses me, since all Backups are normally taken from the passive copy of a Database.
    So my questions to the board are:
    * Does anyone is facing similar issues?
    * Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
    -          * Does someone know the conditions, why shadows copies remain and
    aren´t removed in a proper manner?
    What can cause the circumstance, that only 1 DB is facing such issues?
    Any suggestion is welcome!
    BR
    Markus

    Hi Lenora,
    I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
    those things i´ve all tried now:
    - Backup from passive DB (forced within Symantec Backup Exec)
    - Backup from active DB (forced within Symantec Backup Exec)
    - Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
    - Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
    All those attempts failed.
    But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
    The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
    Backups are working again on all DBs!
    THX for your replys.
    Best regards
    Markus

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

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

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

  • Outlook 2013 error: The connection to Microsoft Exchange is unavailable

    Environment: Windows 7 Enterprise
    Setup: Fresh install of Office 2013
    Issue: When I launch Outlook I get the error:
    The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
    Steps to resolve:
    I made sure my server name and mail address were correct but this did not have an impact.
    I am at a total loss on how to resolve this issue, is there anyway to manually connect to M.E> as it is just saying the connection is unavailable.  All of the other threads dealing with this issue have been no help.  I can sign into my account
    at login.microsoftonline.net so i know the account is valid.  I also receive email to my iPhone with the account and server.  Any advice would be wonderful.
    Now when I start up the application it tells me the same error and brings up something to alter the server and connection address.   

    Hi,
    Have you tried to recreate a new mail profile and then test the issue?
    To do this, please exit Outlook, and then go to
    Control Panel >Mail... > Add…
    Details about create a new mail profile, see:
    http://support.microsoft.com/kb/829918/en-us
    Also, you can try with this KB:
    http://support.microsoft.com/kb/2264398
    This issue occurs when the
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders registry key does not contain all of the required data. Specifically, these problems occur if the
    AppData string value is missing from this registry key.
    To resolve this issue, import the
    User Shell Folders registry key from a working Windows User Profile.
    Hope this helps.
    Best Regards
    Steve Fan
    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. : 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

Maybe you are looking for