The file wasnt available to download.

Learn More ». SteveFL wrote: I am wondering if it's because this particular is not "Activated" yet. This particular 'what' is not activated? Need more information than is in the OP: What other roles are on this server? What do the error logs report? Check if access to windows update sites are blocked. Was the installation error free??.. Check windowsupdate. SteveFL This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.

I posted a reply a few hours ago and now that reply is gone Well, here it goes again. But there is no proxy in use. But still face the issue. Note: 1 The same works for MSO Excel build version but not in build which the user is using.

But yet this will be a workaround but not a permanent fix Kindly suggest if we are missing anything from application end or any changes that we need to incorporate? Thanks In Advance Radhika. Thursday, May 2, AM. Hi, we have the same problem. Office Win10 Build: When saving, the upload center will fail to upload An upload error is displayed. This error does not occur with Win10 Sunday, July 7, AM. Hi, we are facing similar problem after updating to W10 MS, Any suggestion? Tuesday, September 24, PM.

Same problem here. If the file gets opened through "Office Online" there is no problem. There should be a mail user object for the user question. If nothing is returned, investigate the user object.

Contact Microsoft Support if the object can't be synced. When performing a Content search or a search associated with a Core eDiscovery case, a transient error occurs and the search fails with a CS error. Update the search and reduce the complexity of the search query. For example, a wildcard search might return too many results for the system to process, which causes a CS error.

When exporting search results from Core eDiscovery or Content search in the Microsoft compliance center, the download takes longer than expected. You can check to see the amount of data to be download and possibly increase the export speed. Find the amount of data that's to be downloaded in the SearchResults and SearchStatistics parameters.

In the results field, find the data that has been exported, and then view any errors that were encountered. Check for any errors in the Trace. If you still have issues, consider dividing searches that return a large set of results into smaller searches. For example, you can use date ranges in search queries to return a smaller set of results that can be downloaded faster.

When you export search results from Core eDiscovery or Content search in the Microsoft compliance center, the export process is not progressing or appears to be stuck. If necessary, rerun the search. If the search last ran more than seven days ago, you have to rerun the search. When you run an eDiscovery search, if the search continually fails and returns an error message that resembles "Internal server error occurred," you might have to rerun the search on specific mailbox locations only.

Break the search into smaller searches, and run the search again. Try using a smaller date range or limit the number of locations that are searched. It might take an additional 2 hours to update the final deployment status, so check back in a couple hours. Error: Resources: It's taking longer than expected to deploy the policy. When downloading search results using the eDiscovery Export Tool, you might receive the following error message:. To resolve this issue, retry downloading the search results.

This will restart the eDiscovery Export Tool. After a successful export, the completed download through the export tool shows zero files in the results. Remove old searches that are no longer required.