Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1
site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)
Problem
EMS on CU5 return very slow result.
EMS on SP1 still ok.
Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
reply from Social.technet

Hi,
Have you used the above cmdlets to check your Exchange server health?
"all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

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)

Unable to manage/create Resources, Room/Equipment, Exchange 2013 CU5

Hi
We have a mixed 2007SP3 and Exchange 2013 CU5 eviroment.
Pretty much since CU3 (first version we installed) we have had problems with resources, but since SP1 we cannot create or edit resources.
We have a root domain and three child domains, all Exchange 2013 servers are in the root domain. The Exchange 2007 servers are located in the root and two of the child domains.
When creating a Room we get this:
Note: Pulsar is the E2013 CU5 Mailbox-server, Panerai is a Domain Controller in a child domain.
The Room is the listed but when trying to open it we get this:
In the mailbox-server log we get this log: ID 4 Source MSExchange Control Panel
Current user: 'newsec.se/Consultants and Commons/IT-Stureplan/ADMINISTRATOR'
Request for URL 'https://pulsar.newsec.se:444/ecp/UsersGroups/EditRoomMailbox.aspx?pwmcid=37&ReturnObjectType=1&id=638db8e2-355c-4e44-9e01-f577c470f297(https://owa.stronghold.se/ecp/UsersGroups/EditRoomMailbox.aspx?pwmcid=37&ReturnObjectType=1&id=638db8e2-355c-4e44-9e01-f577c470f297)'
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.
at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.FindMiniRecipientBySid[TResult](SecurityIdentifier sId, IEnumerable`1 properties)
at Microsoft.Exchange.Management.ControlPanel.RecipientObjectResolver.ResolveSecurityPrincipalId(IEnumerable`1 sidPrincipalId)
at Microsoft.Exchange.Management.DDIService.MailboxPropertiesHelper.FilterEntSendAsPermission(DataRow inputRow, DataTable dataTable, DataObjectStore store)
We tried to put the AD-account in different domains/OUs... but the same problem occurs.
I have a case with MS-support (114051511444067) but I throw it up here also.
Regards
Robban

Hello Robban,
I didn't see your answer... (no mail notification ?)
I opened a MS ticket (114081411702089) and I got an answer :).
If you check security in ADSIedit.msc on your mailbox database object, you may find ACL entry for the group with the SID reported in the "application error event"
example : (CN=YourBDD,CN=Databases,CN=Exchange Administrative Group (FYDBOHF23SPDLT),CN=Administrative Groups,CN=YourOrganizationName,CN=Microsoft Exchange,CN=Services,CN=Configuration,CN=YourDomain,CN=local)
* "Domain\administrators" (SID S-1-5-32-544
for me )
* "Domain\account
operators" (SID S-1-5-32-548
for you )
Sources : http://support.microsoft.com/kb/243330/en
The "Domain\administrators"
group is not present by default on the exchange organization AD arborescence. I 've checked my customer exchange installation, it seem's the same for "Domain\account operators" group.
To check, you can :
* create a new
mailbox database, and modify the security on these database AD object to remove "Domain\account
operators" ACL (You may have to disable inheritance and copy existing security before)
* Create a ressource mailbox on the new database and edit it using EAC. If your are like me, you
will also be able to edit mailbox permission in EAC for a mailbox on the new database.
If it works, you can validate with MS support that "Domain\Account Operators" group should not have acl on your exchange organisation AD object, and remove the ACL
after a good Active Directory backup
I hope it may help you,
Regards,
Florian

Exchange 2013 CU5 - Outlook Web Access - Error 9646 with HTTP - No error with HTTPS

Hello everyone
i have a strange issue which i actually do not have an idea about what is going wrong.
- Exchange 2013 CU5
- SSL Offloading enabled - Virtual directories configured accordingly
When a user logs in to OWA via HTTP - after a while he sees the inbox but does not see any mail details.
He only sees "Error: Your request can't be completed right now. Please try again later."
After a while i also get an eventlog "9646" with too many open OWA sessions for that user.
Regardless which limit i set in the registry for this - the error does come back - even with 512 sessions allowed.
Working with HTTPS instead of HTTP then EVERYTHING works fine ... ?
Any idea on this?
Actually i am totally lost ...
Best regards
Jörg
Ihr zertifizierter VMware Partner Enterprise Solution Provider, IBM Advanced Partner, Datacore Partner, Microsoft Silver Partner / Solution Provider und Microsoft Small Business Partner. HEGO Informationstechnologie GmbH Telegrafenstrasse 8 D 42929 Wermelskirchen
Geschäftsführer: Jörg Hermanns, Ralf Gogolin Amtsgericht Köln HRB 36509 Fon: +49 (0) 21 96 / 8 82 97 - 0 Fax: +49 (0) 21 96 / 8 82 97 - 23 Web: www.hego-it.com

