Exchange 2013 - RCA reports RPC Proxy can't be pinged (404)

Hi, I've searched extensively and spent hours trying to fix my problem and nothing in the forums has addressed yet.
I have a new exchange server 2013 SP1 and Outlook 2013 clients can't connect. Outlook states Exchange Server is Unavailable.
This led me to Microsoft RCA. RCA reported that the RPC Proxy can't be pinged with a 404 error. But I CAN visit the server RCA references a step or two above and am treated to a white page, no 404. (
https://xch.domain.com/rpc/rpcproxy.dll?xch.domain.com:6002 )
I have set ExternalAuthenticatoin to Negotiate and internal to NTLM, I have set outlookProvider to
[PS] C:\Windows\system32>Get-Outlookprovider
Name Server CertPrincipalName TTL
EXCH msstd:*.domain.com 1
EXPR msstd:*.domain.com 1
WEB
1
The SSL Certificate is a trusted one, the External URL is set properly in the server settings via ECP as well.
Any ideas would be greatly appreciated. I'm tired and incapable of listing all of the steps I've tried, but if you know of any tips for troubleshooting and fixing RPC Ping issues, I would love to hear them.
Thanks!

Hi,
How about OWA, does it works well?
1. If OWA doesn't work, please check wether the Outlook Anywhere has been enabled.
It seems you have configured Outlook Anywhere as below. If not, please change the configuration.
Does the whole error message like this:
Attempting to ping RPC proxy mail.contoso.co.nz.
RPC Proxy can't be pinged.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Please make sure the configuration as below:
Set-OutlookAnywhere
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod : NTLM
IISAuthenticationMethods : {basic, ntlm, negotiate}
Set-OutlookProvider
Name                       Server                      CertPrincipalName            TTL
EXCH
msstd:*.contoso.co.nz     1
EXPR
msstd:*.contoso.co.nz      1
WEB                                                                                                1
More details in the following link:
Exchange 2013 Outlook Anywhere (RPC) Settings
http://infused.co.nz/2013/05/13/exchange-2013-outlook-anywhere-rpc-settings/
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.
2. If the method 1 doesn't help, please collect some related error message in App Log without sensitive information for the further troubleshooting.
3. If OWA works well, just Outlook doesn't work, I suggest try to run 'Test-OutlookConnectivity' command in EMS to verify the connectivity between Exchange server and Outlook client. Please paste the details without sensitive information if there is any
abnormal.
4. Please also run 'Test E-mail AutoConfiguration' on Outlook to verify whether there is anything abnormal.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

Exchange 2013 Delivery Reports not working correctly

Hello,
I'm trying to use the "delivery reports" tool in ECP and it is not acting normally. Here's the situation:
When I try to search a mailbox ([email protected]) for mails that were sent to [email protected] (a distribution group) I only see results that were sent from [email protected] to [email protected] Not all the messages in [email protected]'s mailbox that were sent to [email protected]
So in summary, instead of showing all messages in that mailbox, it shows me all messages on [email protected]'s mailbox that were sent by [email protected] to [email protected]
I have used Exchange Online, which should be almost the same as Exchange 2013 but this was not the behavior before. Can this be a wrong setting somewhere? Can it be related to anti-spam (GFI) software on the serer? Any ideas?

Hi,
How did you use delivery reports tool to track messages ? Is it like below?
*Mailbox to Search: [email protected]
Search for messages sent to: [email protected]
In general, it will show all the messages in [email protected] which were sent to
[email protected], however, if the mailbox has applied any retention policys to delete emails or move the emails to local pst, it may cause your issue.
More information about "Delivery Reports" for your reference:
Track Messages with Delivery Reports
Thanks.
Niko Cheng
TechNet Community Support

Exchange 2013 Delivery Reports - Why does it not show forwarded mail?

We just migrated from 2010 to 2013 and all seems to be working well... We started using EOP at the same time with only a few hiccups. Our Get-MessageTrackingLog command shows all of our email that was delivered or failed, etc... but when I try to run
"Mail Flow -> Delivery reports", it forces me to select a mailbox and I leave the other fields empty - and it only shows emails that come directly to me. The problem is, I have half a dozen email accounts that are set to forward their email
to my exchange account. None of those emails show up with the delivery reports method - but they DO show up via the powershell get-messagetrackinglog command...
With EOP I can see all the emails if I use "Mail Flow -> Message Trace"... why does it work with EOP, but on our local box - it's nerfed to just emails who specify my direct exchange address?

