Exchange 2013 CU3 monitoring

Hello,
I'm getting several times per day the following alert in the Event Viewer of both my Mailbox Role servers which then raise an alert in SCOM 2012:
Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
Source: ManagedAvailability
Event ID: 4
Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate.
I'm not able to find information about what is being monitored and how to get rid of this events.
Any help appreciated.
Thank you in advance.
Raffaele Zamuner

Hi Amit,
here's the output from the EMS and the Event Viewer:
[PS] C:\Windows\system32>Get-ServerHealth [ServerName] | ?{$_.alertvalue -ne "Healthy" -and $_.alertvalue -ne "Disabled"}
Server          State           Name                 TargetResource
HealthSetName   AlertValue ServerComp
onent
[ServerName]        NotApplicable   ScanTimeMeanMonitor                       FIPS
Unhealthy None
[ServerName]        NotApplicable   MaintenanceFailur...                      DAL
Unknown    None
[ServerName]        NotApplicable   DatabaseLogicalPh... FINIT                MailboxSpace    Repairing None
[ServerName]        NotApplicable   DatabaseLogicalPh...                      MailboxSpace
Unhealthy None
[ServerName]        Online          Total.Shadow.Queu...
HubTransport    Unhealthy HubTran...
[ServerName]        NotApplicable   MailboxDeliveryAv...                      MailboxTrans... Unhealthy
None
[ServerName]        NotApplicable   DatabaseLogicalPh... DB1                  MailboxSpace    Repairing None
[ServerName]        NotApplicable   DatabaseLogicalPh... MCS1                 MailboxSpace    Repairing None
[PS] C:\Windows\system32>get-serverhealth -Server [ServerName] -HealthSet AMScanTimeou
[PS] C:\Windows\system32>
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-06-03T07:23:16.626852900Z" />
<EventRecordID>1753</EventRecordID>
<Correlation />
<Execution ProcessID="1860" ThreadID="21496" />
<Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
<Computer>[ServerName].finit.local</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<HealthSet>FIPS</HealthSet>
<Subject>FIPS health set unhealthy (ScanTimeMeanMonitor) - High Mean Scan Time</Subject>
<Message>Mean Scan Time has been greater than 60 seconds for the last 15 mins. Please investigate. ------------------------------------------------------------------------------- States of all monitors within the health set: Note: Data may be stale.
To get current data, run: Get-ServerHealth -Identity '[ServerName]' -HealthSet 'FIPS' State Name TargetResource HealthSet AlertValue ServerComponent ----- ---- -------------- --------- ---------- --------------- NotApplicable ScanProcessesRunningMonitor FIPS
Healthy None NotApplicable ScanProcessBelowMinimumMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutMonitor FIPS Healthy None NotApplicable ScanRequestsTimedOutUrgentMonitor FIPS Healthy None NotApplicable ScanRequestQueueTimeoutUrgentMonitor FIPS
Healthy None NotApplicable RecoveryQueueTimeoutUrgentMonitor FIPS Healthy None NotApplicable ScanTimeMeanMonitor FIPS Healthy None NotApplicable ScanRequestErrorRatioMonitor FIPS Healthy None NotApplicable ScanRequestErrorsMonitor FIPS Healthy None NotApplicable
TextExtractionErrorsMonitor FIPS Healthy None NotApplicable ObsoleteEngineInUseEventMonitor FIPS FIPS Healthy None NotApplicable MaintenanceFailureMonitor.FIPS FIPS Healthy None NotApplicable EngineNotEnabledForUpdatesEventMonitor FIPS FIPS Healthy None NotApplicable
EUSTerminationEventMonitor FIPS FIPS Healthy None NotApplicable EUSUnableToStartEventMonitor FIPS FIPS Healthy None NotApplicable ADFilteringSettingsWatcherStartFaile... FIPS FIPS Healthy None NotApplicable ScanningProcessRepeatedlyCrashingMon... FIPS FIPS
Healthy None NotApplicable FilteringManagementServiceDownMonitor FIPS Healthy None NotApplicable PrivateWorkingSetWarning.fms fms FIPS Healthy None NotApplicable PrivateWorkingSetError.fms fms FIPS Healthy None NotApplicable ProcessProcessorTimeWarning.fms
fms FIPS Healthy None NotApplicable ProcessProcessorTimeError.fms fms FIPS Healthy None NotApplicable ExchangeCrashEventError.fms fms FIPS Healthy None NotApplicable LongRunningWatsonWarning.fms fms FIPS Healthy None NotApplicable LongRunningWerMgrWarning.fms
fms FIPS Healthy None NotApplicable MicrosoftFailedUpdatesMonitor FIPS Healthy None NotApplicable MicrosoftEngineErrorsMonitor FIPS Healthy None NotApplicable MSClassificationEngineErrorsMonitor FIPS Healthy None States of all health sets: Note: Data may be
stale. To get current data, run: Get-HealthReport -Identity '[ServerName]' State HealthSet AlertValue LastTransitionTime MonitorCount ----- --------- ---------- ------------------ ------------ NotApplicable ActiveSync.Protocol Healthy 03/06/2014 05.04.35 9
NotApplicable Autodiscover.Protocol Healthy 03/06/2014 01.18.16 9 NotApplicable ActiveSync Healthy 03/06/2014 08.24.19 1 NotApplicable Antimalware Unhealthy 03/06/2014 09.18.14 11 NotApplicable ECP Healthy 03/06/2014 08.40.07 5 NotApplicable Ediscovery.Protocol
Healthy 03/06/2014 08.55.21 1 NotApplicable AD Healthy 03/06/2014 07.46.15 19 NotApplicable EDS Healthy 03/06/2014 08.52.30 90 NotApplicable EventAssistants Healthy 03/06/2014 09.21.03 15 NotApplicable EWS.Protocol Healthy 03/06/2014 09.15.04 11 NotApplicable
FEP Healthy 02/06/2014 09.04.40 2 NotApplicable FIPS Healthy 03/06/2014 09.15.34 28 NotApplicable Monitoring Healthy 03/06/2014 07.53.12 17 NotApplicable MailboxMigration Healthy 02/06/2014 14.03.19 3 Online UM.CallRouter Healthy 03/06/2014 04.44.11 8 NotApplicable
UM.Protocol Healthy 03/06/2014 05.05.45 22 NotApplicable OAB Healthy 03/06/2014 09.22.26 8 Online HubTransport Unhealthy 03/06/2014 09.22.35 133 NotApplicable EAS Healthy 02/05/2014 10.33.27 1 NotApplicable Autodiscover Healthy 03/06/2014 05.56.59 1 NotApplicable
DataProtection Healthy 03/06/2014 09.18.11 66 NotApplicable FreeBusy Healthy 02/05/2014 10.30.56 1 NotApplicable Clustering Healthy 03/06/2014 08.21.27 5 NotApplicable BitlockerDeployment Healthy 02/06/2014 22.00.36 1 NotApplicable ClientAccess.Proxy Healthy
02/06/2014 14.20.31 1 NotApplicable Compliance Healthy 02/05/2014 10.29.01 1 NotApplicable EWS Healthy 01/06/2014 12.57.38 1 NotApplicable FfoRws Healthy 01/06/2014 09.15.31 1 NotApplicable Places Healthy 03/06/2014 01.16.29 1 Online Transport Healthy 03/06/2014
08.23.33 10 NotApplicable RemoteMonitoring Healthy 02/06/2014 15.11.34 4 NotApplicable Search Healthy 03/06/2014 07.04.56 140 NotApplicable Inference Healthy 01/06/2014 23.57.09 1 NotApplicable OWA Healthy 03/06/2014 09.16.39 2 NotApplicable MailboxSpace Repairing
03/06/2014 09.22.02 17 NotApplicable MRS Healthy 03/06/2014 09.20.58 19 NotApplicable MessageTracing Healthy 03/06/2014 07.03.30 8 NotApplicable Network Healthy 03/06/2014 09.09.30 2 NotApplicable Calendaring Healthy 03/06/2014 09.19.16 8 NotApplicable PeopleConnect
Healthy 02/06/2014 14.10.08 1 NotApplicable IMAP Healthy 03/06/2014 08.10.29 1 NotApplicable POP Healthy 03/06/2014 05.54.04 1 NotApplicable ProcessIsolation Healthy 03/06/2014 07.39.59 22 NotApplicable Provisioning Healthy 03/06/2014 08.35.16 8 NotApplicable
Psws Healthy 03/06/2014 08.51.44 15 NotApplicable PublicFolders Healthy 03/06/2014 09.21.54 5 NotApplicable Outlook Healthy 03/06/2014 05.56.00 1 NotApplicable RPS Healthy 03/06/2014 08.22.48 1 NotApplicable RWS Healthy 03/06/2014 08.11.44 2 NotApplicable
Security Healthy 03/06/2014 08.11.33 8 NotApplicable SiteMailbox Healthy 03/06/2014 09.07.10 4 NotApplicable Store Healthy 03/06/2014 09.19.09 110 NotApplicable TransportSync Healthy 03/06/2014 08.11.56 8 NotApplicable UserThrottling Healthy 03/06/2014 09.21.49
8 NotApplicable FfoWebService Healthy 03/06/2014 07.07.43 1 NotApplicable DAL Healthy 03/06/2014 08.08.02 12 NotApplicable FfoWebstore Healthy 03/06/2014 07.07.33 1 NotApplicable AntiSpam Healthy 03/06/2014 06.02.52 8 NotApplicable OWA.Protocol.Dep Healthy
30/05/2014 17.45.35 1 NotApplicable MigrationMonitor Healthy 03/06/2014 08.33.07 3 NotApplicable MailboxTransport Unhealthy 03/06/2014 09.05.01 63 NotApplicable MSExchangeCertificateDeplo... Disabled 01/01/0001 01.00.00 2 NotApplicable OWA.Protocol Healthy
03/06/2014 07.33.09 9 NotApplicable Outlook.Protocol Healthy 02/06/2014 18.07.34 11 NotApplicable RPS.Protocol Healthy 02/05/2014 10.33.10 2 NotApplicable IMAP.Protocol Healthy 03/06/2014 07.31.55 7 NotApplicable Datamining Healthy 03/06/2014 05.06.42 7 NotApplicable
POP.Protocol Healthy 01/06/2014 19.02.12 7 Online FrontendTransport Healthy 02/06/2014 09.06.30 7 NotApplicable CentralAdmin Healthy 03/06/2014 07.37.18 7 Online ECP.Proxy Healthy 03/06/2014 06.30.43 7 Online RPS.Proxy Healthy 03/06/2014 09.22.16 28 NotApplicable
PushNotifications.Protocol Healthy 03/06/2014 08.34.46 7 Online RWS.Proxy Healthy 02/06/2014 22.55.09 7 Online Outlook.Proxy Healthy 03/06/2014 07.51.37 7 Online OutlookMapi.Proxy Healthy 03/06/2014 08.09.14 7 Note: Subsequent detected alerts are suppressed
until the health set is healthy again.</Message>
<Monitor>ScanTimeMeanMonitor</Monitor>
</EventXML>
</UserData>
</Event>
Raffaele Zamuner

