Last night I tried changing the application pool that the SharePoint service accounts use to be a lesser privileged account (it had been originally set up to use the farm account!). I added a new managed account and updated the IIS service applications app pool to use this new account via Central Admin. Most everything worked fine, all the other service apps with the exception of the search service. When searching for sites or people, the results page would not load and the error in the ULS logs was:
CoreResultsWebPart::OnInit: Exception initializing: System.NullReferenceException: Object reference not set to an instance of an object
Are there other permissions that need to be set somewhere in order for the search to work? Do the search databases need special permissions?
Yes the services are started and I did an iisreset. I ended up changing the app pool account back to the old one so that search would not be down. It did work after changing the app pool account back to the farm account. Hence why I’m pretty sure that the issue is with the permissions of the account that I tried to change it to.
And of course, did you do the magic fix for all SharePoint issues? “iisreset”
Can you check if your services are started?
- SharePoint Server Search
- Search Query and Site Settings Service