Hi,
I have tested to use Delivery Reports to search my manually forward messages in my Exchange 2013 CU1 environment. And the forward messages can be searched and listed in the Search results.
Please make sure the users who forwarded emails to you are in your organization and they are sending
messages by using the Microsoft Outlook or Outlook Web App email clients. Because Delivery Reports doesn’t track messages send from POP or IMAP email clients. For more information about Delivery Reports, please refer to:
http://technet.microsoft.com/en-us/library/jj150554(v=exchg.150).aspx
Additionally, I also tested auto-forward scenario:
User1 is configured to auto-forward messages to User2 in Exchange side(for details, please click
here), when User3 sends a message to User1, the message is forwarded to User2 automatically. If so, when we use Delivery Report to search this forward message for User2, we
need to use Search for messages received from User3 instead of User1 to get this forwarded message.
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 using ARR reverse proxy OWA options won't open

Hi,
I've been using the exchange team's blog post (http://blogs.technet.com/b/exchange/archive/2013/08/05/part-3-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx)
as a guidelin on configuring my ARR deployment in my lab.
Everything was working perfectly right until i got the last part of the blog on restricting the pattern matches.
The rewrite rules all work fine and everything is working as expected with the excpetion of the fact that i cannot access the options in OWA. ECP itself works great if i access it via the
https://ecp.domain.com/ecp url, but as soon as i use the https//mail.domain.com/ecp it just wont display anything.
Looking at the failed request logs it just shows that it executes a 302 rewrite to ecp.domain.com, which is what i would expect it to base done rewrite rule matching
https://mail.domain.com/ecp to the ecp.domain.com server farm.
If i look at the iis logs it looks like it's getting into some sort of loop (the section below is about a 10% of a single attempt to access the options pages:
2014-06-28 12:25:38 xxx.xxx.xx.xxx GET /ecp/ rfr=owa&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=6983c585-b0ea-4fd0-9bb1-fc747ee8e992 443 - xxx.xxx.xx.xxx Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C)
- 302 0 0 15
2014-06-28 12:25:38 xxx.xxx.xx.xxx GET /ecp rfr=owa/&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=d32a3a4f-d8a6-4712-91d4-56360be33793 443 - xxx.xxx.xx.xxx Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C)
- 302 0 0 0
2014-06-28 12:25:38 xxx.xxx.xx.xxx GET /ecp rfr=owa//&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=14797897-f1ad-454a-b73c-fde041a43d2b 443 - xxx.xxx.xx.xxx Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C)
- 302 0 0 0
Did anyone ever run into something like this? Or have an idea where i may have made a mistake? I've tried everything i could think of.
The rewrite rules i have in place are basically exactly the same as the exchange team's blog but just in case i overlooked somehthing, please se the image below.
thanks in advance for your time

Hello,
I wanted to see if anyone has any suggestions on reverse proxy options that can do pre-authentication like TMG use to do? I am currently trying to deploy out a new Excahnge 2013 setup in coexistence with an existing Exchange 2010 environment
which will then be migrated over. And one of the requirements is to block certain users from accessing webmail externally while still allowing others to access webmail. That is currently achieved by using a TMG server but that is going to be decommissioned
along with Exchange 2010.
I have been searching online but so far I have not found anything that seemed to meet this requirement. I have seen that IIS Web Application Proxy tied in with AD FS would do the job. But there is some issue there with Excahnge 2010 still being active that
won't allow it to work. Some suggestions I have seen online involved changing permissions on the IIS directory or modifying web config files but those options didn't seem like they provided a consistent result.
So I am looking for some sort of option that is either inexpensive or some means of leveraging existing Microsoft technologies to achieve my goal any suggestions would be helpful.
Nicholas,
How about IIS ARR?
http://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 pre-authentication & Reverse Proxy Options

