Crawling Exchange Public Folder: error

Question

Hi, i'm trying to configure a content source in the search administration panel of a Sharepoint 2010 installation, to crawl an exchange public folder.

When i start the crawl, the system throw me this error:

The start address exchange://[path] cannot be crawled.

Context: Application 'FAST_Search_Connector_Search_Service_Application', Catalog 'Portal_Content'

Details:

Error while crawling LOB contents. (0x8004fd11)

 

The user configured to crawl the public folder have the correct permission.

Any suggestion is appreciated.

Thanks.

Nicola

Answer 1

Hi,

Sharepoint cannot crawl both sharepoint sites and file shares/exchange folders in the both content source.

And sharepoint cannot crawl the same start addresses more than once in the same search service application.

For more information about crawling, please refer to:

http://technet.microsoft.com/en-us/library/cc280343.aspx

Regards,

Seven

Answer 2

Hi Seven,

the content source that refers to the exchange public folder doesn't have any sharepoint sites/file shares defined. The only path defined is the exchange public folder address.

Also, the search service application is configured with only one start addresses for each different path to crawl. To define the content source and the crawl for the exchange public folder i've followed the following article: http://technet.microsoft.com/en-us/library/ee806927.aspx, but without success.

 

Regards,

Nicola

Answer 3

Hi,

Please make sure you have configure it correctly. please check your configuration based on:

http://technet.microsoft.com/en-us/library/ee806927.aspx

Regards,

Seven

Answer 4

Hi,

yes i've followed the article you posted, as you can see from my previous reply.

 

Regards,

Nicola

Answer 5

Nicola,

Did you find a solution to your problem? I am getting the same error and have not had much luck finding a solution.

Regards,

Paul

Answer 6

Hi Paul,

i'm sorry but for now i've stopped any testing on crawling exchange public folder, because the migration project to sharepoint 2010 had the priority on this.

After the end of the migration i'll surely start again with this task, but i think i will open a microsoft case on this, due to the poor documentation online.

Regards,

Nicola

Answer 7

Thanks for the reply!

Paul

Answer 8

Paul-

did you ever get resolution to this? This problem just popped up in our environment.

Answer 9

From: http://iedaddy.com/2007/08/sharepoint-2007sps3-protocol/

If you want to crawl the exchange public folders, use RB or RBS protocol....

RB protocol	RB://	Used to index Exchange Server public folders
RBS protocol	RBS://	Used to index Exchange Server public folders over SSL

Answer 10

Thanks for the reply, but no dice. I think those protocols have been depreciated for SP2010:

Error while crawling LOB contents. ( The URI prefix is not recognized.)

But thanks for the suggestion!

Answer 11

It's one of two things, either the SP server is making malformed requests to OWA or OWA is returning errors or malformed responses. Since the behavior is the same in spdev and spprod, talking to the same prod Exchange servers, I'm leaning towards it being an Exchange issue.

Answer 12

Hi Scott,

if you found the solution let us know, because i'm stucked on this since months.

Answer 13

Well I fired up Wireshark to take a look at the conversation between Exchange and SharePoint. From what I see, Exchange is returning valid data and SharePoint's Filter Daemon is choking on it, for some reason.

I think I'm going to burn a support ticket for this.

Answer 14

Nicola-

I haven't called MS yet, but I did notice that in our environment, it seems that the public folders that were upgraded from Exchange 2003 still are being crawled. It's only the folders that we have created since migrating to 2010 that won't crawl.

Weird, huh?

Answer 15

Hi Scott, in my environment i have Public Folders only create after migrating to 2010 so i cannot test it.

If it's "work as intented" i'm sure it was a bug and MS should release a fix for this.

Let me know if you contact MS with a support ticket.

Regards,