Similar Messages

Exchange 2013 CU3 Databases only activate on one mailbox server

Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log:     Mailbox logon verification
        EMSMDB.Connect()
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - ErrorDetails =
        - RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
        - ActivityContext =
    EMSMDB.Connect() completed successfully.
        EMSMDB.DoRpc(Logon)
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
        - ErrorDetails =
        - Latency = 00:00:00.0018801
        - ActivityContext =
    EMSMDB.DoRpc(Logon) failed.
    Task produced output:
    - TaskStarted = 11/12/2013 5:15:25 AM
    - TaskFinished = 11/12/2013 5:15:25 AM
    - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State               Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OutlookMapiHttpDeepTestMonitor
Outlook.Protocol              Unhealthy      None
NotApplicable       OutlookRpcDeepTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookRpcSelfTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookMapiHttpSelfTestMonitor                                             Outlook.Protocol
Healthy        None
NotApplicable       PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name:      Application
Source:        MSExchangeRepl
Date:          12.11.2013 4:49:46
Event ID:      3169
Task Category: Service
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="16388">3169</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
    <EventRecordID>1606248</EventRecordID>
    <Channel>Application</Channel>
    <Computer>test-mbx-2.contoso.local</Computer>
    <Security />
</System>
<EventData>
    <Data>DB-01</Data>
    <Data>test-mbx.contoso.local</Data>
    <Data>test-mbx-1.contoso.local</Data>
    <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Hi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