Hello,
I wanted to see if anyone has any suggestions on reverse proxy options that can do pre-authentication like TMG use to do? I am currently trying to deploy out a new Excahnge 2013 setup in coexistence with an existing Exchange 2010 environment
which will then be migrated over. And one of the requirements is to block certain users from accessing webmail externally while still allowing others to access webmail. That is currently achieved by using a TMG server but that is going to be decommissioned
along with Exchange 2010.
I have been searching online but so far I have not found anything that seemed to meet this requirement. I have seen that IIS Web Application Proxy tied in with AD FS would do the job. But there is some issue there with Excahnge 2010 still being active that
won't allow it to work. Some suggestions I have seen online involved changing permissions on the IIS directory or modifying web config files but those options didn't seem like they provided a consistent result.
So I am looking for some sort of option that is either inexpensive or some means of leveraging existing Microsoft technologies to achieve my goal any suggestions would be helpful.
Nicholas,

Hello,
I wanted to see if anyone has any suggestions on reverse proxy options that can do pre-authentication like TMG use to do? I am currently trying to deploy out a new Excahnge 2013 setup in coexistence with an existing Exchange 2010 environment
which will then be migrated over. And one of the requirements is to block certain users from accessing webmail externally while still allowing others to access webmail. That is currently achieved by using a TMG server but that is going to be decommissioned
along with Exchange 2010.
I have been searching online but so far I have not found anything that seemed to meet this requirement. I have seen that IIS Web Application Proxy tied in with AD FS would do the job. But there is some issue there with Excahnge 2010 still being active that
won't allow it to work. Some suggestions I have seen online involved changing permissions on the IIS directory or modifying web config files but those options didn't seem like they provided a consistent result.
So I am looking for some sort of option that is either inexpensive or some means of leveraging existing Microsoft technologies to achieve my goal any suggestions would be helpful.
Nicholas,
How about IIS ARR?
http://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 crash after installing CU9, can i use the database on a backup?

so just installed tried to install CU 9 on Exchange 2013, installed fine and rebooted BSOD problem with ndis.sys, have a backup but dont wanna loose too much mail, can i restore the old backup and copy the databases and logs from the crashed exchange? if it is possible would i need to run some commands afterwards or would it just work?
This topic first appeared in the Spiceworks Community

What’s new: June 2015
Here's a roundup of what's been happening in the world of Office 365 over the last month:
Office for Android phone is here—The new Word, Excel and PowerPoint apps for Android phone have arrived! Review and edit documents on the go, present from your phone, and quickly find the files you were working on in the office or on your tablet. Access files stored in OneDrive, Dropbox, Google Drive and Box. You can download the apps today, and soon they’ll come preloaded on Samsung, Sony, LG and more Android phones.
Wunderlist now part of Microsoft—Microsoft recently acquired Wunderlist, the market-leading to-do list app. Known for its ease of use and innovative design, Wunderlist provides an easy way to capture, organize and collaborate on lists and to-dos—for home, school and work. It’s a fantastic app and it’s available on...

Exchange 2013 co-existence with 2007 can not send from 2013 - receives OK

2013 SP1 -separate servers for MBX and CAS - 4 of each. Exchange 2007 configured as a CCR
I am in co-existence mode but have not yet switched on the legacy.domainname.com. I have a new certificate installed on all servers - 2007 and 2013 with the legacy namespace included
I can receive on the exchange 2013 servers and can send to exchange 2013 users but cannot send to 2007 users or externally. I have enabled protocol logging and I'm seeing:
2014-04-02T00:57:31.476Z,Outbound Primary,08D1120CF8FEEDBA,0,,10.0.9.1:25,*,,attempting to connect
2014-04-02T00:57:52.521Z,Outbound Primary,08D1120CF8FEEDBA,1,,10.0.9.1:25,*,,"Failed to connect. Winsock error code: 10060, Win32 error code: 10060, Error Message: A connection attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has failed to respond 10.0.9.1:25"
The client has a pair of Axway mailgateway appliances (Tumbleweed). We can Telnet between the exchange 2013 servers and the Axways. There is a firewall between these mail gateways and the exchange servers and the following ports were opened - 25,443,465,995,110
I used the existing send connectors from 2007 and just added the mailbox servers to them. I created 2 new receive connectors to match 2 specialist 2007 connectors.
But I still can't send mail. Any suggestions where next to check?

Hi Tony
Based on the protocol logs error looks like there is connectivity problem between Ex2007 and Ex2013
First you can try dropping an email through Telnet from Exchange 2013 to Exchange 2007 to see the message failure happens at which transit.
You can add the IP address of Exchange 2013 in Exchange 2007 default receive connector and vice versa.
Restart the transport service and try sending an email from exchange 2013 to Exchange 2007 and see the results
Also you can try creating a dedicated receive connector for Exchange 2007 in Exchange 2013 and vice versa if the above step does not work
Also try disabling the firewall and see if it helps.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you

