Event ID's 20961 and 28998 during archiving.

book

Article ID: 100032135

calendar_today

Updated On:

Description

Error Message

Event ID: 29061 A problem was encountered while trying to process a saveset in the storage queue. The saveset will be requeued and one more attempt will be made to process it later.  | |Details: <0x8004010f>|Storage Queue Location: C:\EVStorageQueue|Storage Queue Batch File:
C:\EVStorageQueue\EVStorageQueue_1C3BE654F18A7CB4AADC47D47B85B69131210000evserve
r2_20150701184935_00001.EVSQ|Transaction Id:
C0C65A8C87CB8F1B9474651F61869F71|Vault Store Entry Id:
1C3BE654F18A7CB4AADC47D47B85B69131210000evserver2|



Dtrace of StorageCrawler will show the following:

(StorageCrawler) <1416> EV:H {CMsgTraverserBase::Initialise:#137} Completed initialisation: [0x8004010f].

(StorageCrawler) <1416> EV:H {CSMTPTraverserBase::Traverse} (Exit) Status: [<0x8004010f>] (StorageCrawler) <1416> EV:H {CMsgTraverserControl::Traverse} (Exit) Status: [<0x8004010f>] (StorageCrawler) <1416> EV:M CFileSavesetAsMapiSavesetHelper::TraverseMessageOrSaveset - An error occurred 0x8004010F

(StorageCrawler) <1416> EV:M CFileSavesetAsMapiSavesetHelper::TraverseMessageOrSaveset - Exiting

(StorageCrawler) <1416> EV:M CFileSavesetAsMapiSavesetHelper::TraverseAsMessageIfPossible - An error occurred 0x8004010F

(StorageCrawler) <1416> EV:M CFileSavesetAsMapiSavesetHelper::TraverseAsMessageIfPossible - Exiting

(StorageCrawler) <1416> EV:L {CIndexableItemBuilderV2::BuildItem}|Traversing message structure for building new indexable item: <0x8004010f>

(StorageCrawler) <1416> EV:H {CIndexableItemBuilderV2::BuildItem} (Exit) Status: [<0x8004010f>]

(StorageCrawler) <1416> EV:H {CIndexableItemBuilderV2::GetIndexingMetadata} (Exit) Status: [Exception occurred. (0x80020009)]

(StorageCrawler) <1416> EV:M (IIBV2)GetIndexingMetadata() - An error occurred 0x8004010F

(StorageCrawler) <1416> EV:L {CIndexableItemBuilderV2::EndItem} (Entry)

(StorageCrawler) <1416> EV:L IndexableItem::FinalRelease 0X00B8A5B0

(StorageCrawler) <1416> EV:L IndexableItemObject::Clear Size:14 Insertions size:0

(StorageCrawler) <1416> EV:L {CIndexableItemBuilderV2::EndItem} (Exit)

(StorageCrawler) <1416> EV:L {CSavesetXMLBuilder::Unload} Releasing cached XML Indexable Item instance

(StorageCrawler) <1416> EV:L CSavesetPersist::ResetStorage LB: 0xb8bd70 Stg(LB): 0x56d70d0 Stg(doc): 0 File: (null)

(StorageCrawler) <1416> EV:H {CEVByteStream::Flush} (Exit) Status: [Exception](StorageCrawler) <1416> EV~E Event ID: 6727 Abnormal error occurred | |Error: <0x8004010f> |Reference: GIM/gim |Info: 130C498D864C31B439FA1F2534DBBBF5F1110000evserver2 (Journal) | 201507015776574~201303210952240000~Z~C0C65A8C87CB8F1B9474651F61869F71 | |For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3573&error=V-437-6727

(StorageCrawler) <1576> EV:L CItemFetcher::WaitForItem waiting NextISN:1 Wait:5 (secs)(StorageCrawler) <1576> EV:L STAWaitForMultipleObjectsEx: Leaving wait state with result: 0

(StorageCrawler) <1576> EV:L CItemFetcher::WaitForItem Request Info: [1, ifIndexMetadata (3), 10240 (KB), iirmNone (1), 130C498D864C31B439FA1F2534DBBBF5F1110000evserver2+201507015776574~201303210952240000~Z~C0C65A8C87CB8F1B9474651F61869F71+0++0+1+42186.78402777778000000+18+1++1+1+1+1+0+0+681, 1, Abnormal error occurred Error: %1 Reference: %2 Info: %3 %4 %5 For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3573&error=V-437-6727 (0xc0041a47), taken]

(StorageCrawler) <1576> Event ID: 28998 Retrieval of a saveset failed. | |Reason: Abnormal error occurred Error: Reference: Info: For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3573&error=V-437-6727 (0xc0041a47) |Saveset Id: 201507015776574~201303210952240000~Z~C0C65A8C87CB8F1B9474651F61869F71 |Vault Id: 130C498D864C31B439FA1F2534DBBBF5F1110000evserver2 |Index Sequence Number: 1 |Internal Reference: Fetching Saveset for indexing

Cause

The cause of this issue is due to a corrupt message that is SMIME.MultipartSigned and is missing the corresponding P7 attachment from the message.

Resolution

Veritas has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.
 
There are currently no plans to address this issue by way of a cumulative hotfix or service pack in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time, but is not scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see https://www.veritas.com.

Issue/Introduction

Specific items may generate event ID's 20961 and 28988 during archiving. The items will be stored and archived however they will not get indexed.

Additional Information

ETrack: 3814405