problems or the Exchange server is down for maintenance".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 Availability monitoring

Hi All,
I'm sort of stuck on the Exchange 2013 Probe Monitors, Monitors such as Imap, ActiveSync, Pop3 and FrontEndTransport keep failing. To fix/check the issue I'm following the below links:
http://technet.microsoft.com/en-us/library/ms.exch.scom.activesync(v=exchg.150).aspx
http://technet.microsoft.com/en-us/library/ms.exch.scom.imap(v=exchg.150).aspx
For example typing in Invoke-MonitoringProbe ActiveSync\ActiveSyncCTPProbe -Server server1.contoso.com | Format-List
I will get the following error:
WARNING: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Not sure why I'm getting this error.
For Imap testing i.e. typing in Invoke-MonitoringProbe IMAP\ImapCTPProbe -Server server1.contoso.com | Format-List
I will get the following error:
WARNING: No mailboxes were found to use in the CTP probe.
I'm absolutely stumped on why I'm getting these errors.
I'm running my Exchange servers on Hyper-V 2012 (My Hyper-V 2012 is clustered and managed by VMM 2012 SP1)
I have 8 Exchange 2013 Enterprise CU6 nodes, with 2 DAGS
Each Exchange server is running 4 cores of Processor and 24Gig of Ram (Not using Dynamic Memory)
If someon can shed some light on this issue it would be most appreciated.
Regards
Mike

