Thanks so much. I knew I would find the answer I needed here! I would ignore it, however we have a monitoring system (managed by another group entirely) that keeps sending me alerts for this error, so until I do something with it, or tell them to stop monitoring for that particular alert, its kinda hard for me to ignore it!
Jonathan On Tue, Jun 3, 2014 at 5:29 PM, Michael B. Smith <[email protected]> wrote: > Only sites that are Internet-facing should have ExternalUrls. That is > true not just for EWS, but for all virtual directories. > > > > Since both have ExternalUrls, they are trying to proxy to each other. > > > > If you don’t care about the error – ignore it. J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jonathan > *Sent:* Tuesday, June 3, 2014 5:24 PM > > *To:* [email protected] > *Subject:* Re: [Exchange] Event ID 11 with Source MSExchange Web Services > > > > Ok, thanks. > > > > So apparently it has been like this for years. What is the benefit to > resolving this at this point, aside from not getting the events every so > often, if we're really moving away from Exchange to O365? (or, conversely, > the harm if it isn't resolved). > > > > And does one site even need to proxy for the other, since they are > essentially independent Exchange Server just passing HT traffic back and > forth? If not, is there a way to have them not try to proxy for each other? > Both Exchange servers are giving this error for the other site.... > > > > Jonathan > > > > On Tue, Jun 3, 2014 at 5:11 PM, Michael B. Smith <[email protected]> > wrote: > > In order for Site1 to proxy EWS to Site2, you must remove the ExternalUrls > from the EWS sites in Site2. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jonathan > *Sent:* Tuesday, June 3, 2014 4:51 PM > > > *To:* [email protected] > *Subject:* Re: [Exchange] Event ID 11 with Source MSExchange Web Services > > > > Face --palm.... > > > > And that's what I get for responding when I'm in the middle of a > conference call. *sigh* > > > > I believe this is what you're asking for: > > > > [PS] C:\>Get-WebServicesVirtualDirectory | Select name, *url* | fl > > > > > > Name : EWS (Default Web Site) > > InternalNLBBypassUrl : https://mail1.domain.corp/ews/exchange.asmx > > InternalUrl : https://mail-Site1.domain.com/EWS/Exchange.asmx > > ExternalUrl : https://mail-Site1.domain.com/EWS/Exchange.asmx > > > > Name : EWS (Default Web Site) > > InternalNLBBypassUrl : https://mail2.domain.corp/ews/exchange.asmx > > InternalUrl : https://mail-Site2.domain.com/EWS/Exchange.asmx > > ExternalUrl : https://mail-Site2.domain.com/EWS/Exchange.asmx > > > > Name : EWS (Default Web Site) > > InternalNLBBypassUrl : https://mail1casht1.domain.corp/ews/exchange.asmx > > InternalUrl : https://mail1.domain.corp/ews/exchange.asmx > > ExternalUrl : https://mail-Site1.domain.com/ews/exchange.asmx > > > > Name : EWS (Default Web Site) > > InternalNLBBypassUrl : https://mail1casht2.domain.corp/ews/exchange.asmx > > InternalUrl : https://mail1.domain.corp/ews/exchange.asmx > > ExternalUrl : https://mail-Site1.domain.com/ews/exchange.asmx > > > > Name : EWS (Default Web Site) > > InternalNLBBypassUrl : https://Site2casht1.domain.corp/ews/exchange.asmx > > InternalUrl : https://mail2.domain.corp/ews/exchange.asmx > > ExternalUrl : https://mail-Site2.domain.com/ews/exchange.asmx > > > > Name : EWS (Default Web Site) > > InternalNLBBypassUrl : https://Site2casht2.domain.corp/ews/exchange.asmx > > InternalUrl : https://mail2.domain.corp/ews/exchange.asmx > > ExternalUrl : https://mail-Site2.domain.com/ews/exchange.asmx > > > > > > > > [PS] C:\> > > > > The additional 4 servers are Exchange 2010 CAS/HT servers - the company > started down a 2007 to 2010 migration, but then figured out that they > couldn't migrate a single mailbox due to a 3rd party voicemail integration > compatibility issue until until the voicemail could be upgraded to one that > would handle the transition.....so the project stopped dead in its tracks. > So there were/are 8 2010 servers in all just sitting there - 2 CAS/HT > servers for each site, and 2 mailbox servers for each site). > > > > Fast forward a couple of years (yes, years), and we're looking at moving > from Exchange 2007 to O365 and abandoning Exchange altogether, but we're > still months off, so I'm stuck maintaining the environment until then. The > eight 2010 servers were just left in place (in the hopes that the project > would move forward....) > > > > Thanks, > > > > Jonathan > > > > On Tue, Jun 3, 2014 at 4:15 PM, Michael B. Smith <[email protected]> > wrote: > > Right. But you didn’t answer my question. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jonathan > *Sent:* Tuesday, June 3, 2014 4:06 PM > *To:* [email protected] > *Subject:* Re: [Exchange] Event ID 11 with Source MSExchange Web Services > > > > Thanks for the reply. > > > > Meant to include - both servers have OWA enabled for their respective > users. > > > > EWS is published (https://mail.domain.com/ews) > > > > Both sites present challenge dialogue, and once authenticated, both > present this: > > > > Directory Listing Denied > This Virtual Directory does not allow connections to be listed. > > > > Thanks, > > > > Jonathan > > > > On Tue, Jun 3, 2014 at 2:00 PM, Michael B. Smith <[email protected]> > wrote: > > Do you have an ExternalUrl defined for the EWS virtual directory in Site2? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Adam Farage > *Sent:* Tuesday, June 3, 2014 1:17 AM > *To:* [email protected] > *Subject:* RE: [Exchange] Event ID 11 with Source MSExchange Web Services > > > > Firewall blocking the TCP 443 response? > > Adam F > ------------------------------ > > *From: *Jonathan <[email protected]> > *Sent: *6/3/2014 12:44 AM > *To: *[email protected] <[email protected]> > *Subject: *[Exchange] Event ID 11 with Source MSExchange Web Services > > Hi - new to this list, though I was on the Sunbelt lyris list years ago. > Have not been active in a couple of years. I'm hopeful someone here can > help me out. My Google-fu is failing me.... > > > > I have [inherited] two Exchange 2007 Servers running SP3 with the latest > rollup (I got them updated from SP2 back in October) these servers are in > two separate sites. Each server holds all the roles, and we're just passing > HT traffic between. Each sends their own email out their local connection, > but all inbound traffic comes in through Site1. The mailboxes are split > about 50/50 between the two servers. > > > > Anyway, we have been receiving the following event on both servers for > some time. We are NOT getting event ID 17 on either server (as just about > everything I've googled turns up). on each server, the event says "none of > the CAS servers in [the remote] site are responding". > > > > If you have any suggestions on how I can resolve this, I'd be very > grateful. > > > > Event Type: Error > > Event Source: MSExchange Web Services > > Event Category: Core > > Event ID: 11 > > Date: 6/2/2014 > > Time: 9:58:19 PM > > User: N/A > > Computer: EX01Site1 > > Description: > > CAS server EX01Site1 failed to proxy EWS to AD > site CN=Site2,CN=Sites,CN=Configuration,DC=DOMAIN,DC=CORP because none of > the CAS servers in this site are responding. Please check the > configuration and status of the servers in site > CN=Site2,CN=Sites,CN=Configuration,DC=DOMAIN,DC=CORP > > > > For more information, see Help and Support Center at > http://go.microsoft.com/fwlink/events.asp. > > > > > > -- > Jonathan, A+, MCSA, MCSE > > > > > > -- > Jonathan, A+, MCSA, MCSE > > > > > > -- > Jonathan, A+, MCSA, MCSE > > > > > > -- > Jonathan, A+, MCSA, MCSE > -- Jonathan, A+, MCSA, MCSE
