none
Crawl Error message 778 RRS feed

  • Question

  • In the crawl log I have a file marked as an error with "The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)". When I looked at the SQL MSSCrawlURLLog and MSSCrawlURL records for the document, the ErrorID is 778. The MSSCrawlErrorList table doesn't contain a record with ErrorID of 778 (stops at 776) so where is the message being taken from?

    Thanks, Shane


    Thursday, July 14, 2011 4:58 PM

Answers

  • Being outside of things I know, it might be that the id has been added later on without a matching description in the joining table.

    And as these are internal tables without any documentation we are left to play around.

    PS! Keep in mind that doing sql queries directly against a SharePoint database is not allowed / will void warranty. But I assume you are doing this in a dev/test environment ;)

    -m


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Marked as answer by S h a n e Monday, July 18, 2011 3:44 PM
    Sunday, July 17, 2011 10:55 AM

All replies

  • Hi Shane,

    The id is not what is important, but the message. The file you get an error on, is it open in an application which has lock on it, or do you have anti-virus software which might hold a lock on the file? Is the file from a file share?

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    Saturday, July 16, 2011 6:36 PM
  • Hi Mikael,

    I want to completely recreate the crawl log in MS-Access so I exported the MSSCrawlURLLog, MSSCrawlURL and MSSCrawlErrorList tables but when I joined them there was no field value for ID 778 which made me think that there were other tables I needed to export, are there? That's what prompted my question. The actual file was indeed probably locked by anti-virus.

    Thanks, Shane

    Saturday, July 16, 2011 7:15 PM
  • Being outside of things I know, it might be that the id has been added later on without a matching description in the joining table.

    And as these are internal tables without any documentation we are left to play around.

    PS! Keep in mind that doing sql queries directly against a SharePoint database is not allowed / will void warranty. But I assume you are doing this in a dev/test environment ;)

    -m


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    • Marked as answer by S h a n e Monday, July 18, 2011 3:44 PM
    Sunday, July 17, 2011 10:55 AM
  • Hi Mikael,

    yes indeed it is only on a test server but thanks for the reminder anyway.

    Thanks, Shane

    Monday, July 18, 2011 3:43 PM