Hi,
Thanks for your update.
Based on my research, I notice that most of this issue occur on the code level.
Some threads that I've refered:
1.
https://social.msdn.microsoft.com/Forums/en-US/b4d46d2b-ed00-45ce-82ce-1a23790e52d5/index-was-out-of-range-must-be-nonnegative-and-less-than-the-size-of-the-collection-parameter?forum=csharplanguage
2.
http://stackoverflow.com/questions/19162248/index-was-out-of-range-must-be-non-negative-and-less-than-the-size-of-the-colle
Disclaimer: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information
found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
I suggest ask Exchange Development Forum to double confirm this issue. For your convenience:
https://social.technet.microsoft.com/Forums/office/en-US/home?forum=exchangesvrdevelopment
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 CU3 Retention Policy Not working for Calendar & Tasks

We are currently on Exchange 2013 CU3 with Online Archiving Enabled for the user
Default policy is set to move all the items in mailbox which are older than 30 days to online archive mailbox.
Calendar and Tasks Items are also getting archived alongwith other Outlook items from Inbox,Deleted Items etc
Followed Technet website and created RPT for Calendar and Tasks with retention disabled
Still DPT takes precedence and move all the items under Calendar and Task to Online Archive Mailbox

Hi Sam,
I recommend you refer to the following article, despite this for Exchange 2010, however the same applies to exhcnage 2013:
Prevent archiving of items in a default folder in Exchange 2010
To prevent the <acronym title="Default Policy Tag">DPT</acronym> from being applied to a default folder, you can create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for that folder (or disable
any existing RPT for that folder). The Managed Folder Assistant, a mailbox assistant that processes mailbox items and applies retention policies, does not apply the
retention action of a disabled tag. Since the item/folder still has a tag, it's not considered untagged and the DPT isn't applied to it.
Why are items in the Notes folder still archived?
If you create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for the
Notes folder, you'll see items in that folder are not deleted, but they do continue to be moved to the archive! Why does this happen? How do you prevent it?
It's important to understand that:
A retention policy can have a <acronym title="Default Policy Tag">DPT</acronym> to
archive items (using the Move to Archive retention action) and a DPT to
delete items (using the Delete and Allow Recovery or
Permanently Delete retention actions). Both apply to untagged items.
The move and delete actions are exclusive of each other. Mailbox folders and messages can have both types of tags applied - an archive tag and a delete tag. It's not an either/or proposition.
If you create a disabled RPT for the Notes folder to not delete items, the archive DPT for the mailbox would still apply and move items.
When it comes to archiving, there's only one archive policy that administrators can enforce – the <acronym title="Default Policy Tag">DPT</acronym> with 'Move to archive' action.
You can't create a <acronym title="Retention Policy Tag">RPT</acronym> with the 'Move to archive' action. This rules out using the disabled RPT approach to prevent items from being moved.
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2013 CU3 - Outlook Web App LogOff

