none
SharePoint 2013 - Parsing Errors and Possible Corrupt Configuration Database

    Question

  • All,

    We seeing some odd errors after the last round of patches in our SharePoint 2013 farm (2 WFEs, 1 Central Admin Server, 1 Search Server, 1 Distributed Cache) where this patch KB3102467 - Microsoft.Net Framework 4.6.1 for Windows Server 2012 R2 for x64 caused issues noted here:

    https://support.microsoft.com/en-us/help/3102467/the-.net-framework-4.6.1-for-windows-server-2012-r2-on-windows-update

    To try and remedy we installed the Dec 2016 CU -> https://support.microsoft.com/en-us/help/3128005/december-13,-2016,-cumulative-update-for-sharepoint-server-2013-kb3128005 which helped a little bit. At one point we did run through the psconfig wizard with the following command: psconfig -cmd upgrade -inplace b2b -wait -force

    We are pretty certain we may have some kind of corruption in our configuration database and wonder what is the best way to fix such corruption.


    The errors are that it appears sometimes are pages when accessed show parser errors as noted below:

    Parser Error
      Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

     Parser Error Message: The server tag is not well formed.

    Source Error:


    Line 190:        <SharePoint:CssRegistration name="/_catalogs/masterpage/klg/css/departmentlayout.css" runat="server" after="SharepointCssFile" />
    Line 191:        <SharePoint:CssRegistration name="/_catalogs/masterpage/klg/css/Core.css" runat="server" after="SharepointCssFile" />
    Line 192:        <script type="text/javascript" src="/_catalogs/masterpage/klg/js/jquery.min.js">//<![CDATA[
    Line 193:       
    Line 194:       

     Source File:  /private/north/_catalogs/masterpage/klg/klgPrivateMaster.master    Line:  192


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1087.0

    Other errors in the eventvwr - I see are as such:

    UpdatedConcurrencyException: The object SPTenantLogUsageDefinition was updated by another user.  Determine if these changes will conflict, resolve any differences, and reapply the second change.  This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread.

    Performance Counter OS (pdh) call failed with error code PDH_INVALID_DATA

    SystemMetricsTraceAggregator error getting next value System.ComponentModel.Win32Exception (0x80004005): Unknown error (0xc0000bc6)     at Microsoft.Office.Server.Search.Performance.Pdh.CheckReturnValue(PDH_STATUS status, Boolean throwOnError) 


    At one point in time - we also tried some of the aspects noted here:

    https://vigneshsharepointthoughts.com/2017/02/21/resolving-sorry-this-site-hasnt-been-shared-with-you-sharepoint-site-error/

    Thursday, March 23, 2017 2:19 PM

Answers

  • It doesn't look like you have a Config db issue, but instead an issue with a deployed custom solution.

    For what it's worth, if you did have a corrupt Config db, you'd be looking at building a new farm.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Monday, March 27, 2017 8:48 PM
    Moderator

All replies

  • Hi kmoneill,

    Whether you access all pages or some certain pages to encounter this issue?

    Try to clear the SharePoint Configure Cache to check if the issue exists.

    Please share more detailed ULS log for more information about your issue, ULS log file locate at:

    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS

    Best regards,

    Grace Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Friday, March 24, 2017 9:34 AM
  • Thanks - the issue is very sporatic and some pages display fine at times - while sometimes we get various parsing errors in line with what I posted.

    We've cleared the cache on the farm several times and rebooted each time - we cleared the cache.

    One error we just started seeing was timeouts at times when either of the WFE's is trying to connect to the SQL Database - I'm running SQL Server 2014 BI edition - build 12.00.2000

    An exception of type System.Data.SqlClient.SqlException was thrown.  Additional exception information: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

    System.Data.SqlClient.SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out

       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

       at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)

       at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()

       at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()

       at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()

       at System.Data.SqlClient.TdsParserStateObject.TryReadByteArray(Byte[] buff, Int32 offset, Int32 len, Int32& totalRead)

       at System.Data.SqlClient.TdsParserStateObject.TryReadChar(Char& value)

       at System.Data.SqlClient.TdsParser.TryReadPlpUnicodeCharsChunk(Char[] buff, Int32 offst, Int32 len, TdsParserStateObject stateObj, Int32& charsRead)

       at System.Data.SqlClient.TdsParser.TryReadPlpUnicodeChars(Char[]& buff, Int32 offst, Int32 len, TdsParserStateObject stateObj, Int32& totalCharsRead)

       at System.Data.SqlClient.TdsParser.TryReadSqlStringValue(SqlBuffer value, Byte type, Int32 length, Encoding encoding, Boolean isPlp, TdsParserStateObject stateObj)

       at System.Data.SqlClient.TdsParser.TryReadSqlValue(SqlBuffer value, SqlMetaDataPriv md, Int32 length, TdsParserStateObject stateObj, SqlCommandColumnEncryptionSetting columnEncryptionOverride, String columnName)

    Monday, March 27, 2017 8:07 PM
  • It doesn't look like you have a Config db issue, but instead an issue with a deployed custom solution.

    For what it's worth, if you did have a corrupt Config db, you'd be looking at building a new farm.


    Trevor Seward

    Office Servers and Services MVP



    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Monday, March 27, 2017 8:48 PM
    Moderator