SharePoint 2013 Crawl Access Denied Error

I usally can fix these crawl errors fast. DisableLoopbackCheck, Check Web App permissions, check DB permmisions…

But all was configured correctly. All other web apps were being index and running smooth. I just had one web app that would not get indexed. I even deleted the web app and recreated the site since it was a QA server.

Even the logs were not very clear. Just some access denied to robots.txt. I dont even use robot.txt files…

After many hours i decided to ping the FQDN and that when i noticed the issue. Someone in Networking team created the DNS as a C-Name alias. Which means it would return the name of the computer and not the proper name. It was also pointed to an incorrect WFE server.  Once they changed it to a A- Record DNS Search was able to index.

BI Resources and Links

Here’s a list of blogs that has helped me configure Power Pivot for SharePoint 2010 and 2013

SharePoint 2013 Kereberos setup http://blog.blksthl.com/2012/09/26/the-first-kerberos-guide-for-sharepoint-2013-technicians/#step4

Installing 2013 BI features : http://blogs.msdn.com/b/querysimon/archive/2012/11/26/installing-the-bi-features-of-sharepoint-2013.aspx

Installing 2010 BI features: http://blog.cloudshare.com/2012/05/22/step-by-step-guide-to-installing-sharepoint-with-sql-2012-powerpivot-powerview-and-reporting-services/

another 2010 BI blog: http://blogs.msdn.com/b/karang/archive/2012/04/13/step-by-step-guide-of-installing-power-view-with-powerpivot-2012.aspx

Notes: things get tricky in a multi server farm. the SQL install will have all the features needed for SharePoint. For SharePoint 2013 there is a spPowerPivot.msi you can use on the WFEs instead of the SQL server install.

Application Pool Password Recovery

I had to figure out an App Pool password. Depending on your version of IIS you can extract passwords. You just need to login remotely and have local admin access.

For IIS 6

Download resource kit from http://www.microsoft.com/en-us/download/details.aspx?id=17275

And run Metabase Explorer, then just browse to your App Pool. Change your view settings to show Secure Data.

For IIS 7+

run this powershell command with your app pool name.

&$env:windir\system32\inetsrv\appcmd.exe list apppool “Application Pool Name” /text:ProcessModel.Password

 

 

 

1 2 3 4 5