locked
Sharepoint Connector SP3 Patch03 giving weird indexing errors RRS feed

  • Question

  • We upgraded the connector over the weekend (yes we know that Patch 03 was retracted, but we have a work around for the user monitor issue and the fixes outway the risks on it).  In our testing in QA, we didn't see any of these errors. Can't figure out what is erroring. I have increased the logs to debug and will update once the connector runs again. Just wondering if anyone else is experiencing issues.  The errors below happened for 1581 documents, but we also processed 62K successfully during the run.

     

    [2012-02-01 12:01:19] ERROR SharePointConnector Depending document failed
    [2012-02-01 12:01:19] ERROR SharePointConnector Error callback: Document [{0e28191a-8af6-4bee-8e58-1fde40feffc5}:{21f167d6-d4a9-4512-9a86-9844bf0f8bac}] with operation ID [2850] failed in sybsystem [ContentAPI]
    [2012-02-01 12:01:19] ERROR SharePointConnector Document 51ff2e3b79722224da501793bf49acb0_bpsharepoint does not exist
    [2012-02-01 12:01:19] ERROR SharePointConnector Error callback: Document [{0e28191a-8af6-4bee-8e58-1fde40feffc5}:{21f167d6-d4a9-4512-9a86-9844bf0f8bac}] with operation ID [1227] failed in sybsystem [indexing]
     

    Wednesday, February 1, 2012 7:18 PM

All replies

  • This simply means that the connector tried to delete a document that is not in the FAST index. There are a number of reasons that this could happen. For example, documents may have been removed from the index without resetting the state tracking database, or the connector may have marked documents as indexed without that actually being the case (maybe the documents failed indexing?).

     

    Thursday, February 2, 2012 6:58 AM