Hi, I'm getting this error on my exchange 2010 sp1 rollup 2. Event id 16 source MSExchange Web Services. Client Access server CASHTMB01 failed to proxy Exchange Web Services to Active Directory site CN=SiteX,CN=Sites,CN=Configuration,DC=domain,DC=com because there are no applicable Client Access servers in the destination site. Please check the configuration of the servers in site [No Server]. This server was the second CAS Server added to our domain. The first server has since been retired. (exch2010 uninstalled)

Are there Exchange servers in SiteX?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

We only have one site, how can i determine if this server is in the site? it seems like it should be by default.

This error occures if we use CAS-CAS proxy between site CAS servers. what URL is configured in internal and external URL in EWS directory in CAS. http://technet.microsoft.com/en-us/library/bb310763.aspx Anil

You define the sites in Active Directory sites and services based on network subnets.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

Thanks Anil. The internal url is https://CASHTMB01.domain.com/EWS/exchange.asmx The external url is https://mail.domain.com/EWS/exchange.asmx

Do you have a universal communications certificate (UCC) with subject alternative names (SANs) with both of the names?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Hi, Are you in a mixed Exchange environment? For example: The Exchange Server 2010 CAS does not directly connect to an Exchange 2007 MBX server. Also, the Exchange Server 2010 CAS does not proxy a request from an EWS client to an Exchange 2007 CAS in the same Active Directory site. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

We are in the process of transitioning from 2003. What happened to me was that i build the 2010 exchange servers in one datacenter. As i was about to start migrating users, the boss says i need to build in the other datacenter which uses a different name prefix. Cant rename exchange. so i built the new exchange servers in the correct datacenter. after i removed the roles from the servers in the wrong datacenter, this error is showing up on server in new datacenter. So Yes mixed environment for now. As of now, we are using an internal cert from our CA server. it is using SANs. thanks for all of your help. Jason