Tuesday, December 26, 2017



SharePoint Document error on opening document using DocIdRedir.aspx


We are using SharePoint 2010 to host documents for Dynamics Ax, in our organization. Our SharePoint architecture consists of one back-end server and one front-end server. Recently we have experienced and issue in SharePoint document handling site. The issues was that documents cannot be opened using DocIdRedir.aspx search page in SharePoint.
Error description: Could not look up Document Id "xxx" due to an error encountered in Microsoft Search Server. The request channel timed out while waiting for a reply after 00:01:00.
  • I increased 'Time-out' property value (Navigation: Central administration -> Application management -> Manage services on server -> SharePoint server search) of search service from 60 seconds to 120 seconds.
  • Restarted 'SharePoint server search' service in both servers.
  • Restarted front-end server.
  • Reset Search Index (Navigation: Central administration -> Application management -> Manage service applications -> Search Service Application -> Index reset).
  • Full crawl was performed after index reset.
But, nothing worked. Document Id settings (Navigation: Document site home page -> Site Actions -> Site Settings -> Site Collection Administration -> Document Id Settings) was also not opened. It was also throwing time out error.
Finally I stopped and disabled 'SharePoint server search' service in both servers. Still the search service status was shown as 'Started' in both server. So, I tried to stop the services using SharePoint PowerShell command.
  • Found Search service GUID using 'Get-SPServiceInstance' command
  • Executed command 'Stop-SPServiceInstance -Identity <ServiceGUID>' from both servers, to stop service
But, it was throwing error that a component (with a GUID 'xxx-query-13') was still up and running.
Search service status was shown as 'Unprovisioning' in PowerShell 'Get-SPServiceInstance' command, and status in central administration search service was shown as 'Stopping'.
As DocIdRedir.aspx option was still not working, I restarted both the servers at a time. Please note that I had restarted only front-end server earlier.


And all of sudden, DocIdRedir.aspx started working! Document Id settings is also opened!
Search service status is shown as 'Started' in Central administration. But, the status is still shown as 'unprovisioining', when I execute 'Get-SPServiceInstance' command from PowerShell.
Well, I ignore it for now. Because, the lookup issue has been resolved and the users are happy J


I don’t know if I should have restarted both server before trying anything else. I will try it, if the error will be reoccurred. But, I would like to share my experience here, assuming it will be helpful for someone.


Thank you for reading.