Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 41 Source: MSExchange OWA
|Source: MSExchange OWA|
The Client Access server "https://dom.domain.com/owa" attempted to proxy Outlook Web Access traffic for mailbox "/o=ExchMigrationLab/ou=Exchange Administrative Group (SERVRNAME)/cn=Recipients/cn=gquagmire". This failed because no Client Access server with an Outlook Web Access virtual directory configured for Kerberos authentication could be found in the Active Directory site of the mailbox. The simplest way to configure an Outlook Web Access virtual directory for Kerberos authentication is to set it to use Integrated Windows authentication by using the Set-OwaVirtualDirectory cmdlet in the Exchange Management Shell or by using the Exchange Management Console. If you already have a Client Access server deployed in the target Active Directory site with an Outlook Web Access virtual directory configured for Kerberos authentication the proxying Client Access server may not be finding that target Client Access server because it does not have an internalUrl parameter configured. You can configure the internalUrl parameter for the Outlook Web Access virtual directory on the Client Access server in the target Active Directory site by using the Set-OwaVirtualDirectory cmdlet.
|English: Request a translation of the event description in plain English.|
If you have removed the externalURL from the OWAvirtualdirectory (required for proxying) on the non internet facing sites CAS servers and this error is generated then you will need to ensure that you configure authentication for the the OWAVirtualDirectory to be Windows Integrated/Basic and not FBA.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated