Findings on SharePoint Search – BDC – 2

In search result page, when you click on the “View Profile” page, it does call the database to retrieve the data. So Authentication mode is important here. If you specify “PassThrough”, make sure the “Default content access account” (seem in Search Settings page) has access to that DB. Or, change to “RevertToSelf” and the identify of the application pool will be used – please note this is the SSP application pool, not the central admin application pool. However, for unknown reason, The “Default content access account” still need access to the database, otherwise the crawling will fail even the “View Profile” URL can retrieve the data from database. Also, don’t forget to give “Default content access account” (the account used to crawl) appropriate rights to the BDC application and entity.

Please note that there might be a delay of a few minutes after the permission is changed on BDC application and entity. If the crawling still has “Access denied b BDC” error, wait for a few minutes.

You can delete and re-import the BDC application definition at the anytime – no need to re-crawl as long as the BDC name is not changed.

Incremental Crawl – it’s said that if you add a LastModifiedDate column to the record, SharePoint indexing service will use that as a time stamp and incremental crawling is enabled. However in my various tests, it took virtually same time in full and incremental crawling. Either this doesn’t work, or in my test case, most of the time was spent on retrieving the data instead of indexing them.

Some good articles to read:

This entry was posted in BDC, Search and tagged , , , . Bookmark the permalink.

1 Response to Findings on SharePoint Search – BDC – 2

  1. Tim says:


    Thanks for your articles. I have a specific BDC problem where my BDC crawl log returns this Warning message for an arbitrary set of entities … The object was not found. (The item was deleted because it was either not found or the crawler was denied access to it.)

    Each time I re-run the crawl a different set of entities generate Warnings. Always around 600 (out of 40000). I’ve given the default access account privileges right down to the SQL table that the BDC App references. The IDEnumerator is based on a primary key made up of 2 integers

    Have you ever seen these Warnings?



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s