Exchange Archiving Tasks will not start automatically when the task controller starts
Article ID: 100034152
Updated On:
Cause
The primary issue is that Enterprise Vault is unable to get a list of SCP URLs from Active Directory. This can occur when the Enterprise Vault server that the archiving task(s) are running is located in an Active Directory site and Exchange is located in a different Active Directory site.
(EVExchangeWebServicesProxy)… {SCPUrlLister.GetSCPUrls} Computer site name = [ EV Server Site]
(EVExchangeWebServicesProxy)… {SCPUrlLister.ScanCurrentComputerSCPUrls} Scanning for SCP urls for the current computer [ Site=EV Server Site]
After scanning, it will show the results:
(EVExchangeWebServicesProxy)… {SCPUrlLister.GetSCPUrls} The SCP url list is empty, trying LDAP fall-back path.
(EVExchangeWebServicesProxy) … {ExchangeAutodiscover.DoAutodiscover} Found [0] SCP urls for domain [ EV Serve Site]
The dtrace shows the Active Directory site the Enterprise Vault server is associated to. A review of Exchange via the management shell or Active Directory can show the site(s) that the Exchange servers respond to.
Using ADSI Edit, go to properties of Configuration/Services/Microsoft Exchange/ Organization Name/Administrator Groups/Exchange Administrative Group (FYDIBOHF23SPDLT) /Servers/ exchange server/Protocols/Autodiscover/ exchange server
Review serviceBindingInformation. This should be the Autodiscover URL.
Review Keywords. Press Edit to display the Site(s) that the selected exchange server responds to.
If the Site(s) listed do not match the Site that the Enterprise Vault server is reporting, Enterprise Vault will not retrieve the Service Connection Point Url, (AutodiscoverUrl) from Active Directory.
(EVExchangeWebServicesProxy)… {SCPUrlLister.GetSCPUrls} Computer site name = [ EV Server Site]
(EVExchangeWebServicesProxy)… {SCPUrlLister.ScanCurrentComputerSCPUrls} Scanning for SCP urls for the current computer [ Site=EV Server Site]
After scanning, it will show the results:
(EVExchangeWebServicesProxy)… {SCPUrlLister.GetSCPUrls} The SCP url list is empty, trying LDAP fall-back path.
(EVExchangeWebServicesProxy) … {ExchangeAutodiscover.DoAutodiscover} Found [0] SCP urls for domain [ EV Serve Site]
The dtrace shows the Active Directory site the Enterprise Vault server is associated to. A review of Exchange via the management shell or Active Directory can show the site(s) that the Exchange servers respond to.
Using ADSI Edit, go to properties of Configuration/Services/Microsoft Exchange/ Organization Name/Administrator Groups/Exchange Administrative Group (FYDIBOHF23SPDLT) /Servers/ exchange server/Protocols/Autodiscover/ exchange server
Review serviceBindingInformation. This should be the Autodiscover URL.
Review Keywords. Press Edit to display the Site(s) that the selected exchange server responds to.
If the Site(s) listed do not match the Site that the Enterprise Vault server is reporting, Enterprise Vault will not retrieve the Service Connection Point Url, (AutodiscoverUrl) from Active Directory.
Resolution
Add the Enterprise Vault servers site to the lists of sites that the exchange server responds to either using exchange management shell.
Note: Adding the AD site that the Enterprise Vault server belongs to will allow any Outlook clients in the same Active Directory site the ability to connect to this exchange server.
f. Repeat steps b-e for the remaining servers.
Note: Adding the AD site that the Enterprise Vault server belongs to will allow any Outlook clients in the same Active Directory site the ability to connect to this exchange server.
a. On an Exchange Server, open the Exchange Management Shell.
b. Run the following command to review settings:
[PS] C:\Windows\system32>Get-ClientAccessServer | FT Name, AutoDiscoverSiteScope -Autosize
Review Results:
c. Set up site scope for one Exchange server:
[PS] C:\Windows\system32>$sitescope = (Get-ClientAccessServer EX2013-CAS).autodiscoversitescope
Review result:
d. Add site EV Server Site to $sitescope
[PS] C:\Windows\system32>$sitescope +="EV Server Site"
Review result:
e. Add $sitescope to the Exchange server
[PS] C:\Windows\system32>Set-ClientAccessServer EX2013-CAS -AutoDiscoverSiteScope $Sitescope
Review result:
f. Repeat steps b-e for the remaining servers.
Issue/Introduction
When this delay occurs, it is due to Enterprise Vault inability to access the list of SCPs leaving the SCP URL list empty as seen in the line of a dtrace below:
(EVExchangeWebServicesProxy)… {SCPUrlLister.GetSCPUrls} No SCP pointers found for domain [DOMAIN.COM] in the config path [CN=Configuration,DC=domain,DC=com]
Once it has been determine the list is empty, Enterprise Vault will attempt to access the Autodiscover endpoint using two URLs per Microsoft’s guidelines in using AutoDiscovery.
Enterprise Vault will then query mydomain.com/autodiscover/autodiscover.xml. If it cannot connect, it times out after 100,000 milliseconds. This timeout value is hardcoded within HttpWebRequestset within the .NET Framework.
Note: The number of tasks that are being used for Archiving/Journaling contributes to the length of time the delay occurs. For example, 10 archiving/journaling task on one Enterprise Vault server equates to 100,000 milliseconds * 10.
Once the timeout occurs, it will then attempt to connect to autodiscover.mydomain.com/autodiscover/autodiscover.xml. If not successful again a timeout will occur of 100,000 milliseconds.
After the GetExchangeConnectionPointDetailsRequiredByEV has completed, the dtrace will show how long it took to retrieve the details.
(EVExchangeWebServicesProxy)...{ExchangeConnectionPoint.GetExchangeConnectionPointDetailsRequiredByEV} it took [100173] milliseconds to get connection point details from exchange
Note: When Outlook fails to find the Service Connection Point Url via Active Directory, it then attempts to access the Autodiscover endpoint using the below Urls. The below Urls need to be resolvable in DNS to allow an Outlook client use the Urls.
(EVExchangeWebServicesProxy)… {SCPUrlLister.GetSCPUrls} No SCP pointers found for domain [DOMAIN.COM] in the config path [CN=Configuration,DC=domain,DC=com]
Once it has been determine the list is empty, Enterprise Vault will attempt to access the Autodiscover endpoint using two URLs per Microsoft’s guidelines in using AutoDiscovery.
- mydomain.com/autodiscover/autodiscover.xml
- autodiscover.mydomain.com/autodiscover/autodiscover.xml
Enterprise Vault will then query mydomain.com/autodiscover/autodiscover.xml. If it cannot connect, it times out after 100,000 milliseconds. This timeout value is hardcoded within HttpWebRequestset within the .NET Framework.
Note: The number of tasks that are being used for Archiving/Journaling contributes to the length of time the delay occurs. For example, 10 archiving/journaling task on one Enterprise Vault server equates to 100,000 milliseconds * 10.
Once the timeout occurs, it will then attempt to connect to autodiscover.mydomain.com/autodiscover/autodiscover.xml. If not successful again a timeout will occur of 100,000 milliseconds.
After the GetExchangeConnectionPointDetailsRequiredByEV has completed, the dtrace will show how long it took to retrieve the details.
(EVExchangeWebServicesProxy)...{ExchangeConnectionPoint.GetExchangeConnectionPointDetailsRequiredByEV} it took [100173] milliseconds to get connection point details from exchange
Note: When Outlook fails to find the Service Connection Point Url via Active Directory, it then attempts to access the Autodiscover endpoint using the below Urls. The below Urls need to be resolvable in DNS to allow an Outlook client use the Urls.
- mydomain.com/autodiscover/autodiscover.xml
- autodiscover.mydomain.com/autodiscover/autodiscover.xml
Was this article helpful?
Yes
No
Powered by
