Monday, August 18, 2014

SharePoint 2010: Internal Server Error exception while performing Search

Issue: While performing search on any level of the site users getting the error message:

Error Message: Internal server error exception: Troubleshoot issues with Microsoft SharePoint Foundation

Background: Our SharePoint 2010 Search is just recently been extended to next level and when user performed search they started getting error message. There were no major changes in the search service application.

But looking at the event logs it seems to be an issue with the Configuration of the search topology.

Event ID 8031 was reported with the message.  

An exception occurred while updating addresses for connected app {eaf6c00c-cc3f-460e-8bf2-ad9b991ea6ea_aa16845d-045a-46bc-bbc6-d701ff13950d}. The uri endpoint information may be stale. System.InvalidOperationException: The requested application could not be found at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ProcessCommonExceptions(Uri endpointAddress, String operationName, Exception ex, SPServiceLoadBalancerContext context) at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.ExecuteOnChannel(String operationName, CodeBlock codeBlock) at Microsoft.SharePoint.SPTopologyWebServiceApplicationProxy.GetEndPoints(Guid serviceId) at Microsoft.SharePoint.SPConnectedServiceApplicationAddressesRefreshJob.Execute(Guid targetInstanceId) bf94139a-66f8-4aab-af31-406a5ebb6db9


Checked the search settings on all the levels and it was fine.
Checked the configuration changes from the search service application prospective.
Checked the permissions level of the search Content access account and Search Service account.
Everything was fine until we realized.


That the web application which was associated with the Search Service Proxy but the Search Service Proxy was not associated with the Search Service application. We re-associated the correct web application with a valid Search service application proxy and asked user to perform the search and it did worked fine.

You need to go to CA, Manage service applications option. To do this, follow these steps:

1.    Open Central Administration.
2.    Click Manage web applications.
3.    Select the affected web application.
4.    On the ribbon, click Service Connections.
5.    Under Configure Service Application Associations, select the valid Search service application proxy check box.

Product Applies to: SharePoint Server 2010.

Sunday, August 17, 2014

SharePoint Server 2013 Standalone installation: An exception of type System.ArgumentException was thrown. Additional exception information: The SDDL string contains an invalid sid or sid that cannot be translated.

Issue: While installing SharePoint 2013 in the development environment in a workgroup got the error message.

Error: An exception of type System.ArgumentException was thrown. Additional exception information: The SDDL string contains an invalid sid or sid that cannot be translated.
Parameter name: sddlForm

To diagnose the problem, review the application event log and the configuration log file located at:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\PSCDiagnostics %%%%%%%%.log

Background: While everything ran smoothly, Product and configuration wizard failed at step 8 showing the above error.


forum=sharepointadmin and best approach I had found and which resolved my issue by creating a search service account and configuring it as search service account by following the steps give in the below articles.


By following the above steps my issue was resolved and was able to run PS configuration wizard smoothly by running few last steps and completed with Step 8, 9 and 10 and my set-up is complete now.

If you have any issue implementing the above given steps do let me know. It would be my immense pleasure to assist you.

Product Applies to: SharePoint Server 2013 and SharePoint Foundation 2013


snow flakes

blogger widgets Blogspot Tutorial


Related Posts Plugin for WordPress, Blogger...