in

Dot Net Mafia

Group site for developer blogs dealing with (usually) .NET, SharePoint 2013, SharePoint 2010, Office 365, SharePoint Online, and other Microsoft products, as well as some discussion of general programming related concepts.

This Blog

Syndication

Archives

Corey Roth [MVP]

A SharePoint MVP bringing you the latest time saving tips for SharePoint 2013, Office 365 / SharePoint Online and Visual Studio 2013.

Enterprise Search Crawl Error: The parameter is incorrect

I have been reconfiguring a search index and running into this issue a lot, so I thought I would post on it.  In my case, I am crawling a content source that comes from a BDC application definition.  The first time I crawl, I get the following error.

The parameter is incorrect. (LobSystemInstance could not be found using criteria 'Name=MyBDCInstance'.)

This is obviously a cryptic error.  As I have said in the past though, if you get an error crawling, always try to crawl again.  In this case, this is exactly the fix for it.  Full Crawl again and everything works just fine.  I am sure there is a good reason this happens, but I have never bothered to look into it.  If you get the error, just crawl again.

Comments

 

Jack Ad. said:

Corey,

I was wondering what one can do if the error does not go away with a full crawl.

I keep getting the same error unless I restart the SQL and the Search Server VMs.  Then everything crawls fine up to 600K + records. Then the error comes in again.  This is definitely not a permission issue and the ADF is published to the correct SSP.

Any guidance would be appreciated.

Thank you.

November 18, 2010 10:50 AM
 

CoreyRoth said:

@Jack Check your ULS logs in your 12 / 14 hive) when you perform a crawl.  Look and see if you can find any additional information that might be related to a permissions error accessing the underlying database or web service you are indexing.

November 22, 2010 4:54 PM
 

Lee C. said:

I was having this problem yesterday.  None of the recommended fixes worked for me.  I ultimately addressed it by deleting the Content Source and all related items (Crawl Rules, Scopes, etc.), then crecreated everything e-x-a-c-t-l-y as before.  This seems to be the unfortunate "solution" to several issues I'm experiencing.  Accordingly, I've scripted as much of it as possible.

December 7, 2010 10:20 AM

Leave a Comment

(required)  
(optional)
(required)  
Add

About CoreyRoth

Corey Roth is an independent SharePoint consultant specializing in ECM, Apps, and Search.
2015 dotnetmafia.
Powered by Community Server (Non-Commercial Edition), by Telligent Systems