Mailbox move slow performance - RelinquishedWlnStall on Exchange 2013

I see a number of my mailbox moves going into a stalled state migrating from Exchange 2007 to 2013. I have paired back the number of simultaneous moves to 7 max. This has helped, but not eliminated the problem. Looking at the MoveRequestStatistics
I see that StalledDueToWriteCpu number is high. No other counter is of concern.
I see the status shows as below;
Informational: The request has been temporarily postponed due to unfavorable
server health or budget limitations. MRS will attempt to continue processing
the request again after 4/23/2015 10:39:02 AM.
Does this mean that the CPU is spiking to a high level and causing the mailbox move to stall? I have 8 cores allocated to this server 4 of the cores are averaging around 80% the other 4 about 30-40%.
Thanks

Hi BTRowdy1,
Thank you for your question.
By the information reminder, mailbox movement will be stopped because you have high hardware usage. it occurred when the server have some performance issues, for example hardware performance, you could add hardware(eg: memory) for move mailbox, we could
move few mailboxes at the simultaneous.
Are there any other applications on this server which occurred on CPU?
I suggest we move mailboxes out of production. In addition, we could monitor it for 24 hours if there is any improvement. If not, we could create a new move request for mailbox movement.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Similar Messages

Performance counters for exchange 2013 mailbox & cas servers?

what are the Performance counters for exchange 2013 mailbox & cas servers?
similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013.

Hi,
Please see this:
Ask the Perf Guy: Sizing Exchange 2013 Deployments
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Hope it is what you need.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Multiple domain mailboxes for one AD user in exchange 2013

I just wanted to make sure that this hasn't changed in exchange 2013 or if there's a better way to do this
we have a few users that need an email for companyA.com and CompanyB.com. For easy separation we've decided to create a separate mailbox for each email. Right now the only way i can figure how to easily associate both mailboxes with 1 AD user is to set up
their main email as their default mailbox, then create a shared mailbox and grant full permission for that user. Then in Outlook they have access to both accounts from 1 profile.
However I'm not sure how this would work for mobile access. In Office365 connecting to 2 exchange accounts on a mobile device was pretty straight forward since each mailbox had a unique login. I know when a shared mailbox is created, a disabled user
is created in AD, I'm wondering if i can enable that account and then the user uses that login to connect to that account through their mobile device. Or maybe theres a simpler way to accomplish this goal?

we have a few users that need an email for companyA.com and CompanyB.com.
Hi Derek,
Why not just create an additional email address for the users?
"You can use the EAC or the Shell to add or remove an email address for a user mailbox. You can configure more than one email address for the same mailbox. The additional addresses are called
proxy addresses. A proxy address lets a user receive email that’s sent to a different email address. Any email message sent to the user's proxy address is delivered to their primary email address, which is also known as the
primary SMTP address or the default reply address."
Add or Remove Email Addresses for a Mailbox
http://technet.microsoft.com/en-us/library/bb123794.aspx
"create a shared mailbox and grant full permission for that user"
Do you mean a few users have a shared email address? For example:
UserA:
Primary(main) address: [email protected], shared address:
[email protected]
UserB:
Primary(main) address: [email protected], shared address: [email protected]
If not, you can just create an addtional address for the users.
If you have any feedback on our support, please click
here
Frank Wang
TechNet Community Support

Cannot Adding Mailbox Server for Database Copy for Exchange 2013 SP1

Before I upgraded to 2013 SP1 everything works find but after I upgrade to SP1 I cannot add database copy. the details are...
I have 2 sites
Site 1 : 4 Mailboxes (Mailbox01,Mailbox02,Mailbox03,Mailbox04)   + 2 CAS
Site 2 : 2 Mailboxes (Mailbox05,Mailbox06)   + 2 CAS (just for standby site)
So I have 2 DAG group  (6 Mailboxes separate to 3 Mailboxes for 1 DAG group Mailbox01,Mailbox02,Mailbox05 for DAG1 and Mailbox03,Mailbox04,Mailbox06 for DAG2)
After I upgrade Exchange 2013 to SP1 , I try to create new database on Mailbox01 and after that I try to add mailbox02 and mailbox05 to database copy of new database that I created.
"Mailbox05 can added to be database copy but Mailbox02 cannot add database copy for it , Error "Network path not found" occur" but Im very sure that path is the same for each mailbox database server.
so I try to create new database on Mailbox 03 and add database copy on mailbox04 and mailbox06.... the result is the same only Mailbox06 can add mailbox copy of database.
It look like I cannot have 2 mailbox in site 1 for database copy of each new database (I already try to create new database on Mailbox 02 and add database copy on mailbox01 and mailbox05 , the result is only mailbox05 can be database copy of database).
Please help me to fix this out.