Exchange 2013 SP1 OWA the page can't be displayed issue

OWA the page can't be displayed
Hi, i've Exchange topology (upgraded from 2007 one server)
2 CAS servers NLB with VIP 172.16.0.98
2 MBX Servers DAG with DAG
using Cisco ASA NAT public IP for example 9.9.9.9 ....> 172.16.0.98
i've created split DNS zone for public domain in internal DNS to unify URLs internal and external Mail.Domain.Com
i've created internal zone called Mail.Domain.Com and Autodiscover.domain.com point to VIP 172.16.0.98
Everything is OK but sometimes users report when they access OWA from inside or outside when user submit user/ pass faced error the page can't be displayed?
i tried this this user from different browsers and different computer the same issue
if i tried another user from the same computer it works fine
the strangest point after 30-60 minutes it backs to live and everything going fine
i checked event viewer there is nothing related to this issue.
in sometimes if i tried to access manual to CAS1.Domain.Local / IP address/ owa it works fine.
URL changes to https://Mail.Domain.Com/owa/auth.owa
i red some about putting my public domain as remote domain but it's not clear !
any ideas please?

If it works properly when connecting directly to the server, then something is misconfigured in the load balancer or something else in that data path.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Thanks Ed,
NLB converged is OK. and all users are running well, except while this issue accrued.
i checked event viewer under exchange managed availability
EMSMDB.Connect() step of ComplianceOutlookLogonToArchiveMapiHttpCtpProbe/MBX2DB2 has failed against ExCAS1.Domain.LOCAL proxying to Unknown for [email protected].
Latency: 00:00:00.0380000
ActivityContext:
Outline: [37]6/19/2014 11:27:05 AM [FAILED!] EMSMDB.Connect();
Likely root cause: UnknownIssue
Details:
Error: Error returned in ConnectCallResult. Error code = LogonFailed (0x80040111)
Log: Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 6/19/2014 11:27:05 AM
- TaskFinished = 6/19/2014 11:27:05 AM
- Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in ConnectCallResult. Error code = LogonFailed (0x80040111) ---> System.Exception: Microsoft.Exchange.RpcClientAccess.Server.LoginFailureException:
Unable to access AD (StoreError=LoginFailure) ---> Microsoft.Exchange.Data.Storage.MailboxInfoStaleException: Can't connect to the mailbox of user Mailbox database guid: d020aa7f-371b-4da5-808a-3a5d18dc8d81 because the ExchangePrincipal object
contains outdated information. The mailbox may have been moved recently. ---> Microsoft.Exchange.Data.Storage.DatabaseNotFoundException: The database with ID d020aa7f-371b-4da5-808a-3a5d18dc8d81 couldn't be found.
at Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManager.GetServerNameForDatabase(Guid databaseId, GetServerForDatabaseFlags gsfdFlags, IPerformanceDataLogger perfLogger, IADDatabase& database)
at Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManager.GetServerForDatabase(Guid databaseId, GetServerForDatabaseFlags gsfdFlags, IPerformanceDataLogger perfLogger)
at Microsoft.Exchange.Data.Storage.DatabaseLocationProvider.GetLocationInfo(Guid mdbGuid, Boolean bypassCache, Boolean ignoreSiteBoundary)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.DatabaseLocationProvider.GetLocationInfo(Guid mdbGuid, Boolean bypassCache, Boolean ignoreSiteBoundary)
at Microsoft.Exchange.RpcClientAccess.Server.UserManager.User.UpdatePrincipalCacheIfNeeded()
at Microsoft.Exchange.RpcClientAccess.Server.UserManager.User.UpdatePrincipalCacheWrapped(Boolean ignoreCrossForestMailboxErrors)
--- End of inner exception stack trace ---
at Microsoft.Exchange.RpcClientAccess.Server.UserManager.User.UpdatePrincipalCacheWrapped(Boolean ignoreCrossForestMailboxErrors)
at Microsoft.Exchange.RpcClientAccess.Server.UserManager.Get(SecurityIdentifier authenticatedUserSid, String actAsLegacyDN, String userDomain)
at Microsoft.Exchange.RpcClientAccess.Server.RpcDispatch.<>c__DisplayClassc.<EcDoConnectEx>b__8()
at Microsoft.Exchange.RpcClientAccess.Server.RpcDispatch.Execute(Func`1 getExecuteParameters, Func`1 executeDelegate, Action`1 exceptionSerializationDelegate)
--- End of inner exception stack trace ---
- ErrorDetails =
- RespondingRpcClientAccessServerVersion = 15.0.847.30
- Latency = 00:00:00.0377761
EMSMDB.Connect() failed.
Task produced output:
- TaskStarted = 6/19/2014 11:27:05 AM
- TaskFinished = 6/19/2014 11:27:05 AM
- Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException: Error returned in ConnectCallResult. Error code = LogonFailed (0x80040111) ---> System.Exception: Microsoft.Exchange.RpcClientAccess.Server.LoginFailureException: Unable
to access AD (StoreError=LoginFailure) ---> Microsoft.Exchange.Data.Storage.MailboxInfoStaleException: Can't connect to the mailbox of user Mailbox database guid: d020aa7f-371b-4da5-808a-3a5d18dc8d81 because the ExchangePrincipal object contains outdated
information. The mailbox may have been moved recently. ---> Microsoft.Exchange.Data.Storage.DatabaseNotFoundException: The database with ID d020aa7f-371b-4da5-808a-3a5d18dc8d81 couldn't be found.
at Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManager.GetServerNameForDatabase(Guid databaseId, GetServerForDatabaseFlags gsfdFlags, IPerformanceDataLogger perfLogger, IADDatabase& database)
at Microsoft.Exchange.Data.Storage.ActiveManager.ActiveManager.GetServerForDatabase(Guid databaseId, GetServerForDatabaseFlags gsfdFlags, IPerformanceDataLogger perfLogger)
at Microsoft.Exchange.Data.Storage.DatabaseLocationProvider.GetLocationInfo(Guid mdbGuid, Boolean bypassCache, Boolean ignoreSiteBoundary)
--- End of inner exception stac
if user access to ExMBX2.Domain.Local it works fine.?
any ideas please ?

Exchange 2013 delivery reports for mail enabled public folder

How can I get delivery reports for mail enabled public folders? Would I search the related public folder mailbox?

Hi,
When you track messages using Delivery Reports, you can only choose user mailbox when you select mailbox to search. Under the option "Mailbox to search", there is no mail-enabled public folder listed there for you to select from
the address book.
But you can search messages sent to or received from mail-enabled public folder.
Track messages with delivery reports
http://technet.microsoft.com/en-GB/library/jj150554(v=exchg.150).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Exchange 2013 OWA VirtualDirectory Gone and can't be re-add

Hello everyone,
owavirtualdirectory but failed with the error "The Path 'D:\Exchange2013\FrontEnd\HttpProxy\owa' doesn't exist on 'xxxxxx'", actually the folder is there...We tried copy the "owa" folder from another server also but still failed. We check
the folder permission all are default settings.
Could you please let's know how can I make this work? I don't want to reinstall the server right now...
Thanks a lot guys!!!
Best regards
Jack Zhou

Hi,
Have you tried Prakash’s suggestion to remove the OWA virtual directory and re-create it back? Does it work? How about your Ecp virtual directory?
It seems that your Exchange server is installed in a customized Disk. Please check the OWA virtual directory in IIS Manager:
1. Expand Sites > Default Web Site.
2. Right-click owa > Manage Application > Advanced Settings. Then check the Physical Path value and make sure it is set to:
D:\Exchange2013\FrontEnd\HttpProxy\owa
3. Open Web.config file for OWA in the following paths:
D:\Exchange2013\FrontEnd\HttpProxy\owa
D:\Exchange2013\ClientAccess\Owa.
If there is any %ExchangeInstallDir% in the web.config content, replace all of them with
D:\Exchange2013\.
4. Restart IIS service by running IISReset /noforce from a command prompt window.
If the issue persists, please collect any event view or IIS logs for further analysis.
Regards,

Reset Authentication method to Exchange 2013 EAC and now I can't get in.

In trying to work through a list of issues related to Exchange upgrade I inadvertently have locked myself out of the EAC by changing the authentication method. Is there any way to change it back?

Hi,
According to my experience, the ECP login failure issue has many reasons. Thus, to narrow down the cause, we can try to confirm the following information and try the following troubleshooting:
1. Check the detail information about OWA and ECP virtual directory:
Get-owavirtualdirectory |fl
Get-ecpvirtualdirectory |fl
2. Clear or restart the MSExchangeOWAAppPool
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Exchange 2013 - Scripting Reports

Hey guys, I'm looking to utilize JBeeden's Email Stats script to try to automate some reporting...https://gallery.technet.microsoft.com/office/Exchange-200720102013-0ea7662b
I'd like to also be able to limit each report to specific distribution or security groups (for departmental reports)
Could you guys give suggestion on which lines to modify in JBeeden's script to limit the report to specific groups?
Also I'd like to schedule these to run on a monthly basis, and be emailed out to managers or myself. Is this possible to do in Exchange? or will I have to have use bat script in a scheduled task to run the powershell script and email the CSV?

Two days ago the same problem started in our production enviroment
its not happening all the time though
i've checked the logs on the mailbox server and found that the get-mailbox command is sometimes triggered before the Enable-Mailbox command is completed .
This is so weird , all commands ins the scripts should be triggered on complete !
anyway , im still investigating the problem
I wonder if you have found any solution for this issue ?
Regards,
Best Regards Bisher Shbib

Configure external users phones and tablets in exchange 2013

I have a single Exchange 2013 server that i cannot seem to make external users work by configuring the phones.
using exchange connectivity analyzer i have RPC Ping problems i cannot seem to find a proper answer.
I only have port 443 incoming from the internet to the Exchange 2013.
The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.
Attempting the FolderSync command on the Exchange ActiveSync session.
Exchange ActiveSync returned an HTTP 500 response (Internal Server Error).
Diagnostics:
AAA==_S111_Error:ADOperationException1:Active Directory operation failed on VM-DC-002.ourdomain.com. This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031521E1, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 _Mbx:VM-EXCH13-001.ourdomain.com_Dc:VM-DC-002.IFARHU.GOB.PA_Throttle0_DBL7_DBS1_CmdHC-
Also,
Attempting to ping RPC proxy correo.ourdomain.com.
RPC Proxy can't be pinged.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: 1711b40e-d416-4f8f-ada1-876c5e8719e0
X-CasErrorCode: EndpointNotFound
X-FEServer: VM-EXCH13-001
Content-Length: 0
Cache-Control: private
Date: Tue, 24 Dec 2013 06:57:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 222 ms.
Suggestions?

EAS problems were traced to permissions problems because in our AD we do not use the normal OU called "users" and we use a different OU name.
However the RPC Ping problem still remains. no matter what permission we set:
Attempting to ping RPC proxy correo.ifarhu.gob.pa.
RPC Proxy can't be pinged.
Additional Details
A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.
Headers received:
request-id: 1e075c85-5cfb-4ff2-9fb6-59b3eaf102b8
X-CasErrorCode: EndpointNotFound
X-FEServer: VM-EXCH13-001
Content-Length: 0
Cache-Control: private
Date: Tue, 31 Dec 2013 12:28:29 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 190 ms.
I do not know if this is related, but just to let you know, we use the same DNS name for both internal and external access (correo.ifarhu.gob.pa). At internal level the internal DNS resolves
to internal address. at external level public DNSs resolves to external internet addresses.
Also, we are using form based OWA. Can someone tell me how the settings look like at exchange powershell level and at IIS level?
thanks,

Outlook 2013 can't connect to Exchange 2013 SP1

Hello,
I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain) with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
Thank you in advance,
Michael

Hi,
When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
"Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Error reported after Exchange 2013 Setup (initialize-ExchangeUniversalGroups)

My Exchange 2013 setup reported the error below. Just wondering if someone has experienced this and how easy it was to fix.
Error:
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:81ee6b49-29e5-41ff-93d4-30c547de15b1,CN=Deleted Objects,DC=ad,DC=mydomain,DC=co
on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=mydomain,DC=co points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateRoleGroup(ADOrganizationalUnit usgContainer, RoleGroupDefinition roleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Roger

Thanks for replying.
My domain is actually routable (I just renamed it thinking that perhaps its more secure to withhold the info).
I had previously installed Es2013 and had to delete the VM. So this is a re-install on the Active Directory. I'm wondering if there isn't something in the "deleted folder" that is causing hassles.
Roger

Exchange 2013 - RCA reports RPC Proxy can't be pinged (404)

Similar Messages

Maybe you are looking for