Hello All,
I have Exchange 2013 CU3 installed and i'm using TMG server for authentication. I am able to login through OWA but when i try to logoff it shows me message of "Close All your Browser Windows.." but OWA does not sign out.
On TMG, only Basic and NTLM authentication is supported. And in IIS Authentication for the OWA Virtual Directory is set to basic.
Can anyone please help me for TMG settings for exchange server 2013? Thankyou for the answers.

Hi,
Thank you for your patience and support.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards
Quan Gu

Tuning Exchange 2013 HealthSet Monitors (example: MailboxTransport - Mapi.Submit.Monitor)

Hello everyone,
I was hoping some of you could help me out a bit with the new monitors in Exchange 2013.
Especially after updating to CU6 we are getting a lot of warnings from SCOM with different HealthSets that show as unhealthy. These are usually “OK” again when we log on to the server and run Get-ServerHealth or Get-HealthReport. The most common healthset is
Compliance, but also get warnings from MailboxTransport and ActiveSync.
If we do manage to log on before the healthset returns to healthy again, like in the example below, we can drill down a bit. We are however very unsure about what to do with this information. Perhaps we should change the threshold, but how do we find out exactly
what this monitor is reporting on? We know it has something to do with Mapi Submit, and that the threshold is 8, but not much more than that?
Get-ServerHealth SERVER | where {($_.healthsetname -eq "mailboxtransport") -and ($_.alertvalue -eq "unhealthy")} | ft name,alertvalue -auto
Name AlertValue
Mapi.Submit.Monitor Unhealthy
(Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/MonitorDefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like "Mapi.Submit.Monitor"}
auto-ns2 : http://schemas.microsoft.com/win/2004/08/events
xmlns : myNs
Id : 266
AssemblyPath : D:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll
TypeName : Microsoft.Office.Datacenter.ActiveMonitoring.OverallXFailuresMonitor
Name : Mapi.Submit.Monitor
WorkItemVersion : [null]
ServiceName : MailboxTransport
DeploymentId : 0
ExecutionLocation : [null]
CreatedTime : 2014-11-20T08:51:03.5576888Z
Enabled : 1
TargetPartition : [null]
TargetGroup : [null]
TargetResource : MailboxTransport
TargetExtension : [null]
TargetVersion : [null]
RecurrenceIntervalSeconds : 0
TimeoutSeconds : 30
StartTime : 2014-11-20T08:51:03.5576888Z
UpdateTime : 2014-11-20T08:42:58.9416436Z
MaxRetryAttempts : 0
ExtensionAttributes : [null]
SampleMask : Mapi.Submit.Probe
MonitoringIntervalSeconds : 3600
MinimumErrorCount : 0
MonitoringThreshold : 8
SecondaryMonitoringThreshold : 0
MonitoringSamplesThreshold : 100
ServicePriority : 2
ServiceSeverity : 0
IsHaImpacting : 0
CreatedById : 57
InsufficientSamplesIntervalSeconds : 28800
StateAttribute1Mask : [null]
FailureCategoryMask : 0
ComponentName : ServiceComponents/MailboxTransport/High
StateTransitionsXml : <StateTransitions>
<Transition ToState="Unrecoverable" TimeoutInSeconds="0" />
</StateTransitions>
AllowCorrelationToMonitor : 0
ScenarioDescription : [null]
SourceScope : [null]
TargetScopes : [null]
HaScope : Server
Version : 65536
We have an Exchange 2007 server coexisting in the environment, but it is not in use and will be decommissioned.
ServerRole Edition AdminDisplayVersion
Mailbox, ClientAccess, HubTransport Standard Version 8.3 (Build 83.6)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)
Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)

