Ediscovery Cannot Continue the Application is Improperly Formatted
DragonsRule This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. 
I seem to recall having trouble with that in any browser other than IE.
2 found this helpful thumb_up thumb_down
LarryG
Well that seems to have done the trick. I tried it in IE on Win10 and it is working fine now. Thanks a ton for the help.
Mike
1 found this helpful thumb_up thumb_down
No problem
Was this post helpful? thumb_up thumb_down
Old discussion I know, but one key I found when doing this, and it didn't have to do with using IE as a browser (Though I'm sure that's a good idea).
It appears that if I tried to run this on an internal LAN, it would use the NetBIOS name of the local host; this would not work. You can see the problem when you click "Details" on the error. The path will show up something like this:
PLATFORM VERSION INFO Windows : 6.2.9200.0 (Win32NT) Common Language Runtime : 4.0.30319.34209 System.Deployment.dll : 4.0.30319.34274 built by: FX452RTMGDR clr.dll : 4.0.30319.34209 built by: FX452RTMGDR dfdll.dll : 4.0.30319.34274 built by: FX452RTMGDR dfshim.dll : 6.3.9600.16384 (winblue_rtm.130821-1623) SOURCES Deployment url : /microsoft.exchange.ediscovery.exporttool.application?name=ce66od_1&ews=https%3A%2F%2Flocalhost%2Fews%2FExchange.asmx">https://localhost/ecp/15.0.1076.9/exporttool/<servername>/microsoft.exchange.ediscovery.export... SUMMARY Below is a summary of the errors, details of these errors are listed later in the log. * Activation of /microsoft.exchange.ediscovery.exporttool.application?name=ce66od_1&ews=https%3A%2F%2Flocalhost%2Fews%2FExchange.asmx">https://localhost/ecp/15.0.1076.9/exporttool/<servername>/microsoft.exchange.ediscovery.export... in exception. Following failure messages were detected: + Downloading /microsoft.exchange.ediscovery.exporttool.application?name=ce66od_1&ews=https://localhost/ews/Exchange.asmx">https://localhost/ecp/15.0.1076.9/exporttool/<server... did not succeed. + The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. + The remote certificate is invalid according to the validation procedure.
If the https address says "localhost" or "yourinternalservername", this will not work. In my case, I copied that deployment url, edited it and pasted it back in using my MX record, like so:
https://mail.myservername.com/ecp/15.0.1076.9/exporttool/<servername>/microsoft.exchange.ediscovery.export....
This resolves that issue; the application downloads and runs, even if you're running it from a box on your internal LAN. Alternately, you may be able to specifically log in to the ECP and ensure you're using https://mail.myservername.com/ecp instead of https://myinternalservername/ecp .
I found this of critical importance and hope it helps someone else.
3 found this helpful thumb_up thumb_down
Perfect - using the full name has worked -many thanks!
Sarah
Was this post helpful? thumb_up thumb_down
Stellar EDB to PST Converter is the best alternative of Exchange 2013 eDiscovery Export Tool. The software exports mailboxes to PST in three simple steps. You can also check the preview of mailboxes by downloading the demo version from Official website: https://www.stellarinfo.com/email-repair/edb-pst-converter.php
Was this post helpful? thumb_up thumb_down
This below one worked well for me in Chrome.
PROBLEM
Consider the following scenario. In Microsoft Exchange Online, you create an eDiscovery mailbox search in the Exchange admin center. You're then ready to export the search results to a PST file. You click Export to a PST file, and then you're prompted to install the eDiscovery PST Export Tool. However, after you install and start the eDiscovery PST Export Tool, you experience one of the following symptoms:
If you're using Windows Internet Explorer 9.0 or later, the application tries to connect but then crashes without displaying an error message.If you're using a third-party browser, you receive the following error message:
Cannot Download the application. The application is missing required files. Contact application vendor for assistance.
CAUSE
This issue may occur if one or more of the following conditions are true:
You're using Internet Explorer 9.0 or later, and you don't have the Microsoft .NET Framework 4.5 or later installed.Local intranet zone settings aren't set up correctly in Internet Explorer.You're using a third-party browser, and you don't have the ClickOnce browser extension installed.You're using an outgoing proxy server, and the connection times out.
SOLUTION
To resolve this issue, do one or more of the following, as appropriate for your situation.Scenario 1: You're using Internet Explorer 9.0 or later, and you don't have the .NET Framework 4.5 or later installedInstall the .NET Framework 4.5 or a later version.Scenario 2: Local intranet zone settings aren't set up correctly in Internet Explorer
Make sure that https://*.outlook.com is added to the Local intranet zone in Internet Explorer. To do this, follow these steps:
In Internet Explorer, click Internet Options on the Tools menu.On the Security tab, select Local intranet.Click Sites, and then click Advanced.Add https://*.outlook.com (if it's not already listed).Click Close.
Additionally, make sure that the following URLs are not listed as Trusted zone sites:
https://*.outlook.comhttps://r4.res.outlook.comhttps://*.res.outlook.comScenario
3: You're using a third-party (non-Microsoft) browser, and you don't have the ClickOnce browser extension installedInstall the ClickOnce extension. The extension can be found on the add-on webpage for that browser.
For Mozilla Firefox: https://addons.mozilla.org/en-US/firefox/extensions/?sort=featuredFor Google Chrome: https://chrome.google.com/webstore/category/appsScenario 4: You're using an outgoing proxy server, and the connection times outUse the netsh command-line tool to open port 8080 on the proxy server. To do this, follow these steps:
Open a Command Prompt window, and then run the following command:
netsh winhttp show proxy
Run the following command:
netsh winhttp set proxy proxyservername:8080
For example:
netsh winhttp set proxy proxy.contoso.com:8080
Was this post helpful? thumb_up thumb_down
I could only get it working with Edge... but it was perfect under that browser.
Was this post helpful? thumb_up thumb_down
I was having trouble with the Export Tool and came across this page (and a lot of similar pages). After beating my head against the wall for a couple hours I was finally able to solve it by using "Run as administrator" when opening Internet Explorer. Give that a try, maybe it will save you some time....
Was this post helpful? thumb_up thumb_down
I feel so dumb, that was it!
Thanks so much for sharing!
Was this post helpful? thumb_up thumb_down
Try enabling ClickOnce support -
Was this post helpful? thumb_up thumb_down
Source: https://community.spiceworks.com/topic/1126062-exchange-2013-ediscovery-export-tool-will-not-install
0 Response to "Ediscovery Cannot Continue the Application is Improperly Formatted"
Post a Comment