Answered by:
Unable to download Outlook Add-ins

Question
-
I'm totally lost. My exchanges server is functioning with out issues except when I try to install an add in from the MS store. After selecting the add-in. I get a message saying "ERROR The app could not be downloaded." The event log records Event id 6. CMDlet Failed. Cmdlet new-App parameters - OrganizationApp "True" -MarketplaceAssetID "WA104218067" -MarketPlaceQueryMarket "en001" -MarketPlaceServiceURl "https://officeclient.microsoft.com/config16" -Etoken "" -DownloadOnly "True"
This happens on both the Exchange server and the outlook client.
Exchange 2016 CU16 on a Hyper VM
MS Outlook 2016
Host server 2016
Log Name: Application
Source: MSExchangeApplicationLogic
Date: 06/09/20 11:43:08 AM
Event ID: 3018
Task Category: Extension
Level: Error
Keywords: Classic
User: N/A
Computer: Exchange2016.Corp.*******.com
Description:
Scenario[ServiceHealth]: GetKillBit. CorrelationId: 89f9ba3e-2922-4f3a-8390-eb74fc948006. The request failed. Mailbox: Url: https://store.office.com/appinfo/query?rt=XML&corr=89f9ba3e-2922-4f3a-8390-eb74fc948006 Exception: System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass18_0.<EndGetResponseCallback>b__0()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeApplicationLogic" />
<EventID Qualifiers="49156">3018</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-09T15:43:08.400755600Z" />
<EventRecordID>9779756</EventRecordID>
<Channel>Application</Channel>
<Computer>Exchange2016.*************.com</Computer>
<Security />
</System>
<EventData>
<Data>GetKillBit</Data>
<Data>89f9ba3e-2922-4f3a-8390-eb74fc948006</Data>
<Data>
</Data>
<Data>https://store.office.com/appinfo/query?rt=XML&corr=89f9ba3e-2922-4f3a-8390-eb74fc948006</Data>
<Data>System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)Help!
Sandor Borbas
- Edited by Sandor Borbas Tuesday, June 9, 2020 4:59 PM
Tuesday, June 9, 2020 3:36 PM
Answers
-
Hi Sandor,
What's the detailed version of your Exchange 2016? You can check with the following command:
Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion
If you have enabled TLS1.2 in Windows Schannel, please check and make sure TLS 1.2 is enabled for .NET 4.x. Go to Registry Editor, create SystemDefaultTlsVersions registry entry and set to 1 in these locations:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001
The SystemDefaultTlsVersions registry value defines which security protocol version defaults will be used by .NET Framework 4.x. If the value is set to 1, then .NET Framework 4.x will inherit its defaults from the Windows Schannel DisabledByDefault registry values. If the value is undefined, it will behave as if the value is set to 0.
Then you have to restart your computer for the change to take effect. Additionally, here is a similar issue for your reference: Can't install add-ins from store.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
- Edited by Lydia ZhouMicrosoft contingent staff Wednesday, June 10, 2020 2:07 AM
- Proposed as answer by Udara Kaushalya Wednesday, June 10, 2020 3:50 AM
- Marked as answer by Sandor Borbas Friday, June 12, 2020 3:36 PM
Wednesday, June 10, 2020 2:06 AM
All replies
-
Hi Sandor,
What's the detailed version of your Exchange 2016? You can check with the following command:
Get-ExchangeServer | Format-List Name,Edition,AdminDisplayVersion
If you have enabled TLS1.2 in Windows Schannel, please check and make sure TLS 1.2 is enabled for .NET 4.x. Go to Registry Editor, create SystemDefaultTlsVersions registry entry and set to 1 in these locations:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319] "SystemDefaultTlsVersions"=dword:00000001
The SystemDefaultTlsVersions registry value defines which security protocol version defaults will be used by .NET Framework 4.x. If the value is set to 1, then .NET Framework 4.x will inherit its defaults from the Windows Schannel DisabledByDefault registry values. If the value is undefined, it will behave as if the value is set to 0.
Then you have to restart your computer for the change to take effect. Additionally, here is a similar issue for your reference: Can't install add-ins from store.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
- Edited by Lydia ZhouMicrosoft contingent staff Wednesday, June 10, 2020 2:07 AM
- Proposed as answer by Udara Kaushalya Wednesday, June 10, 2020 3:50 AM
- Marked as answer by Sandor Borbas Friday, June 12, 2020 3:36 PM
Wednesday, June 10, 2020 2:06 AM -
Lyndia
Thanks for the reply. I implemented the tls registry changes but it didn't make a difference and as you can see by the event viewer entry above, it does not have a url to Invoke-WebRequest. To me it seems to be an office365 issue. We do have an online presence with the same account login but not and email address. This work with out any issues before MS switch the add ins to office365. Any further suggestion?
SABorbas
Wednesday, June 10, 2020 4:57 PM -
Did you restart the server after modifying the Registry Editor?
If your Exchange Server has an internet connection, please check the proxy server to see whether the URL in your event log is enabled for access "https://store.office.com/appinfo/query?rt=XML&corr=89f9ba3e-2922-4f3a-8390-eb74fc948006". For your reference: Event MSExchangeApplicationLogic 3025 & 3018.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Friday, June 12, 2020 7:01 AM -
Lyndia
I found the problem. I had a typo in one of my registry entry for the tls setting. One I fixed it all started to work. Thankyou for your help. Much appreciated
Sandor Borbas
Friday, June 12, 2020 3:36 PM -
Glad to hear that. If you have any other issues about Exchange, please feel free to post in our forum.
Have a nice day.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Monday, June 15, 2020 1:19 AM