Securitytoken.svc
Exception: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it [::1]:32843
Solution:
On Task 2 of PSConfig, perform an IISReset. Check in IIS if the “SharePoint Web Services Root” application pool is started
CTypes Feature
Feature upgrade action ‘AddContentTypeField’ threw an exception upgrading Feature ‘CTypes’ (Id: 15/’00000000-a48b-4a8e-8ea5-26ea7fc1d162′) in Site ‘https://contoso.com’: The object has been updated by another user since it was last fetched.….
Solution:
Check the Columns on site for any conflicts. Rename if found.
Site Settings > Site Content Types > look for conflicting names/types, rename.
If none found, Disable CType feature and then Re-Enable CType feature.
Disable-SPFeature -identity ‘CTypes’ -URL ‘https://contoso.com’
Enable-SPFeature -identity ‘CTypes’ -URL ‘https://contoso.com’
Database Grow Failed
Attempt PSConfig/Update again, if this becomes a blocking issue then manually grow the MDF and LDF files a 100mb+ directly from SQL Server. Also recommend evaluating growth settings and make sure not % or 1mb.Issue: Attempt to register null pointer at:
Attempt to register null pointer at: at Microsoft.SharePoint.Upgrade.SPHierarchyManager.AddNextLevelObjects(Object current, IEnumerable nextObjects)…..
INFO SPWebApplication Name=Contoso 00000000-0000-0000-0000-000000000000
ERROR Attempt to register null pointer at: …….
Clue: Null pointer is not reporting any details and is blank.
Solution:
You have an Orphan content database
Requires discovery to identify where this might be.
View each Site Collection in Central Admin to make sure they return URL and DB name.
Worst case, detach each content database 1 at a time and attempt to re-attach.
If you locate an issue with a database this may be your issue.
This gets more complicated when it is a service application. You will have to find documentation on how to handle each service application.
Alternative when nothing seems to be working.
Note: Microsoft has guidance against running queries against SharePoint databases.
SELECT TOP [Id],[ClassId],[ParentId],[Name],[Status],[Version],cast([Properties] as XML)
FROM [SharePoint_Config].[dbo].[Objects] (nolock) where Id = '<Guid of the Web Application>'
Click on the XML link form top SQL Statement and look for <fld type=”null” />.
Click on the XML link form top SQL Statement and look for <fld type=”null” />.
This tells you that the issue is with this database, 00000000-6581-4314-90bd-a00f3efe18e3
Now with PowerShell,
$wa = Get-SPWebApplication -Identity https://contoso.com
$wa.ContentDatabases.Delete(“0000000-6581-4314-90bd-a00f3efe18e3”)
You may see errors, but this normally will clear up the issues anyway. Double Check by re-running the SQL statement above and view the XML and see if the information no longer has any null values.
Problem Connecting or service starting and stopping
Inner Exception: Unable to connect to the remote server
An exception was encountered when trying to start service W3SVC
The process C:\Windows\system32\IISReset.exe exited with return code 1052
An exception was encountered when trying to stop service SPTimerV4
Solution:
Verify IIS Admin Service, SharePoint Admin Service, SharePoint Timer Service, World Wide Web Server Service are started on all servers and not disabled Prior to PSConfig.
net start IISADMIN
net start W3SVC
net start SPTraceV4
net start SPWriterV4
net start SPAdminV4
net start SPTimerV4
If similar occurs during the PSConfig after Step 5,
Verify IIS Admin Service, SharePoint Admin Service, SharePoint Timer Service, World Wide Web Server Service are started on all servers and not disabled on Step 5 during PSConfig.
net start IISADMIN
net start W3SVC
net start SPTraceV4
net start SPWriterV4
net start SPAdminV4
net start SPTimerV4
IIS CanUpgrade Failed
ERROR CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.
Solution:
Review IIS Sites, in this case, it was attempting to connect to existing sites to see if they match the environment. Turned out there was a temp site that was no longer working and gave error not able to find virtual directory. Removed site from IIS, PSconfig was able to continue.