Hi,
I recommend you check if the Remote Registry service is running on Mailbox01, Mailbox02, Mailbox03 and Mailbox04. If not, please start it and then add mailbox database copy to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Office mail merges are extremely slow after upgrade to Exchange 2013

Ever since we migrated from Exchange 2007 to 2013 SP1, our employees have reported that mail merges are taking triple the amount of time to send messages. What used to take an hour is now 3 to 4 hours. Some offices are required to send upwards of 6,000
messages at a time. I know Exchange 2013 handles throttling differently than previous versions however the default (global) ThrottlingPolicy was sufficient with our previous 2007 installation. I've never had to deal much with Throttling so I'm not exactly
sure of what settings I should be looking at....also I'm not sure if this would even be related to throttling. Has anyone experienced this issue before with Exchange 2013 and could you provide any recommendations or settings that I need to be focusing on in
relation to Outlook client connections? We are currently using the GlobalThottlingPolicy for all users.

Hi,
What’s the version of Office?
The following Outlook client versions are fully supported by Exchange server 2013.
Outlook 2013
Outlook 2010 SP1 with November 2012 Cumulative Update ( available from
http://support.microsoft.com/kb/2687623 )
Outlook 2007 SP3 with November 2012 Cumulative Update ( available from
https://support.microsoft.com/en-us/kb/2687404 )
I suggest to upgrade one office client to Outlook 2013 (with word 2013) to check this issue.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Unable to move mailbox to newly created database in exchange 2013

Hi, i created a new database in our existing exchange server 2013 sp1 and i was trying to move my mailbox to the newly created one using the EAC. But the mailbox is not getting moved and i am not receiving any errors. Is there anything else i need to do
after creating the database.
Please advise.

Hello
lets play again:
new-moverequest -identity useremailaddress -targetdatabase new database
after two minute get move req log
get-moverequest -identity useremailaddress |get-moverequeststatistics -includereport |fl
or if have got more DC specified one Dc with -domincontroller DCname
sorry my english

Search-MailboxAuditLog is empty - Mailbox Audit Logging not working in Exchange 2013 CU6 environment

Hello,
i activated Mailbox Audit Logging for Admin, delegate and owner with all supported operations (update, delete, etc..)
like mentioned here:
http://exchangeserverpro.com/using-exchange-server-2013-mailbox-audit-logging/
But also two days later (and also one Server reboot later) search-MailboxAuditLog is still empty.
any ideas how to fix this?
Best,
martin

Hi S.Nithyanandham,
i looked up the mailboxfolderstatistics. There are items in the folder:
[PS] C:\Windows\system32>Get-MailboxFolderStatistics mailboxname |where{$_.Name -like "*audit*"}
RunspaceId : a95e32b8-93c3-4330-8d42-45cade9d64d4
Date : 18.09.2014 16:35:20
Name : Audits
FolderPath : /Audits
FolderId : LgAAAADmBpGVdb8iQp3F89WOcmcHAQBpQNFODkTESLeLj74B887wAAAAAAESAAAB
FolderType : Audits
ItemsInFolder : 147
DeletedItemsInFolder : 0
FolderSize : 434.2 KB (444,649 bytes)
ItemsInFolderAndSubfolders : 147
DeletedItemsInFolderAndSubfolders : 0
FolderAndSubfolderSize : 434.2 KB (444,649 bytes)
OldestItemReceivedDate :
NewestItemReceivedDate :
OldestDeletedItemReceivedDate :
NewestDeletedItemReceivedDate :
OldestItemLastModifiedDate :
NewestItemLastModifiedDate :
OldestDeletedItemLastModifiedDate :
NewestDeletedItemLastModifiedDate :
ManagedFolder :
DeletePolicy :
ArchivePolicy :
TopSubject :
TopSubjectSize : 0 B (0 bytes)
TopSubjectCount : 0
TopSubjectClass :
TopSubjectPath :
TopSubjectReceivedTime :
TopSubjectFrom :
TopClientInfoForSubject :
TopClientInfoCountForSubject : 0
SearchFolders :
Identity : mailboxname\Audits
IsValid : True
ObjectState : New
What do you think?
why cant i search and find these entries the auditlog?
best,
martin

Exchange 2013 mailbox migration from third party cloud to on premises

Hi,
we are currently utilizing a third party exchange 2013 cloud service to host user's mailboxes ( intermedia), now we implemented an exchange 2013 on-premises environment in Hyper V infrastructure and want to plan migration of mailboxes and related configuration.
cloud and on-premises environment have same SMTP domain ( Eg: XYZ.ORG) and currently an additional Temporary SMTP domain ( XYZ.CO ) used to test the external mailflow of on-premises since xyz.org is registered with cloud.
we need to migrate all mailboxes to on premises and enable XYZ.ORG for on-premises.
Pls suggest the prerequisites,steps, best practices for migration
Thanks in advance.

Hi Sumesh,
1. Please make sure your mails are flowing correctly using XYZ.CO domain. Hope you have XYZ.ORG also created in Exchange.
2. Hope you already created the users in your Exchange2013 server and distribution groups for current users
3. You plan a weekend for changing your MX records.
4. Change MX and A records to a lower TTL days before the migration to decrease DNS update time on migration day
5. Export Hosted Exchange data for each user to PST files using the PST capture tool and move your PSTs to a centralized location.
6. Change MX and A records to point to on-premises Exchange 2013
7. Import Hosted Exchange data from PST files into the new Exchange profiles
Please check these as well
http://community.office365.com/en-us/b/office_365_community_blog/archive/2011/08/15/exchange-hybrid-configuration-tips-moving-cloud-based-mailboxes-to-the-on-premises-organization.aspx
http://technet.microsoft.com/en-us/library/hh781036(v=exchg.141).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/microsoft-pst-capture-tool-part1.html
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Auto-Mapping Exchange 2013 Mailboxs in an Exchange 2010 Mailbox

We're in the middle of migrating mailboxes from Exchange 2010 to Exchange 2013. Many of our users have Auto-Mapped mailboxes as well. In my testing, I've found that I cannot Auto-Map a mailbox that's on Exchange 2013 in a Exchange 2010 mailbox. I can manually
add it and it works fine. Is this by design with this type of coexistence or is there a fix for it? Our current Exchange 2010 environment is at SP3 with UR2.
Orange County District Attorney

This issues is fixed in UR5 so suggest you to upgrade Exchange 2010 to SP3 UR5.
Reference Thread: http://social.technet.microsoft.com/Forums/exchange/en-US/a2aa4163-f74b-401f-aec5-13324e6b29c8/exchange-2010-mailbox-not-able-to-access-automapped-exchange-2013-cu3-mailbox?forum=exchangesvradmin
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2013 - EMC 2013 - View Mailbox Size With Column In EMC - How To View Mailbox Size Exchange 2013?

Is there a way to add a column to show each users mailbox size in the EMC for Exchange 2013 under recipients > mailboxes?
Such a simple tool would be so much easier for administrative purposes.

Hi,
There is no way to add the column of mailbox size back to EAC in Exchange 2013, I don't know why this option is removed and there is no official document explaining this issue.
To get the mailbox size, we can use commands to get it.
Thanks for your understanding.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 - outlook in LAN environment very slow upload but fast download - not using 'use cached exchange mode'

Hi,
I have Exchange 2013 setup in a new environment (no migration) and it is working great except I just realized there is a big problem.
I notice the following
Problem 1:
Outlook 2010 with sp2 with cached exchange mode on: when I import the pst into outlook, it imports fine but the sync is extremely slow. It uploads to the Exchange 2013 mail server at 20-70KB/sec (bytes) via LAN.
Problem 2:
Outlook 2010 with sp2 with cached exchange mode off: when I import the pst into outlook, it imports extremely slow. It uploads to the Exchange 2013 mail server at 20-70KB/sec (bytes) via LAN.
More info:
-user1 has 1GB of mail and when setting up the user on a new pc with outlook with cached exchange mode on, it downloads the mail very fast. It downloads at 40-80 Mbps/sec (bits).
-I have Exchange 2013 with CU3 with win2k12 non r2.
Why is the download so fast from Exchange 2013 but the upload to Exchange 2013 is extremely slow? How do I fix this?
Thanks

I did some more testing.
I setup a test environment with:
-Exchange 2013 SP1 on win2k12 r2
-Outlook 2010 SP2 on windows 7 sp1
-Outlook 2010 SP2 on windows 8.1
-Outlook 2013 SP1 on windows 8.1
Both windows 7 and windows 8.1 have the very slow upload issue to Exchange 2013. Windows 7 upload to Exchange 2013 is around 20-70KB/sec (bytes) via LAN. Windows 8.1 upload is a bit more responsive at around 500-600KB/sec (bytes) via LAN.
I changed the TcpAckFrequency to 1 for windows 7 and 8.1 and the problem went away. The upload on both Windows 7 and 8.1 was going at megabytes after the change.
I hope Microsoft fixes this soon.
PowerShell script to have this automated via GPO:
http://community.spiceworks.com/topic/571571-outlook-slow-after-migrating-to-exchange-2013
PowerShell Script:
$strGUIDS=[array](Get-WmiObject win32_networkadapter -filter "netconnectionstatus = 2" | select -expand GUID)
foreach ($strGUID in $strGUIDS) {New-ItemProperty -path HKLM:\System\CurrentControlSet\services\Tcpip\Parameters\Interfaces\$strGUID -propertytype DWORD -name TcpAckFrequency -value 1}

Exchange 2007 to Exchange 2010 cross forest simultaneous mailbox move limits

Hi All,
I am testing the throughput of mailbox moves from Exchange 2007 to Exchange 2010 cross forest. Single mailbox moves seem to be quite fast and I am not concerned about network, disk IO or server resource limitations, however I have not tested multiple simultaneous
mailbox moves to determine what the Exchange limitations are. If anyone could identify the limitations of the items below it would be much appreciated:
Limit of Exchange 2007 simultaneous mailbox moves per database
Limit of Exchange 2007 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2007 simultaneous mailbox moves per CAS server
Limit of Exchange 2010 simultaneous mailbox moves per database
Limit of Exchange 2010 simultaneous mailbox moves per Mailbox server
Limit of Exchange 2010 simultaneous mailbox moves per CAS server
Any other Exchange 2007 or 2010 hard coded limits
Thanks in advance.
Michael.

My usual answer to this question is that Microsoft set these limits for a reason. Increasing them may not offer you much in the way of benefits if you end up slamming the server. I generally recommend that you leave them alone.
I have had occasional opportunities to change these constraints, most notably back during a migration to Exchange 2003 and international mailbox moves (Asia to U.S.) where the limiting factor was network latency. I was able to increase the number of
concurrent threads to 16 from the default 2 and there was still available bandwidth because the process was limited by the latency.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Help With Migration From Exchange 2007 To Exchange 2013

We have an Exchange 2007 Server with Service Pack 3 and Rollup 12 applied.
I installed a new Exchange 2013 Server and then immediately applied CU3.
I am following this Technet article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The only deviation from the instruction I have had to do is in Part 2, section 4 “Configure offline address book (OAB)”.
Instead of entering:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
I had to enter:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"
I believe this is due to the fact that the writer installed from an Exchange 2013 CU1 disk and I only had Exchange 2013.
Also when I tried to run:
Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server SRV-EX2013
I get the following error:
Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'SRV-EX2013'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform
this operation. Error message : 'Catastrophic failure (Exception from RESULT: 0x8000FFFF (E_UNEXPECTED))'.At line:1 char:24+ Move-OfflineAddressBook <<<<
-Identity "Default Offline Address Book" -Server SRV-ex2013+ CategoryInfo
: InvalidResult: (Default Offline Address Book:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException
+ FullyQualifiedErrorId : 9250969C,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook
However when I looked at the address books in EAC I could see that “Default Offline Address Book (Ex2012)” was the default and that it contained a copy of the Global Address List. So I did nothing else about it.
I am now at Part 3, section 7 “Move Mailboxes” and it keeps failing.
I am using the EAC so that I at least see the error as using the powershell brings back no results.
Anyway it Syncs the 18 items in the mailbox then fails with:
Data migrated: 936.7 KB ‎(959,145 bytes)‎
Migration rate: 0 B ‎(0 bytes)‎
Error: MigrationPermanentException: Error: An error occurred while updating a user object after the move operation. --> Unable to generate the e-mail address. Unable to load address module ‎'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\address\SMTP\AMD64\inproxy.dll‎'
for address type ‎'SMTP‎'. Additional message: ‎'Access is denied‎'.
Help??
Tony

Hi,
You can't configure Exchange 2013 to generate other OAB versions, and the OAB generation occurs on the Mailbox server on which the organization mailbox resides.Therefore, to move OAB generation in Exchange 2013, you must move the organization mailbox. You
can only move the OAB generation to another Exchange 2013 mailbox database. You can’t move OAB generation to a previous version of Exchange.
And please refer to the following articles :
Moving OABs between Exchange versions
If you want to upgrade from exchange 2007 to exchange 2013,I recommend you refer to the following article:
Upgrade from Exchange 2007 to Exchange 2013
Exchange version
Exchange organization coexistence
Exchange 2007
Supported with the following versions of Exchange:
Update Rollup 10 for Exchange        2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the
organization, including Edge Transport servers.
Exchange 2013 Cumulative        Update 2 (CU2) or later on all Exchange 2013 servers in the
organization.
Install Exchange 2013 in an Existing Exchange 2007 Organization
You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place
upgrade from Exchange 2007 to Exchange 2013.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 CU5 fresh install suffering issues with services not starting and coexistence with 2007

Hi everyone,
Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.
On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.
The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's
The main problems are as follows:
There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport
Service.
The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long... It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
I receive an error in the Event Log regarding RPC over HTTP Proxy
to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down
this post
The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs
for over chatty warnings about disk space (the warning is that we have loads of space...)
This is a brief outline of the environment:
Exchange 2007 SP3 RU13
UK - Two physical locations in a stretch LAN (100Mb WAN)
4 x CCR Cluster Mailbox Servers in two separate CCR Clusters
Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.
Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.
Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.
2 x Virtual Windows 2003 R2 - Hub Transport Servers
2 x Virtual Windows 2003 R2 - Client Access Servers
1 x Virtual Windows 2003 R2 - Unified Messaging Server
1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)
US - One physical location
1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server
Exchange 2013 CU5
UK - Installed into same site along side Exchange 2007 servers
1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server
Problem 2 Error Message - Please note, server names and domain name changed:
Log Name:      Application
Source:        MSExchange Front End HTTP Proxy
Date:          18/07/2014 10:00:37
Event ID:      3005
Task Category: Core
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EXC2013.domain.local
Description:
[RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
Event Xml:
<Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
<System>
    <Provider Name="MSExchange Front End HTTP Proxy" />
    <EventID Qualifiers="32768">3005</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
    <EventRecordID>64832</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EXC2013.domain.local</Computer>
    <Security />
</System>
<EventData>
    <Data>RpcHttp</Data>
    <Data>EXC2007CAS1.domain.local</Data>
    <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
    <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
</EventData>
</Event>

Hi Off2work,
I've gone through the article and the Get-OutlookAnywhere commandlet looks fine (especially when compared with our working CAS).
Having looked through IIS I have spotted two additional misconfigurations with a missing setting to require SSL on the RPC folder and also the .NET version was not set.
I've now set those to Require SSL and .NET 2.0.5072 however this has made no difference following restarted of both 2007 CAS and 2013 servers.
I could potentially reinstall the CAS server or additionally decommission it as we have two of them and the other is not causing any errors with the 2013 server. This broken CAS server doesn't even have DNS records (except it's own hostname) or firewall
rules pointing to it, nor does it have any active client connections if I check with a quick netstat -a
As for UM, it's next on my list following some client/server connectivity testing so I have not yet assigned the SSL to the services or setup the dial plans, etc.
The services do start most of the time, but others then don't so it's not a consistent issue with just this service. On my current boot, the DAG Management service failed to start, but again I don't have a DAG implemented yet.
I will see if UM drops out of that list once I've configured it shortly
Thanks for taking the time to respond (and that goes to DareDevil too)

Mailbox move slow performance - RelinquishedWlnStall on Exchange 2013

Similar Messages

Maybe you are looking for