SharePoint 2010 and SharePoint 2013 August Cumulative updates.

SharePoint 2013 August Cumulative updates.

·         SharePoint Server 2013 Cumulative updates: KB 2883086, KB 2883085, KB 2883078, KB 2880559, and KB 2760213 

·         SharePoint Foundation 2013 Cumulative updates: KB 2883081

·         SharePoint Server 2013 with Project Server Cumulative updates: KB 2883083 

·         Office Web Apps Server 2013 Cumulative updated: KB 2883093 

SharePoint 2010 August Cumulative updates:

·         SharePoint Foundation 2010: KB 2889825  and KB 2760757

·         SharePoint Server 2010: KB 2889831 and KB 2883011

For more details check MS SEE Stefan Gossner’s Blog:

http://blogs.technet.com/b/stefan_gossner/archive/2014/08/13/august-2014-cu-for-sharepoint-2010-has-been-released.aspx

http://blogs.technet.com/b/stefan_gossner/archive/2014/08/13/august-2014-cu-for-sharepoint-2013-has-been-released.aspx

Product Applies to: SharePoint Server 2010 and SharePoint Server 2013.

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

Troubleshooting:

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.

Resolution:

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.

Another reference with different resolution: http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-2010-search-internal-server-error-exception-system-nullreferenceexception.aspx

Product Applies to: SharePoint Server 2010.

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.

Troubleshooting:

I revised all the steps mentioned in the Install SharePoint 2013 on a single server with a built-in database.

Have read some of the threads on internet  http://social.technet.microsoft.com/Forums/sharepoint/en-US/bba93428-364c-4afc-ac7e-57783f15f165/standalone-install-sddl-string-contains-an-invalid-sid?

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.

Resolution:

Blog explaining the issue:  http://squidpip.com/blog/sharepoint-server-2013-release-to-manufacturing-version-standalone-installation.

Resolving Step 1: http://squidpip.com/blog/sharepoint-2013-resolving-the-sddl-issue.

Resolving Steps 2: http://squidpip.com/blog/sharepoint-2013-resolving-the-sddl-issue-part-2

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

HTTP 405 Method not allowed + PerformancePoint Dashboard Designer + SharePoint Server 2013

Issues: When opening a Performance Point Dashboard Designer using SharePoint 2013 you get below error message.

Error: HTTP 405 "Method not allowed".

Background: We had some users who tried to create Performance Point Dashboard using Performance Point in SharePoint Server 2013. But when browsing the site they get error message.

Their dashboard creation shows successful. But when they tried to browse the dashboard it failed.

Troubleshooting:

Before moving any further I thought of letting you all read about what is HTTP 405 “Method not allowed” error is about.

A very good reference is: http://www.checkupdown.com/status/E405.html

I checked if the Performance Point service was configured correctly and based on what I Had read about the HTTP 405 error it seems to be an issue with the failure of authentication to some level and needed to find at where it is failing. 

Resolution:

MS KB: http://support.microsoft.com/kb/2755141 has given me the final direction about the resolution.

It says user will get the above issue in one of the following scenarios:

·         You configure a web application to use multiple authentication methods in Microsoft SharePoint Server 2013.

·         You use forms-based authentication to log on to the web application.

·         You use Windows authentication to open the PerformancePoint Dashboard Designer.

First, point explained the issue well, when I had checked that we had implemented more than one type of authentication on a single zone.

Have configured the PerformancePoint Dashboard and the web app IN CA to use same authentication method and it solved the issues for the users.  

Applies to: SharePoint Server 2013, Performance Point Dashboard.