Thanks Belinda.
We had a look in the log you mentioned, and found some events that appear to be related.
Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed.
This could indicate that the mailbox submissions are taking too long or not progressing at all.
SequenceNumber: 635515592255510017
Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635515592255510017. First Run? = False. Previous mail submission to store
was successful. Results - # of previous results: 0. Could Not Find stages that ran. Previous SendMail failure - Mail submitted to Store during the previous run never reached SendAsCheck.
This may indicate a latency from Store to Submission Service. Investigating. Found lower SA latency. Indicates an issue in Submission service.
Investigate. In SendMail - NotificationID=00000044-0000-0000-0000-0000659c9601 Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail
failure.
CheckPreviousRunMail exception details:
Current SendMail exception details:
MailWasSentInLastRun (0(no)/1(yes)): 1
CheckMailSuccess(0(no)/1(yes)): 0
SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1
PreviousMailLatencies: <[email protected]>,,2014-11-20T08:37:58.817Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.811|SA=0.343|MTSSDMO=0.426|MTSSDPL=0.002|MTSSDSS=0.008|MTSSDS=0.031|MTSS=0.466;;<[email protected]>,,2014-11-20T08:32:58.772Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.702|SA=0.203|MTSSDMO=0.451|MTSSDPL=0.003|MTSSDSS=0.007|MTSSDS=0.047|MTSS=0.500;;<[email protected]>,,2014-11-20T08:27:58.664Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=1.170|SA=0.530|MTSSDMO=0.548|MTSSDPL=0.002|MTSSDSS=0.035|MTSSDS=0.078|MTSS=0.647;;
GetPreviousMailLatencyFailures:
(The following are applicable if the mail was actually sent)
MailSentAt: 20.11.2014 08:42:58
TimeInSendingToStore: 62,3989
Sent Mail Result Details:
(InternetMessageId:<[email protected]>;
ItemEntryId:0 0 0 0 2E 57 BD C1 1C 4B 5C 47 9E 54 6E B8 B2 C5 75 38 7 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 0 0 1 B 0 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 18 1A CD F1 0 0 )
Properties of Sending mail
(Subject:00000044-0000-0000-0000-0000659c9601-MapiSubmitLAMProbe;
Sender:[email protected];
MbxGuid:340b204b-c716-4dfe-bbe1-cf09b5c73934;
MdbGuid:2a6b9801-1647-4378-bc11-6ff342d22fcf;
Recipient:[email protected];
Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException,
Exception currentRunException, DateTime timeMessageSentToStore)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
at System.Threading.Tasks.Task.Execute()'
Probe Result Name: 'Mapi.Submit.Probe'
Probe Result Type: 'Failed'
Monitor Total Value: '0'
Monitor Total Sample Count: '12'
Monitor Total Failed Count: '12'
Monitor Poisoned Count: '0'
Monitor First Alert Observed Time: '16.11.2014 21:40:10'

Exchange 2013 CU3 and Firefox 26.0