Hi,
Please confirm if the following features are added in your server manager:
•.NET framework 4.5 -> WCF Services -> HTTP Activation
•Windows process activation service -> Process model
•Windows process activation service -> Configuration APIs
If not, please add these features. Then ran IISReset \noforce from a Command Prompt window to restart IIS service. Also recycle Application Pools in IIS manager.
For more information about the IIS Prerequisites for Exchange 2013, please check the windows feature listed in the following article:
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
Regards,
Winnie Liang
TechNet Community Support

Update Exchange 2013 CU5 to CU7 - Installation Order

Hi,
I have a multi-site, multi-DAG, Exchange 2010 and Exchange 2013 CU5 installation. All servers are multi-role. We are about to commence a server update to CU7 for all of the Exchange 2013 Servers.
What is the Microsoft supported order in which to upgrade the servers?
Can I do the upgrades over a number of nights, does everything need upgrading together, should I do it site at a time or a DAG at a time?
Are there any TechNet articles which explain the supported method? It is important that during the update to CU7 the installation stays in a supported configuration.
Thanks in advance.

Hi,
As Andy suggested, you need to upgrade Mailbox servers and then upgrade Client Access servers. What's more, if your DAG have more nodes, at first, you need upgrade all non-PAM nodes and then upgrade PAM node.
Here is a helpful blog for your reference.
How to Apply Exchange Server 2013 RTM to Cumulative Update 1 (Note: Though it is upgrading from Exchange RTM to CU1, it also applies to upgrading from Exchange 2013 CU5 to CU7 about the required order issue.)
http://blogs.technet.com/b/justin_gao/archive/2013/04/09/you-need-to-know-how-to-apply-exchange-server-2013-rtm-to-cumulative-update-1.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 with Outlook on RDS Server is extremely slow

Exchange 2013 CU5 on Server 2012 R2 fresh install/new to domain; Outlook 2010 or 2013 on Remote Desktop server not in cached mode is slow to open, search and send messages with attachments. Opening messages and opening attachments runs quickly.
My test mailbox has 300kb worth of mail in it and sending a message with a 5Mb attachment locks up Outlook for close to 1 minute and takes another 30 to 90 seconds to disappear from the outbox and and move to sent items. This issue does not present
itself in OWA. My current testing RDS environment is a fresh install of Server 2008 R2 with Outlook 2013. No additional add-ins or AV running on the Exchange server or the test RDS server.
When cached mode is enabled, Outlook runs better as shown in Outlook 2010 (+ Exchange 2013) works extremely slow; however, I don't consider this an option because there isn't enough drive space on the RDS server to cache all of the user profiles.
Other Exchange environments - Outlook 2010 or 2013 in an RDS environment (non-cached) with Exchange 2007 or 2010 - don't show the same performance issues. Moving within Outlook and sending large attachments runs quickly.
I have checked Exchange throttling settings and monitored logs, but have not found cases where my test user is being throttled. I have also looked at turning off IPv6 based on another post's suggestion; however, I have seen conflicting information
about disabling IPv6 for Server 2012 R2, so I have not yet gone down this path.
The Exchange server is a VM on a new VMware host and has assigned 8 cores from Intel Xeon E5-2640 procs and 16GB RAM; 1TB thick provisioned database volume on a RAID 5 array with 6 x 10k RPM SAS drives. Disk queues are low on the Exchange server (in
the .20 to .70 range). My test RDS server is on the same VMware host on the same vSwitch. Another test system is on a different system, but exhibiting the same behavior.

Hi,
How about the suggestion from Festivalman?
Feel free to contact me if there is any update.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Migrate mailboxes from Exchange 2013 to Exchange 2010

Hello,
We have a merger and would like to know if it is possible to migrate mailboxes from Exchange 2013 to Exchange 2010 in a cross-forest scenario.
Or should we first upgrade destination Exchange 2010 to 2013?
Peteris

Hi Peteris,
Based on my tests, we can move mailboxes from Exchange Server 2013 to Exchange server 2010. You can use the Prepare-MoveRequest.ps1 script in the EMS to prepare mailboxes for cross forest moves.
For more information about it, here is a helpful article for your reference.
Prepare mailboxes for cross-forest moves using the Prepare-MoveRequest.ps1 script in the Shell
http://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx
Hope my clarification can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Cannot send mail from Exchange 2013 to Exchange 2007

