Application Pool Not Starting

We had issue in our environment where one of the application pool was not starting hosting all services. After looking at the logs and getting some sense of the error, we tried the following two ways:-

1) Go to App pool in IIS manager, Right click and open Advanced settings, Put in the new password or reset the password again. Once done, restart the app pool.
   If it doesnt start again, try the step 2

2) Go to the Local policy editor and under User rights assignment, add the app pool user under Log on as a batch job and Restart Group Policy Client Service (services.msc).

Sharepoint Search Crawl error (Error HRESULT E_FAIL has been returned from a call to a COM component)

SharePoint search was throwing error very next morning when trying to search anything on the page or were trying to crawl the url's. After looking at the Logs and EV, it was throwing the following error.

Error:-

HRESULT E_FAIL has been returned from a call to a COM component. Troubleshoot issues with Microsoft SharePoint Foundation.

Resolution:-

1) Go to Windows services

2) Click SharePoint Search Service and open properties.

3) Put in the correct new password and restart the service again


It should be good to go now. Reason was that after changing the password in the SP farm, password was not changed under services and that's why was throwing this weird error.

Get the SharePoint farm ID

We were installing 3rd party software where we needed to get  our farm ID to get the license for the software installation.

Resolution:-
We can do this using Powershell:-

Start- Open SP management Shell-

Run these commands in the window.

$SPFarm = Get-spfarm
$SPFarm.ID

Cannot start the SharePoint 2010 Administration Service service after Windows update

We had an issue where our windows team did the server patching upgrade and next day SP admin service did not start. Below is the resolution how to make it work.

Resolution:-
Go to start - gpedit.msc to open the local policy editor

1. Under the Computer Configuration node in the Local Group Policy Editor, double-click Policies.
2. Double-click Windows Settings, double-click Security Settings, and then double-click Public Key Policies.
3. In the details pane, double-click Certificate Path Validation Settings.
4. Click the Network Retrieval tab, click to select the Define these policy settings check box, and then click to clear the Automatically update certificates in the Microsoft Root Certificate Program (recommended) check box.
5. Click OK, and then close the Local Group Policy Editor.

 Try to restart the service again it should start without any issues. You have to update all the servers where this patching was performed.

SharePoint query server not responding (Event ID 2587, 92)

SP query server was in not responding state.We had hard time fixing this problem.Following was the error message while looking at the EVR logs:-
The following conditions are currently affecting index propagation to this server for search service application 'Search Service Application ':
1. Query 0, catalog Main: failing to copy index files from crawl component 0 for 37 minutes. Access is denied.   0x80070005
2. Query 0 will be disabled in 22 minutes so that crawls can continue.

Also while looking at the SP logs, it was showing as follows:--

1b4-c-0 Po] file copy failed (error 0x80070005: Access is denied.   0x80070005, source c:\program files\microsoft office servers\14.0\data\office server\applications\1b4f03ba-b0b4-4b1b-9f7f-7c654df8a6d5-crawl-0\projects\portal_content\indexer\cifiles\00010002.ci, destination \\Server\1b4f03ba-b0b4-4b1b-9f7f-7c654df8a6d5-query-0\1b4f03ba-b0b4-4b1b-9f7f-7c654df8a6d5-query-0\Projects\Portal_Content\Indexer\CiFiles\0000.00010002.ci.cp)  [indexpropagator.cxx:403]  d:\office\source\search\native\ytrip\tripoli\propagation\indexpropagator.cxx   

Resolution:-
We have to make sure couple of points below to make it working:0-
1) The query location address shuould be shared and must have wss_wpg local group added with the change permission.
2) This is the main point that usually people miss it. Make sure that your CA app pool account is added into the Wss_Wpg group. Restart the timer and search service and crawl again. It should be working fine now.