I upgraded Exchange 2013 to CU3 last night. I tested the mail flow and everything worked fine sending and recieving. The problem that I am having is with OWA in firefox 26.0 (currently newest version). I get weird graphical glitches when
OWA first loads. Once you click around the display stabilizes but the biggest problem is that not all of the emails are displayed in a folder. I have a folder with a bunch of system data emails that are collected throughout the day and in firefox
I can see ~20 while in IE 9 I can see them all. The inbox also has 5 emails in it but there is a scroll bar that is completely unnecessary in firefox but not IE 9. Do you have any thoughts on this? Thank you in advance.

There's no way, as there's nothing wrong with the server.
You will have to wait for the update from Firefox to get it fixed.
It's purely Browser issue As I said before.
Cheers,
Gulab Prasad,
Technology Consultant
Blog:
www.exchangeranger.com
Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 Performance Monitor Data Collector Sets

I've noticed that the Exchange 2013 install created two data collector sets within Performance Monitor:
ExchangeDiagnosticsDailyPerformanceLog
ExchangeDiagnosticsPerformanceLog
These sets are creating daily log files saved in C:\Program Files\Microsoft\Exchange Server\V15\Logging\Diagnostics\DailyPerformanceLogs that are about 500MB in size, which are filling up our system volume.
I've tried stopping them, but they get restarted automatically. I also tried deleting them, but they get recreated automatically. Is there a way to disable these? We have a 3rd party tool that we use for performance monitoring and would like to avoid having
to delete these log files on a regular basis to keep our system volume from filling up.
As a workaround, I've changed the path where the log files get saved to a non existent drive letter, but would still like to disable the Data Collector Sets completely.
Thanks,
-Cory

