Quantcast
Channel: Symantec Connect - Archiving and eDiscovery - Discussions
Viewing all articles
Browse latest Browse all 3821

Problems accessing archived items

$
0
0
Oui, j'ai besoin d'une solution

Hi All,

 

I have a deep rooted issue that I just can't seem to get to the bottom of.

 

I initially came across this issue as I am in a project of decomissioning EV for a customer. I am exporting files from FSA, firstly replacing the placeholders back to the file servers using fsautility -b and secondly exporting the entire archive to a scratch storage using fsautility -t -d.

 

I have came across a small number of files that throw up errors during the export to the scratch storage. The original event id is 41145.

Restoring of file [filename] failed for destination [destination]

Additional info: Error HRESULT E_FAIL has been returned from a call to a COM component.

 

Along with a 6882 event id:

Unable to complete retrieval request

Reason: Decompression failed. The number of bytes actually read does not match the number of bytes expected. (0xc004713d)
 

Both these errors come from the File Server Archive Manager.

 

These errors also lead me on to another underlying issue. I find the file(s) causing the issue and drill down to them using Archive Explorer. When I double click on the item it comes up with "GetOnlineAttachmentFileSize 0x80004005"

 

It also gives the event ids: 6882 and 6287 when trying to open the file.

The 6287 event id is a Web Application (WP) warning stating:

Unable to fetch item from [Server]
Reason: Unspecified error (0x80004005)
Reference: [GOAFS]

I have ran a dtrace against w3wp, storagerestore, storageonlineopns, storagemanagement, storagefilewatch, storagecrawler and storagearchive and recreated the issue when trying to open via archive explorer.

 

The DTRACE is attached.

I am most concerned about the line:

592 11:52:04.917 [4524] (StorageOnlineOpns) <4564> EV:L {CZlibCompressor::LoadInputBuffer:#381} Zero bytes read from the stream, normally indicating end of stream (or a read problem under heavy load).

 

I have tried searching each issue one-by-one, but I feel like I'm chasing my tail with this one. Any help would be appreciated.

Cheers
CD


Viewing all articles
Browse latest Browse all 3821

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>