Forum Discussion

Elio_C's avatar
Elio_C
Level 6
12 years ago

A COM error occurred: 0x80040205

Hi, any assistance with the below would be greatly appreciated.
 
Trying to synchronise a Vault Cache and some items only display the header info (and the yellow add-in text).
Looking in the client log file there are entries as below for the issue items.
I have rebuilt the Virtual Cache and Outlook profiles and confirmed the items are available via web-links.
 
(FYI EV 9.0.4 with 10.0.2.1210 Add-In for Outlook 2010, Virtual Cache and no shortcuts.)
 
 

18/09/2013 08:02:09.484[6324][H]: Failed to load DOM reason 'A string literal was expected, but no opening quote character was found.

 

' srcText '            <span><H1>Server Error in '/EnterpriseVault' Application.<hr width=100% size=1 color=silver></H1>'

18/09/2013 08:02:35.445[2672][H]: A COM error occurred: 0x80040205

18/09/2013 08:02:35.446[8148][H]: EVMSP: <Annual Assicurazioni 2012> [Common::GetFullItem] Failed to obtain message from the CC: A COM error exception has been caught:80040205

18/09/2013 08:02:38.397[2672][H]: A COM error occurred: 0x80040205

18/09/2013 08:02:38.398[8148][H]: EVMSP: <Annual Assicurazioni 2012> [Common::GetFullItem] Failed to obtain message from the CC: A COM error exception has been caught:80040205

 

 

18/09/2013 08:05:53.310[6324][H]: Failed to load DOM reason 'A string literal was expected, but no opening quote character was found.

 

' srcText '            <span><H1>Server Error in '/EnterpriseVault' Application.<hr width=100% size=1 color=silver></H1>'

18/09/2013 08:06:00.677[1124][H]: A COM error occurred: 0x80040205

18/09/2013 08:06:00.678[8148][H]: EVMSP: <Sent Items> [Common::GetFullItem] Failed to obtain message from the CC: A COM error exception has been caught:80040205

 
  • The cause of this issue is related to large/complex/damaged attachment(s) associated with the affected message.  It is also observed that the EVConverterSandbox process, which converts attachments into HTML, will spike in CPU during the archival process of this message.  Message attachments affected will take greater than 10 minutes to convert during normal archival.

    The default conversion timeout is 10 minutes per object.

    Workaround :
    Add the affected attachment type to be excluded from conversions.  This will stop Enterprise Vault (EV) from attempting to convert these attachment types to HTML. 

    Registry key value:
    ExcludedFileTypesFromConversion

    Location
     HKEY_LOCAL_MACHINE
     \SOFTWARE
      \KVS
       \Enterprise Vault

    Content
     String value containing list of file types. The list format is:

    .filetype[.filetype].

    Prefix each file type with a period and end the list with a period.

    For example:

    .GIF.JPG.

     

  • Thanks for your response Ajay

    The error is in the client log when trying to synchronise the vault cache not at the time of archiving.

    The items are visible via the /archiveexplorerui.asp page, the message body and attachments can be opened/viewed as normal. This only happens to some not all messages. The particular messages I'm looking at do have attachments but then others with attachments are synchronised as normal.

     

     

  • Hey EC.

     

    I do not agree with teh workaround provided. I think that if you ahve some level of reproducibailty and this is breaking the VC from loading for you, you should reach out to support. I do not believe skipping the indexing of these items will help your client issues.

     

    I have seen these sorts of issues after a client upgrade. Have you tried a new profile or resetting the VC?

     

    Regards,

  • Thanks for your response TypoProne.

    Yes, the error is in the client log when trying to synchronise the vault cache not at the time of archiving. I have cleared out the current local cache, reinstalled the 10.0.2.1210 add-in and created a new outlook profile (general client cache troubleshooting) and still have the same issue.

    I am going to test on another clean build PC and also try the 10.0.4.1189 add-in tomorrow to establish if it's an archive (content) or client issue.