SharePoint 2013 September 2015 Cumulative Updates

The SharePoint 2013 September 2015 Cumulative Updates have been released:

SharePoint Foundation: https://support.microsoft.com/en-us/kb/2975894

SharePoint Server 2013: https://support.microsoft.com/en-us/kb/2986213

Project Server 2013: https://support.microsoft.com/en-us/kb/2986195

Office Web Apps 2013: https://support.microsoft.com/en-us/kb/3085487

Office Updates: https://support.microsoft.com/en-us/kb/3092181

3 Comments

  1. Hi Trevor,

    SharePoint Server 2013:

    Our Current SP CU is April 2014.

    We have installed September 2015 CU in Development environment and verified the applications are working fine and there are no issues in Server level also.

    The same September 2015 we have installed in Stage and configuration wizard ran successfully but application is not working.

    While browsing getting “Server error in ‘/’ Application”.
    url is blocking at ” https://siteurl.com/_trust/default.aspx

    We are getting the below errors in SharePoint Log and event viewer:

    Error1:

    High SPSecurityContext: Request for security token failed with exception: System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs. at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.ReadResponse(Message response) at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustChannel.Issue(RequestSecurityToken rst, RequestSecurityTokenResponse& rstr) at Microsoft.IdentityModel.Protoco… 75b63e9d-2e96-90bc-1d09-366622e797f9

    Error2:

    Event iD :5617
    There is a compatibility range mismatch between the Web server and database , and connections to the data have been blocked to due to this incompatibility. This can happen when a content database has not been upgraded to be within the compatibility range of the Web server, or if the database has been

    Verified all the services are and app pools are running as is.

    Could you please help me in this situation.

  2. Hi Trevor,

    Thanks for your reply..

    We have reverted the snapshots on the same day and installed September 2015 CU in SharePoint 2013.

    We are not getting the error 1 and applications are working fine.

    However we are getting error 2.

    Now my question is, Can we ignore error2 as applications are working fine without any issues.

    Please let me know your thoughts on this error.

    If we upgrade SP content Databases what exactly it will do. Will it create any other Problems?

    Currently we are working in Staging environment.

Leave a Reply