This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Remove From My Forums

ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'

Question
0

Sign in to vote
first of all, I am not sure if I am posting in the right forum, my apologies if I am not. Please direct me to the correct one.

We are currently testing Exchange Online Archive with one mailbox. This seems to go well for the user so far, but on the server side we are getting the following errors:

SCOM reports:

Probe: {Compliance/ELCComponent_LastSuccessTooLongAgo} Mailbox guid: {035f402b-8ad1-4e8b-b4e2-b73090f3cc9c} In Org: {} Is archive: {IsArchiveMailbox = False} With stack trace: {The difference: 7.00431698556481 days between today: 11/19/2015 6:31:33 AM and the date of last successful ELC run: 11/12/2015 6:25:20 AM for mailbox: 035f402b-8ad1-4e8b-b4e2-b73090f3cc9c is above the threshold: 7} Get last ELC exception from Export-MailboxDiagnosticLogs -Component MRM then statistics with -ExtendedProperties and look at all ELC properties, specifically the value of ELCLastSuccessTimestamp. If mailbox is Archive use -Archive.

And running the suggested commandlets returns the following error:
11/19/2015 6:31:33 AM Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException:
ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is
unknown.
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.RemoteArchiveProcessorBase..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isCrossPremise, Boolean
isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.CloudArchiveProcessor..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ArchiveProcessorFactory.Create(ArchiveLocation
archiveLocation, MailboxSession mailboxSession, ADUser adUser, StatisticsLogEntry statisticsLogEntry,
Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.MailboxData.get_ArchiveProcessor()
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.InvokeInternal(MailboxDataForTags
mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.Invoke(MailboxDataForTags
mailboxDataForTags)
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.InvokeInternal(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.Invoke(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeCore(MailboxSession
mailboxSession, StatisticsLogEntry logEntry, ElcParameters parameters)
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate
filterDelegate, CatchDelegate catchDelegate)
11/18/2015 6:32:02 AM Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException:
ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is
unknown.
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.RemoteArchiveProcessorBase..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isCrossPremise, Boolean
isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.CloudArchiveProcessor..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ArchiveProcessorFactory.Create(ArchiveLocation
archiveLocation, MailboxSession mailboxSession, ADUser adUser, StatisticsLogEntry statisticsLogEntry,
Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.MailboxData.get_ArchiveProcessor()
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.InvokeInternal(MailboxDataForTags
mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.Invoke(MailboxDataForTags
mailboxDataForTags)
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.InvokeInternal(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.Invoke(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeCore(MailboxSession
mailboxSession, StatisticsLogEntry logEntry, ElcParameters parameters)
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate
filterDelegate, CatchDelegate catchDelegate)
11/17/2015 6:32:16 AM Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException:
ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is
unknown.
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.RemoteArchiveProcessorBase..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isCrossPremise, Boolean
isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.CloudArchiveProcessor..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ArchiveProcessorFactory.Create(ArchiveLocation
archiveLocation, MailboxSession mailboxSession, ADUser adUser, StatisticsLogEntry statisticsLogEntry,
Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.MailboxData.get_ArchiveProcessor()
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.InvokeInternal(MailboxDataForTags
mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.Invoke(MailboxDataForTags
mailboxDataForTags)
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.InvokeInternal(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.Invoke(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ELCAssistant.InvokeCore(MailboxSession
mailboxSession, StatisticsLogEntry logEntry, ElcParameters parameters)
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate
filterDelegate, CatchDelegate catchDelegate)
11/16/2015 6:32:23 AM Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException:
ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is
unknown.
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.RemoteArchiveProcessorBase..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isCrossPremise, Boolean
isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.CloudArchiveProcessor..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ArchiveProcessorFactory.Create(ArchiveLocation
archiveLocation, MailboxSession mailboxSession, ADUser adUser, StatisticsLogEntry statisticsLogEntry,
Boolean isTestMode)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.MailboxData.get_ArchiveProcessor()
   at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.InvokeInternal(MailboxDataForTags
mailboxDataForTags)
   at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.Invoke(MailboxDataForTags
mailboxDataForTags)

The "todo" mentioned by the SCOM logging "Get last ELC exception from Export-MailboxDiagnosticLogs -Component MRM then statistics with -ExtendedProperties and look at all ELC properties, specifically the value of ELCLastSuccessTimestamp." makes no sense to me at all. the first part I get and I am able to run, but the second part about "-extendedProperties" doesn't ring a bell.

I am pretty clueless were to go from here....
- Edited by Erik Nettekoven Thursday, November 19, 2015 8:37 AM
Thursday, November 19, 2015 8:37 AM

All replies

0

Sign in to vote

My read is that SCOM can't figure out how to get to the online archive mailbox with Exchange Web Services. My guess is that it's a red herring, but I can't say for sure.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Celebrating 20 years of providing Exchange peer support!

Thursday, November 19, 2015 4:23 PM
0

Sign in to vote

Hi Erik,

According to the error information, it seems that SCOM cannot find Exchange Web Services (EWS) Url:

"ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is
unknown."

You can try to check if the EWS URL could be accessed in SCOM server:

Enter the EWS URL into a web browser. You should get a screen asking for a name and password. If you successfully enter a name and password, then the browser should display some XML.

Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Niko Cheng
TechNet Community Support

Monday, November 23, 2015 9:08 AM
0

Sign in to vote

Thank you for your suggestions but...

I probably was a little bit unclear, it is not SCOM that is reporting "Archive EWS url is unknown." it is Exchange.

SCOM only advises me to run "Export-MailboxDiagnosticLogs -Component MRM" on the Exchange server. So when I run this command on one of the Exchange servers, it is Exchange that reports back the error:

"Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException:
ELC EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is
unknown."

This error only occurs with the Mailbox that has an Online Exchange Archive configured.

Monday, November 23, 2015 9:15 AM
1

Sign in to vote
Hi Erik,

Sorry for misunderstanding!

As I read your original post again, my understanding is as below :

the SCOM report tell us the last successful ELC(Email Lifecycle Assistant) in the mailbox (it is not archive mailbox, "IsArchiveMailbox = False") has exceed 7 days, it has exceed the threshold which exists in SCOM. So, SCOM generate a report.

Now, run the following command to check if we can get the value of "ELCLastSuccessTimestamp":

Export-MailboxDiagnosticLogs -Identity username -ExtendedProperties

In addition, the following article may give you some hints to troubleshoot email lifecycle issue:

http://windowsitpro.com/blog/behind-scenes-managed-folder-assistant

Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially by Microsoft.

Best regards,

Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Niko Cheng
TechNet Community Support
Tuesday, November 24, 2015 11:14 AM
0

Sign in to vote

Hi Niko,

When I run that command I get the following output for the mentioned variable:

<Name>ELCLastSuccessTimestamp</Name>
<Value>11/12/2015 6:25:20 AM</Value>

It also looks like the error is gone all of a sudden..... weird.

Tuesday, November 24, 2015 11:40 AM
0

Sign in to vote

Hi Niko,

When I run that command I get the following output for the mentioned variable:

<Name>ELCLastSuccessTimestamp</Name>
<Value>11/12/2015 6:25:20 AM</Value>

It also looks like the error is gone all of a sudden..... weird.

I was mistaken the error is still there and I have no clue how to fix this, except not using Exchange Online Archiving.

Friday, November 27, 2015 7:16 AM
0

Sign in to vote

Any resolution on this? i am having the same problem.

I have 10 users with Exchange 2016 on prem mailboxes using Exchange online archives. MRM is not working for any of the users. the folder and folder items are being stamped with the correct retention policies but when i run the "Export-MailboxdiagnosticLogs "user" -ComponentName MRM" command i get the same error as the originaluser. (nothing to do with SCOM)

20/02/2018 16:05:01 Exception: Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcEwsException: ELC
EWS failed with error type: 'ArchiveExchangeWebServiceNotAvailable'. Message: Archive EWS url is unknown.
at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.RemoteArchiveProcessorBase..ctor(MailboxSession
mailboxSession, ADUser user, StatisticsLogEntry statisticsLogEntry, Boolean isCrossPremise, Boolean
isTestMode, MailboxesInformation archiveMailboxesInformation)
at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ArchiveProcessorFactory.Create(ArchiveLocation
archiveLocation, MailboxSession mailboxSession, ADUser adUser, StatisticsLogEntry statisticsLogEntry,
Boolean isTestMode, MailboxesInformation archiveMailboxesInformation)
at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.MailboxData.get_ArchiveProcessor()
at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcUserTagInformation.SaveConfigItem(MailboxDat
aForTags mailboxDataForTags)
at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.InvokeInternal(MailboxDataForTags
mailboxDataForTags)
at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.TagProvisioner.Invoke(MailboxDataForTags
mailboxDataForTags)
at
Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.InvokeInternal(MailboxSession
mailboxSession, MailboxDataForTags mailboxDataForTags)
at Microsoft.Exchange.MailboxAssistants.Assistants.ELC.ElcTagSubAssistant.Invoke(MailboxSession

Wednesday, February 21, 2018 3:32 PM
0

Sign in to vote

The issue is with your proxy server and the oauth protocol. MS exchange does not respect the proxy setting (either set at the OS level or by exchange cmdlet). you have to set your exchange servers to have direct connection to the O365 servers without a proxy server in between. i allowed the EXO ranges over 443 on my firewalls and this resolved the issue. let me know if this helps.

Wednesday, July 25, 2018 1:12 PM