Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Forums Home > Microsoft Enterprise Search Forums > SharePoint - Search (pre-SharePoint 2010) > ComInterop Exception when Crawling MOSS Sites

Answered ComInterop Exception when Crawling MOSS Sites

    •  
      Thursday, May 24, 2007 8:54 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi there

      I have created a Content Source containing a single SharePoint web application. When initiating a full crawl on this content source the crawl immediately stops displaying the following error:

       

      Typelib export: General error. See IError info for more information. (Exception from HRESULT: 0x80131163) (ComInterop Exception)

       

      On the same web app I have also received this following error

       

      Error HRESULT E_FAIL has been returned from a call to a COM component. (ComInterop Exception)

       

      Has anyone here experienced this? Any hints are appreciated.

       

      tia, Bruno

       

    Answers

    • Thursday, July 05, 2007 3:43 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      The same resolution for us. This problem was due to the impersonation settings.

       

      Here the details :

       

      Description of the issue :

       

      Impossible to complete the crawl in MOSS 2007 due to the error :

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

       

      Work Arround :

       

      Open the web.config for the website 80. Find the line : identity impersonate="true"

      If the identity impersonate is set to "false" (which create the error during the crawl), set up to "true".

       

      Then run the crawl again. It completes now sucessfully.

       

      Note: contact the developpers to see the impacts to switch the impersonation to "true" for the security of the portal. If the impersonation was set to false because of the application, you can use the protocol net.tcp instead of the netNamepiped banding. By this way, both crawl and application will work successfully.

       

      Yannick
       

    All Replies

    • Tuesday, June 12, 2007 3:06 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I'm having a somewhat similar issue. I have a single server running MOSS, with search enabled. Strange thing is that the indexer worked up until very recently. Could it be that a Windows Update changed some settings?

      I'm now getting the following error msg in the crawl log:
      http://<sharepointurl>
      Error HRESULT E_FAIL has been returned from a call to a COM component. (Cannot complete this action. Please try again.)

      Also, I checked the event logs and noticed warning msgs such as:

      The start address <http://sharepointurl> cannot be crawled.
      Context: Application 'SharedServices1', Catalog 'Portal_Content'
      Details:
          Unspecified error
       (0x80004005)

      If anyone has suggestions, it would be greatly appreciated.

      Thanks!

       
    • Monday, June 25, 2007 6:39 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I'm getting same error.Any suggestion from gurus.
       
    • Wednesday, June 27, 2007 10:09 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hello Guys,

       

      Did anyone find a solution to this one?  Please let me know, if you have.

       

      Thanks,

      Prashanth

       
    • Thursday, July 05, 2007 12:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      After lot of debugging, we found out the issue was related to imperonation. You need to have impersonation enabled to get the search working. 

       

       
    • Thursday, July 05, 2007 3:43 PM
       
       Answered
      Sign In to Vote
      1
      Sign In to Vote

      The same resolution for us. This problem was due to the impersonation settings.

       

      Here the details :

       

      Description of the issue :

       

      Impossible to complete the crawl in MOSS 2007 due to the error :

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

       

      Work Arround :

       

      Open the web.config for the website 80. Find the line : identity impersonate="true"

      If the identity impersonate is set to "false" (which create the error during the crawl), set up to "true".

       

      Then run the crawl again. It completes now sucessfully.

       

      Note: contact the developpers to see the impacts to switch the impersonation to "true" for the security of the portal. If the impersonation was set to false because of the application, you can use the protocol net.tcp instead of the netNamepiped banding. By this way, both crawl and application will work successfully.

       

      Yannick
       
    • Tuesday, November 06, 2007 5:47 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I tried this and the web.config already had the identity impersonate=true.

      Any other ideas?

       
    • Monday, January 14, 2008 4:43 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Hi Yannick,

       

      I am having the same problem. But my web application requires to be in condition impersonate = false.

      I read ur note .. that we can use protocol net.tcp -->

      but i didn't get excatly what it means. Can you please suggest me any way to solve my problem.

      Any help is appreciated

       

      Thanks,

       
    • Monday, January 14, 2008 4:54 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Sorry Komali, I don't remember another method.

       

      Yannick

       
    • Monday, January 14, 2008 5:04 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote

       

      Thanks Yannick,

      By any chance if you remembers other method at any time. Please post it.

       

      Thanks&Regards

      Komali

       
    • Wednesday, January 28, 2009 4:49 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Yannicks solution worked for me...however i am a little concerned as to what else this can do?

       

      This seems a pretty important thing to change, can anyone advise what else could be impacted by this change?

       

      Many thanks,

       

       
    • Monday, March 23, 2009 9:20 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      HI YANNICK,

      As you suggested
       
      "If the impersonation was set to false because of the application, you can use the protocol net.tcp instead of the netNamepiped banding. By this way, both crawl and application will work successfully. "

      Would you kindly tell me where and how this setting needs to be implemented. Where should one mention the netNamedpiped banding instead of net.tcp?????

      Thanking you in anticipation.


      Regards,
      SHAILENDRA MOHAN