Critical, Unexpected, Warnings and Monitorable errors in the SharePoint 2013 ULS logs

Recently I wrote a PowerShell script to collect all Critical, Unexpected and Monitorable messages in the ULS logs.

SharePoint ULS logs

With this script I’m creating an item in a SharePoint list. Gosh this does create a lot of items. Things I wasn’t aware of are now visible. I thought that we had quite a healthy SharePoint 2013 farm.

If you are interested in the script then please contact me or you can now download it from codeplex at https://github.com/Pieter-Veenstra/ULS-Monitor.

I have now installed ULSMonitor at some of my customers. If you want me to help you too then please get in touch.

First what do all the different levels mean:

Unexpected

These are the error that should not really happen. Something has gone wrong and some code is not handling the specific error. So this looks a bit like

try

{

… Some dodgy code …

}

catch (Exception ex)

{

… Log error ex in the ULS logs …

}

So a catch all is collecting all errors rather than specific errors being handled.

Critical

Something has gone wrong. Microsoft knows about this and the code is reporting this issue to you. Something should be done by a system administrator.

Warning

The health Analyser has found an issue (e.g. running out of disk space soon but not yet). In general you shouldn’t leave these issues there.

Monitorable

Something is happening but it’s not always clear what has gone wrong.

The errors I found so far

A lot of the below errors I might not have a solution for so if you have the same error and you do have a solution then please feel free to contact me and I will update this blog. I will update this blog as I go along fixing the issues.

Critical 1

The SharePoint Health Analyzer detected an error. Drives are running out of free space. Available drive space is less than twice the value of physical memory. This is dangerous because it does not provide enough room for a full memory dump with continued operation. It also could cause problems with the Virtual Memory swap file: OS (SPHOST – C:\), LOGS (SPHOST – E:\). Examine the failing servers and delete old logs or free space on the drives. For more information about this rule, see “http://go.microsoft.com/fwlink/?LinkID=142688”.

Issue: SharePoint wants to have enough spare disk space is case of a system crash.

Solution: In our case we have disabled memory dumps to be written to the disks mentioned however SharePoint still sees the lack of disk space as a critical issue.

Critical 2

Table SPDistributedCacheCalls_Partition14 has 461012992 bytes that has exceeded the max bytes 460175067

Issue: Too much unnecessary usage data.

Solution: http://stevemannspath.blogspot.co.uk/2013/04/sharepoint-2013-sql-partition-exceeded.html

Critical 3

Unknown SQL Exception 53 occurred. Additional error information from SQL Server is included below. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server)

Issue: Unknown

Solution: Unknown. Related articles found:

http://jakejacobsen.net/2010/01/06/sharepoint-configuration-wizard-failing-with-sql-exception-a-number-of-possible-fixes/

Critical 4

A certificate validation operation took 15002.4863 milliseconds and has exceeded the execution time threshold. If this continues to occur, it may represent a configuration issue. Please see http://go.microsoft.com/fwlink/?LinkId=246987 for more details.

Solution: For this problem I decided to create a separate post

Unexpected 1

SPReaderWriterLock named [SPInitializeOnceLock] held for 3166 milliseconds. Call stack: at Microsoft.SharePoint.Utilities.SPReaderWriterLock.SPReaderWriterLockScope.Dispose() at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.get_ReferencedAssemblies() at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.SubCompiler.AddReferenceableAssemblies(WorkflowCompilerParameters theParameters) at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.SubCompiler.DoCompile(WorkflowCompilerParameters parameters, String xomlSource, String assemblyName, CompilationPacket& packet, DirectoryInfo& tempDir)

Read more about SPReaderWriterLock

Unexpected 2

An SPPerformanceCounter was not properly disposed. This could cause excessive memory use.

Issue: An SPSite, SP Web or any other object that needs to be disposed isn’t disposed properly. Check your code and make sure that everything is cleaned up properly before the garbage collection kicks in.

Solution: https://msdn.microsoft.com/en-us/library/aa973248(v=office.12).aspx

Unexpected 3

the User profile service returns the following unexpected errors:

ActivityManager.ProcessUserPostCollection (Setting Current User), AccountName:{0}, Exception: {1}.

SPSocialFeedManager.ProcessUserPost: Exception: Microsoft.Office.Server.UserProfiles.SocialDataStoreException: PersonalSiteNotFound : Personal site does not exist. at Microsoft.Office.Server.UserProfiles.SPS2SAppUtility.GetPersonalUrl(UserProfile& profile) at Microsoft.Office.Server.UserProfiles.SPS2SAppExecutionContext.InitializeForProfile() at Microsoft.Office.Server.UserProfiles.SPS2SAppExecutionContext.EnsureInitialized() at Microsoft.Office.Server.Social.SPSocialFeedManager.S2SInvokeWithTrustedFeedManager(String name, UserProfile profile, SPServiceContext serviceContext, Action`1 func)

Issue: Unknown

Solution: Unknown