I was looking for a way to troubleshoot search crawl errors a little bit better and figured why not use a tool I already use daily…Fiddler! Here is a quick guide on how to use Fiddler2 as a search proxy so you can see what is happening when the user agent is crawling the content.
- Login to the appropriate SharePoint 2010 Application Server where Fiddler is installed
- Run Fiddler2 as the SharePoint 2010 default content access account
- Minimize the Fiddler2 window and browse to http://localhost:8888
- You should see a screen similar to this:
- Login to central admin
- Go to Application management > Manage Service Applications > Search Service Application
- Click on None next to Proxy Server: Select “use the proxy server specified” and type http://localhost for Address and 8888 for port.
- Click OK
- Now run a full crawl on the content source in question. The crawl results will appear in the Fiddler2 window on the server.
Now watch for any errors…especially those pesky red 500 errors!