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

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

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

Exchange 2013 SP1 RU4 Public Folder Permissions

Hi All,
Exchange 2013 SP1 RU4 Public Folder Permissions
We have a weird problem after migrating our PF from Exchange 2010 to 2013.
Users do not have permission to create or delete in PF even thou they have owner permissions.
Example:-
I have created a '\test1' folder in the root which has the following permissions (this works OK):-
Myself - Owner
Default - Author
Anonymous - None
I have created another folder '\admin\test2' folder which has the same permissions as above but i get the "cannot create the folder. you don't have appropriate permissions to perform this operation"
I get this problem across all of the folders that were migrated. clean folders created at the root with the correct permission function as per expected.
Regards
Paul Sheldon

Hi,
I recommend you use the Get-PublicFolderClientPermission -Identity publicfolder command to check the client access permissions to a public folder.
If possible, please remove permission and re-add permission to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

First exchange 2013 server install in coexistence: Recreating arbitration mailboxes first

Hi
We have exchange 2010 servers and I want to introduce the first exchange 2013 server.
Some of our arbitration mailboxes currently in 2010 have become corrupt and my initial exchange 2013 installation failed.
Question: Can I remove existing exchange 2010 arbitration mailboxes and recreate them using EXCHANGE 2013 "SETUP /PrepareAD"???????? Afterall there are no 2013 servers in the environment yet
I wonder if it will fail due to version incompatibilities
Thanks

Hi,
Agree with DJ Grijalva. Exchange 2013 /prepareAD will create the arbitration mailboxes for Exchange 2013. And the arbitration mailboxes between Exchange 2010 and Exchange 2013 are different. So I recommend you use the 2010 /prepareAD to recreate the arbitration
mailboxes for 2010.
Hope my clarification is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

New features in Exchange 2013 that can help speed recovery ?

What new features are available in Exchange 2013 to help speed data recovery ? anything change to the architecture which means it is no longer needed to restore mailboxes and replay logs prior to restoring data ?

Hi ITForum2013,
from the Exchange perspective backup and restore is Dumpster.
http://technet.microsoft.com/en-us/library/ee364755(v=exchg.150).aspx and, if applicable, you can run your Exchange Servers backupless. So more "speed" is the same improvement on IOps as for the EDB.
This is for availability of you mailbox data.
So you need to define a little more your goals of backup and recovery, while on the other hand there is no more backup "tool" outside of dumpster as you never need it from an Exchange Servers view. ntbackup is old style. :)
Regards,
Martin

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 - Admins can only log into one ECP server

Simple run down of my environment:
• Two AD sites (Site1 and Site2)
• One 2008 R2 domain controller at each site (DC1 w/ FSMOs and DC2) running AD forest function level 2008 R2
• One 2012 Std server with Exchange 2012 Std CU3 at each site (EX1 and EX2) – CAS/MBX on both, No DAG
• Half of mailboxes on each server
Using https://webmail.domain.com for all of our internal and external virtual directories. Adding /OWA or /ECP will get you into the respective site from either internal or external.
All Domain Admin/Exchange Admin (Organization Management) do NOT have mailboxes. Those individuals can log into ECP from https://webmail.domain.com/ecp, or FQDN or IP of EX2 only. If John Smith has no mailbox then he must use:
https://webmail.domain.com/ecp
or
https://ex2.domain.com/ecp
or
https://10.16.109.31/ecp
If EX2 goes offline or they use https://ex1.domain.com/ecp or https://10.16.108.31/ecp then none of the admins can login and they get the following:
Use the following link to open this mailbox with the best performance:
https://webmail.domain.com/owa/auth.owa
X-FEServer: EX2
Date: 2/18/2014 10:37:42 PM
s ECP or the https://webamil.domain.com/ecps ECP.
They can access EMS from either server and run Get-ECPVirtualDirectory and it shows what we would expect:
– https://webmail.domain.com/ecp
– https://webmail.domain.com/ecp
Why can an admin with no mailbox only log into the ECP on EX2? What is forcing the login to EX2 only? How can I move that “forced login” to EX1 if we ever get into a situation where EX2 is having problems? What happened in Active Directory or Exchange that
made EX2 the primary login server for ECP and OWA? My FSMOs are located at Site 1…the same location where EX1 is located. The same server that I cannot log into ECP directly.
~Rick

Any admin that is mail enabled can then only log into the server that hosts his mailbox. Admins without mailboxes can only log into EX2. And again, all admins can log into https://webmail.domain.com/ecp unless one of the servers goes offline
and that's when the problems occur. Nothing obvious or unusual regarding mail flow. Done various internal and external tests and have not seen anything obvious or in the logs.
Yesterday's change that MS Support had me do was to delete the ExternalURL for the ECP virtual directories. No difference. So, my latest update from MS Support that requested me to try today's change...
set-owavirtualdirectory “owa (default web site)” -RedirectToOptimalOWAServer $false
After performing an IIS reset and making sure replication had completed there was no difference. So, I am now forced to wait till Monday for MS to respond if the pattern stays at one email per day.
Has anyone with multiple servers at different AD sites been able to log directly into the either server like I'm trying? I get this problem in my labs and I even had MS, while on the phone, remote in to make sure I was setting it up properly.
The guy on the phone never said if their labs do the same thing cause they don't have multiple AD sites in their labs. In my lab if I have two servers at each site then I can log into both servers at the site, but not the other site. It appears it becomes
site dependent then.
MS has taken numerous logs and they are acting like this is the first time they've seen this. Yet I can reproduce it with no problem time after time. I'll create new VMs and start all over from scratch and make this happen every time I create a new AD/Exchange
environment (it does take me a while to build all those VMs from scratch). No fancy GPOs to AD and no radical changes to the Exchange servers. Other than obvious config changes to make sure email can flow internally and externally, this is pretty much out
of the box.
~Rick

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>

Import Calendar Entries to Exchange 2013 Causes Outlook Calendar View Problems

Today I was working on a way to import company holidays for 2014 into people's calendars. We're running Exchange 2013. Most users have Outlook 2010, but I'm on the bleeding edge with Outlook 2013.
The best method I found online for adding events to everyone's calendar involved creating a calendar in a PST file that contained all of the company holidays and then using the Exchange 2013 Management Shell to import the PST file into people's calendars.
I created the calendar in a PST using Outlook 2013. Each holiday is an all day appointment. I then used the management shell to import those appointments into my calendar. Outlook was running when I ran the import.
After the import completed, I went to look at my calendar and Outlook 2013 crashed. I restarted it, clicked on my calendar and it crashed again. After some digging, I found a suggestion that I start Outlook with /cleanviews. That seems
to have corrected the problem. All appointments appear as expected. Well, that was ugly. But I'm the only one on Outlook 2013 right now, so it's not a showstopper.
I then found a victim running Outlook 2010 for my next import experiment. Outlook 2010 didn't crash. But the calendar view did reset to a list view instead of whatever the user was running before. Strange... I ran the test again with
another person and was able to reproduce the result. All appointments are present, but Outlook feels the need to change views?
Does anyone have a suggestion for how to import these appointments without the calendar view being reset? I don't want to think about all the support calls we're going to get when people's calendar view gets changed to a list view.
Thanks
Patrick

Hi Patrick,
Is the use able to change the calendar view manually? Please check whether all calendar items are in list view both in OWA and Outlook? Please try to import the PST file from Outlook side to check whether the issue persists.
Thanks,
Winnie Liang
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 Can't view permissions on mailbox in EAC

Similar Messages

Maybe you are looking for