Do note,
These performance counters only take up 1 week and not more so it will be about 3-5 GB if you can`t spare this on you c disk you have not implemented any best practise exchange design.
specialy with todays JBOD SATA design your c disk will be 1TB +. Review your designs to match MS advise.
MCTS-MCITP exchange 2010 | MCTS-MCITP Exchange: 2007 | MCSA Messaging: 2003 | MCP windows 2000
Hello Martin,
Many of us are implementing exchange in a virtual environment, where disk is at a premium. Spending money on a 1 TB system drive is not a reasonable expectation. Even if that is best practice, there should be a way to manage the location and
size of these log files.
The inability to manage the location of log/performance data for centralization, or other reasons, is one more example of the disconnect between MS and their customer's use cases in regards to 2013.
These are the requirements for 2013 from MS:
At least 30 GB on the drive on which you install Exchange
An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
200 MB of available disk space on the system drive
A hard disk that stores the message queue database on with at least 500 MB of free space.
So your statement is invalid as 30 GB is not even close to deal with the amount of log and performance data that we cannot modify in any way.

Exchange 2013 CU3 Can't Access ECP from Office365 Enabled Account

We recently upgraded our Exchange 2013 server to CU3 to fix the OWA redirection error. Unfortunately, we've now noticed that any admin mailboxes that have been 'moved' to Office365 can not access ECP and instead get a redirect warning to OWA.
I had to create a new, onprem admin account to access in the meantime. This is the message I see:
Use the following link to open this mailbox with the best performance:
http://outlook.com/owa/ACME.onmicrosoft.com
X-FEServer: EXCHANGE
Date: 12/3/2013 6:13:23 PM
more detail...
I assume this is due to the fix for OWA redirection? How do I manage Exchange with my 'oncloud' mailbox accounts?

Hi,
I think it will be more suitable to ask this question on Exchange Online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

The Microsoft Exchange Administrator has made a change that requires you to Quit and restart outlook in Exchange 2013 CU3

I have a Exchange 2013, That has been running for a few months now since we moved it over, but now I get the Microsoft Outlook Message "The Microsoft Exchange Administrator has made a change that requires you to quit and restart Outlook." It only
shows up on certain users but not on others. What could be the problem? The only answers I have seen are for Exchange 2010.
All Help is much appreciated

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

Installation Error Installing Exchange 2013 CU3 on Server 2012

Hello,
When Installing Exchange 2013 on server 2012 I get the following error during Step 1 of 8 of Transport Service. I have installed and unistalled Exchange a few times, restarted the machine manually and removed exchange from AD, etc. to no avail.
Any suggestions will be very much appreciated.
Thank You.
VK
Error:
The following error was generated when "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASDat.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASDat.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " was run: "Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. This action is only valid for products that are currently installed. Error
code is 1605.".

Martina,
Thank you for your response. KB says that Machinepolicy and Userpolicy are to be set to Undefined and that is what I have.
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Users\Administrator> get-executionpolicy –list
Scope
ExecutionPolicy
MachinePolicy
Undefined
UserPolicy
Undefined
Process
Undefined
CurrentUser
Undefined
LocalMachine
RemoteSigned
VK

Exchange 2013 CU3 Fails "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception."

I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Organization Preparation
FAILED
     The following error was generated when "$error.Clear();
        install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

I have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
PS C:\Windows\system32> cd c:\temp\ex2013cu3
PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Extending Active Directory schema
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation completed successfully.
PS C:\temp\ex2013cu3>
The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
at 21% of Organization Preparation before finally failing with the following output....
PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for installation.
Performing Microsoft Exchange Server Prerequisite Check
    Prerequisite Analysis
COMPLETED
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
Configuring Microsoft Exchange Server
    Organization Preparation
FAILED
     The following error was generated when "$error.Clear();
        install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
ainController $RoleDomainController
" was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
ected.
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
ffected.
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS C:\temp\ex2013cu3>

Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

Windows Server 2013; Exchange Server 2013 with Cumulative Update 1
Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with
[xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid. See the Exchange setup log for more information on this error.
[xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
[xxx] [0] [ERROR] The supplied credential is invalid.
(Crosses - XXX - replace original values.)
I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely
conincidental:
The Security System could not establish a secured connection with the server
ldap/xxx.xxx/[email protected] No authentication protocol was available.
Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

Hi vhr1,
Based on my knowledge, the Event ID 40961 is a warning message.
This behavior occurs when we restart the server that was promoted to a DC. The Windows Time service tries to authenticate before Directory Services has started.
Found some resources for your reference even if the Exchange Version is mismatched:
http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx
http://support.microsoft.com/kb/823712/en-us
About the error message, "Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid."
The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.
Found a similar thread for your reference, hope it is helpful:
http://social.technet.microsoft.com/Forums/en-US/98e26ad6-8e43-4ef5-8ff9-e9fee6e76bda/bind-operation-is-invalid?forum=exchangesvrdeploylegacy
Feel free to contact me if there is any problem.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 CU3 Can't view permissions on mailbox in EAC

Recently upgraded to CU3. I'm not sure if my EAC problems are due to that or something else. I could have swore this worked before, but I am not 100% positive.
If I go to "Recipients > Mailboxes > Properties on a mailbox > Mailbox Delegation" it says "Please wait...". It stays like that for about 15-20 seconds, then finally comes back with: "error. Your request
couldn't be completed. Please try again in a few minutes". I hit OK and the boxes for Send As, Send on Behalf, and Full Access are all empty.
I can view permissions on that same mailbox with PowerShell.
Also, if I do the same process for a Distribution Group, then that works okay in EAC!

Hi
Almost the same problem here...
Editing a Resorce Room...
Request for URL 'https://InternalServerName:444/ecp/UsersGroups/EditRoomMailbox.aspx?pwmcid=8&ReturnObjectType=1&id=21b9ba56-12cf-4138-ba3d-9de2342f28b2(https://LoadBalancedExternalName/UsersGroups/EditRoomMailbox.aspx?pwmcid=8&ReturnObjectType=1&id=21b9ba56-12cf-4138-ba3d-9de2342f28b2)'
failed with the following error:
System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException:
Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Data.Directory.Recipient.NonUniqueRecipientException: Multiple objects with Sid S-1-5-32-548 were found.
Did you fix it?
Regards
Robban

Exchange 2013 CU3 monitoring

Similar Messages

Maybe you are looking for