I have an
Exchange 2007server with all roles in the same server (Version:
08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
(full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
few articles on the Internet.
Any suggestions?

These two sentences are in conflict : "I can also send
internal mail
from Exchange
2007 to
Exchange 2013. But
the problem is
that I am unable
to send from Exchange
2007 to
Exchange 2013. "
Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Damir

OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanks

Hi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang

Migrating to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
Many thanks.

Hi,
You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
Kindly mark this as answer if it fulfill your requirements. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Exchange 2013 and exchange 2000

Hy guys...
I have this problem...i have a dommain controller x.com and i installed Exchange 2013 on it. I have another dommain controler
y.com with Exchange 2000. Thex.com dommain sends and receives mails from other Exchange 2013 servers but when it comes to
y.com dommaind i am only able to send emails to
[email protected] I cannot send emails from y.com
(Exchange 2000) tox.com (Exchange 2013).
Bothx.com dommain controller and y.com dommain controller are in the same network and i fave connectivity between them.
What might be the problem?
Than u,
M.S

Hi,
Firstly, it’s not supported to install Exchange 2013 and Exchange 2000 in the same organization and it’s not recommended to install Exchange server on Domain Controller.
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.exchange2000or2003presentinorg(v=exchg.150).aspx
To understand more about the mail flow issue, I’d like to confirm your meaning that two DCs are in the same network.
If they are in the same forest, it’s by design that Exchange 2013 and Exchange 2000 cannot coexist.
For general mail flow troubleshooting , we can use telnet to check it.
For more information, you can refer to the following articles:
http://technet.microsoft.com/en-us/library/bb123686(v=exchg.150).aspx
http://msexchangeguru.com/2013/07/29/troubleshooting-mail-flow-issues/
Note: 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.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Is there Exchange 2013 view Exchange Management Shell command similar to Exchange 2010

Hi,
Is there anything similar in Exchange 2013 (Please refer the image). In Exchange 2010 if you make any changes via Management console you could go to "View Exchange Management Shell Command Log" and see what shell command it ran in the background.
It was very handy to copy shell command from here and then run it from shell in case you need to make bulk changes rather than try to find out the shell command from scratch.
I was wondering if there is anything similar in Exchange 2013.
Thanks,
Raman

Probably in SP1...
Keep your finger cross ;)
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://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 CU5 will not install, please help

Hi everyone
Please help, I am trying to upgrade Exchange 2013 SP1 to CU5 but it just stops at the following point, please help:

Hi,
Have you disabled any third-party firewall or AV programs for a test?
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013, cu5 - need to run /m:RecoverServer - am I screwed?

One other option - you could reinstall the OS on the server with a repair install from an ISO or a DVD. That'll preserve the version of exchange on it. It's a slim shot but it might work.
Either way, some sort of clone, copy, backup of those LUN's and the data contained therein would be a good idea.

Ok - for reasons beyond my control, our Exchange Server died on me (INACCESSIBLE_BOOT_DEVICE) with no possibility of repair that I can find.
I built a new VM with the same name, etc, etc, and reattached the iSCSI LUNs for the Databases and Logfiles - however, when I run Setup with the /m:RecoverServer option, I'm greeted with:
Prerequisite Analysis
Exchange Server version 15.0 (Build 913.22) or later must be used to perform a recovery of this server.
The problem is, the latest ISO on Microsoft's VLSC is SP1, which is CU4 - Build 913.22 is CU5. Do I have any hope of recovery here, or am I boned?
This topic first appeared in the Spiceworks Community

IPhone 7 & 8 can't connect to Exchange 2013 CU5

I am getting call from users with iPhone and iPads that can't connect to our Exchange 2013 server. They get a error that the server can't be found. I can take the same account and run Microsoft online connectivity test and it passes. They don't have problem
with Outlook. Just the iPhone and iPads.
Matt Stehouwer Michigan State University

The error message I get is Exchange Account “Unable to verify account information”. This appears after the first screen that I guess you would call the autodiscovery screen if I click on that I am left on the auto discovery screen until I click cancel
I don’t advance to a screen that allows me to type the server or anything. I did the first time or two get the advanced setup screen that allowed me to type in a server but after that It wouldn’t take me to that screen again.
Looking at the cert idea.
Matt Stehouwer Michigan State University

Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.

Similar Messages

Maybe you are looking for