Forum Discussion

GertjanA's avatar
GertjanA
Moderator
9 years ago

ev1101chf3 - unable to fetch item

hello all,

I have a user complaining she cannot retrieve some items from her archive. We do not allow deletes, nor do we run expiry. From the eventlog, the error 6287 is shown.

Wierd thing is that in the event the offending saveset is listed.

The saveset listed for this user is shown as:

Saveset Id: #57885$11439A0B3C222A145910021C323A105DC1110000sitealias.region.company.com

For another user, same error (way earlier), the saveset listed is:

Saveset Id: 201508290868091~201507291217000000~Z~B09882EED8116CA4DBA8589923343A11

As you see, the first saveset is either malformed, or some sort of format I have not seen before. Has anyone seen this? Should I run EVSVR on her archive, to check?

any advice?

Thanks.

Gertjan

 

 

 

  • Strange, but fixed it anyway.

    I exported the offending folder to a PST file. The export went well, exported the expected 115 items. I opened the PST file in Outlook, and could open each and every item, and the attachments to those items without issues. The items were therefor correctly stored in the archive.

    I then ran an export to pst from that one folder again, with the option to remove the items from the archive. That worked. I then (to be sure) synchronized the index again, to make sure the deletions were processed. I opened the EVS, and that showed the folder was empty.

    I then imported the PST in a test-archive, and verified that after the import, the items were visible, and could be opened from the EVS, including the attachments.

    I then imported the PST back into the original archive, and tested again. The same error occurred...

    I've rebuild the index, same error after rebuild finished. I then exported the same folder again, with 'delete items after exporting'. I then opened the PST, and renamed the folder to another name (basically from 'username' to 'username_2'). I then imported the PST again in the original archive.

    Opened EVS, the new folder showed, and the items can now be opened without issues. It looks like, although items were deleted after the import, there might be a corruption in sql somewherem causing the Savesetid to show #57885$11439A0B3C222A145910021C323A105DC1110000sitealias.region.company.com instead of something like 201508290868091~201507291217000000~Z~B09882EED8116CA4DBA8589923343A11

    User is happy, issue resolved, reason of error unknown.

    GJ

     

  • Weird. Can you dtrace while they try to retrieve to see what the saveset shows up as. You could run an EVSVR ArchiveObjects ObjectContainerExists to check savesets.

  • Hi, I though this weird too.

    I am running an EVSVR verify, but that is terribly slow. I'll let it run through the weekend, to see what that gives.

    User is not in today, so will run dtrace monday.

    Thanks.

  • Strange, but fixed it anyway.

    I exported the offending folder to a PST file. The export went well, exported the expected 115 items. I opened the PST file in Outlook, and could open each and every item, and the attachments to those items without issues. The items were therefor correctly stored in the archive.

    I then ran an export to pst from that one folder again, with the option to remove the items from the archive. That worked. I then (to be sure) synchronized the index again, to make sure the deletions were processed. I opened the EVS, and that showed the folder was empty.

    I then imported the PST in a test-archive, and verified that after the import, the items were visible, and could be opened from the EVS, including the attachments.

    I then imported the PST back into the original archive, and tested again. The same error occurred...

    I've rebuild the index, same error after rebuild finished. I then exported the same folder again, with 'delete items after exporting'. I then opened the PST, and renamed the folder to another name (basically from 'username' to 'username_2'). I then imported the PST again in the original archive.

    Opened EVS, the new folder showed, and the items can now be opened without issues. It looks like, although items were deleted after the import, there might be a corruption in sql somewherem causing the Savesetid to show #57885$11439A0B3C222A145910021C323A105DC1110000sitealias.region.company.com instead of something like 201508290868091~201507291217000000~Z~B09882EED8116CA4DBA8589923343A11

    User is happy, issue resolved, reason of error unknown.

    GJ