Event ID: 8031 – Requested Application Could Not Be Found

While verifying an issue with our local SharePoint instance, noticed in event logs on one of the SharePoint Application servers that one of the Application Endpoints couldn’t be found.

Event ID: 8031 – The request application could not be found.

EventID8031

This is related to an old Service Application that was deleted but didn’t delete all endpoints from all servers in the SharePoint Farm.

To resolve this error, you need to clean up the database for this application.

Open SQL Server where your content database sits.

Write the command into the script:

SELECT ID, Name, Status, Properties
FROM .dbo.Objects
WHERE NAME LIKE ‘%%’
GO

Eg.

SELECT ID, Name, Status, Properties
FROM ContentDB.dbo.Objects
WHERE NAME LIKE ‘%285C%’
GO

Confirm that the name column matches the GUID in the logs.

EventID8031_#1

Run the following script in SQL Server to remove the endpoint from the database:

DELETE *
FROM dbo.Objects
WHERE Name LIKE ‘%285C%’
GO

Perform an IISReset on the affected server.

SharePoint Compatibility Matrix

Recently had a discussion with a colleague as someone tabled migrating our SharePoint 2010 databases to the a newly created SQL Server 2014 cluster. I was like im pretty sure SharePoint 2010 is not supported with SQL Server 2014. After some googling and looking at a million websites, found the answer (its not), and was like why isn’t there a compatibility matrix for SharePoint. Hence this post.

  SharePoint 2010 SharePoint 2013 SharePoint 2016 SharePoint 2019
SQL Server 2005 X(min SP3)      
SQL Server 2008 X(min SP1)      
SQL Server 2008 R2 X X    
SQL Server 2012 X X    
SQL Server 2012 R2   X    
SQL Server 2014   X X(min SP1)  
SQL Server 2016     X X
SQL Server 2017     X X

NP – 64bit versions of SQL Server only.
NPP – SharePoint On-Prem only.

Last Updated – 18th May 2019.

 

CommVault Synthetic Full Issue – SharePoint

Currently backing up a SharePoint Portal of which the database is not even 150GB. The backup isn’t a VM snapshot, but the Application Aware backup which backs up all the SharePoint Lists, Libraries and Sites.

Been running synthetic full backups on this site for the past 18months.

Noticed the last month that it was reporting that the application size was growing rapidly. Like really rapidly and causing the backup to run well over its allocated time.

Jan 2018 1.55TB – 65hours

Apr 2018 2.86TB – 80hours

July 2018 3.55TB – 100hours

Nov 2018 4.13TB – 120hours

Jan 2019 4.29TB – 89hours (with 8 streams running).

Ran a Full backup.
Ran in 9 hours. Total application size was 79GB.

What the synthetic full does, is append any changes to the Full backup (the first full backup file back before Jan 2018). This keeps the physical backup file footprint small.

Running a Full backup instead of Synthetic backup cleaned the ‘slate’.

So the new schedule we have is:
Full backups once a month
Synthetic Full every other Friday night
Incrementals throughout the week.

 

Reading Material:

http://documentation.commvault.com/commvault/v11/article?p=11694.htm

 

Technical Details:

CommVault v11 Service Pack 10.

SharePoint 2010 with March 2018 CU.

Windows Server 2008 R2.

SQL Server 2008 R2.

Certificate Revocation Check

Had an issue recently in a SharePoint Development environment where the SharePoint Web App was taking forever to display its contents.

After some investigation and checking the logs, I noticed that there was a lot of events about Certificates taking longer than normal to process.

The problem occurs in offline environments where the server has no internet access to check the certificate revocation for the .NET assemblies.

The easiest way to fix this issue is to disable the Certificate Revocation Check via the registry.

  1. Click Windows + R and type in REGEDIT.
  2. Navigate to the following location in the registry: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\TrustProvider\Software Publishing
  3. Change the State REG_DWORD to 146944
    CertificateRevocationCheck#1
  4. Click ok.
  5. To enable, change the State REG_DWORD to 146432.

 

 

SharePoint Web Application Not Loading

Last week i encountered an issue where the Web Front Ends were not displaying the main Web Application.

I triple checked all the servers including that the database servers were online, and then proceeded to check if i could access the Central Admin website on the Central Admin server. I then tried to access the Central Admin website from the Web Front Ends and was not able to resolve which means its a DNS issue.

Solution:

The Central Admin server network adapter was set to automatic. Changed it back to static IP Address and performed an IISreset on the Web Front Ends and the Web Application was restored.