DPM services fail to start following an upgrade to Windows Server 2016

I had SCDPM 2012 R2 running on Windows Server 2012 R2 with SQL Server 2012.  I followed the instructions here to upgrade to SCDPM 2016 UR 2 running on Windows Server 2016 with SQL Server 2016.

Everything was working fine until the final step to upgrade from Windows Server 2012 R2 to Windows Server 2016.  Following this the DPM services failed to start and the Event Log was full of errors like the below:

System.Exception: -2147023107

ATL Failure in Initializing Security of msdpm

Microsoft.Internal.EnterpriseStorage.Dls.Utils.DlsException: exception —> System.Runtime.InteropServices.COMException: Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))

The resolution was to change the Netlogon service from Manual to Automatic.  Following this change and a reboot everything started working again.

 

Advertisements

SCCM stuck in downloading state

The 1610 update for SCCM had been stuck in the downloading state, with a last update time of three days ago.  There’s a note within the SCCM console that if an update is stuck in the downloading state for a long period of time you should restart the SMS_EXECUTIVE (smsexec) service on the standalone primary or central administration site server (CAS).

I restarted this service, but nothing changed.  The next step was to check dmpdownloader.log, which can be found in C:\Program Files\Microsoft Configuration Manager\Logs.  This contained the error below, where I’ve replaced the proxy and SCCM server name with placeholders.

ERROR: Failed to download redist for 91406b1d-7c14-42d8-a68b-484be5c5e9b8 with command  /RedistUrl http://go.microsoft.com/fwlink/?LinkID=831290 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=831291 /RedistVersion 112015 /ProxyUri http://%PROXYURL%/ /NoUI  “\\%SCCMSERVERNAME%\EasySetupPayload\91406b1d-7c14-42d8-a68b-484be5c5e9b8\redist” .

Looking in the C:\Program Files\Microsoft Configuration Manager\EasySetupPayload\91406b1d-7c14-42d8-a68b-484be5c5e9b8\redist folder, I could see the last modified date was three days ago, equal to the last update time in the console.  I was able to manually download the two CAB files in the above error, so there wasn’t an access issue.  I restarted the SMS_EXECUTIVE (smsexec) service again and this time I could see some more files had been download to the redist folder.  Unfortunately, the update was still listed as downloading.  I restarted the SMS_EXECUTIVE (smsexec) service again, which again resulted in some more files appearing in the redist folder and the update became available.  So the take away from this is that if the update is stuck in a downloading state you may have to restart the SMS_EXECUTIVE (smsexec) service more than once.

Update 14/02/18

Beginning with version 1706 there’s an update reset tool which can be used to fix issues when in-console updates have problems downloading or replicating.  Fore more information see here.

SharePoint 2013 Save Document Library As Template Missing

If you view a document library settings page and “Save document library is a template” is missing try this work around.

Take the document library settings page URL, e.g. http://SharePoint/_layouts/15/listedit.aspx?List=58d3d056… and change listedit.aspx to savetmpl.aspx.  Press enter to load the page and you should be prompted to save the document library as a template.

 

WSUS Integrated With SCCM 2012 R2 Fails To Start

On SCCM 2012 R2 with WSUS integrated for software update deployments I was unable to open the WSUS console.  The WSUS service had stopped and the event log showed event ID 507 Windows Server Update Services, Update Services failed its initialization and stopped.  WSUS is configured to use a SQL database and the SQL Server Logs contained multiple errors for Login failed for user ‘DOMAIN\SCCMSERVERNAME$’. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]

Opening SQL Server Management Studio, I navigated to the SUSDB.  Expanding users showed a user for NT AUTHORITY\NETWORK SERVICE.

SCCMWSUS1

I next opened Security -> Logins and could not see a login for NT AUTHORITY\NETWORK SERVICE.  I added a login for NT AUTHORITY\NETWORK SERVICE and started the WSUS service.  this resolved the problem.

SCCMWSUS2windowwindows

 

Missing Search Results In SharePoint 2013 When Using A Content Enrichment Web Service

Users reported that they couldn’t find a few specific documents when searching within SharePoint 2013.  Checking the crawl log showed documents with the error “The item failed due to an error occurring when sending or receiving data to the external content processing enrichment web service.”  I searched the ULS for one of the effected documents and found the error “System.Net.WebException: The remote server returned an error: (413) Request Entity Too Large.”  Checking the web.config for the content enrichment web service showed the maxReceivedMessageSize value was configured to 8 MB.

TWCEWS0

 

To resolve the error I increased the value of the maxReceivedMessageSize property and re-indexed the document library.

The interesting thing about this case is that the content enrichment web service is designed to add additional metadata to documents.  When the content enrichment web service failed to receive documents over 8 MB the documents didn’t appear within search at all, it wasn’t just the case that they appeared but without the extra metadata.

Dell Firmware Update Fails With “Creation of Dynamic Partition Failed.”

When attempting to run a Dell firmware update you receive the error “Creation of Dynamic Partition Failed.”

DellFWUpdate0

In order to resolve the error reset the Dell iDRAC from the command prompt.  Open a command prompt as administrator and run racadm racreset.

DellFWUpdate1

Once the iDRAC has reset retry the update.

Configure SharePoint 2013 Search Index Managed Property Sizes

If you check the crawl logs for SharePoint 2013 you may see warnings similar to those below:

The item has been truncated in the index because it exceeds the maximum size.

This item was partially parsed. The item has been truncated in the index because it exceeds the maximum size.

This item was truncated because the parsed output was greater than the maximum number of allowed characters.

Microsoft have detailed the SharePoint 2013 Search boundaries and limits here and I’ll show how these boundaries and limits relate to the warnings above.

The item has been truncated in the index because it exceeds the maximum size.

This message relates to the indexed managed property size and according to the aforementioned documentation “This is the default maximum size of a managed property that is set to either “searchable” or “queryable”.”  The property limit can be configured between 0 and 2048KB.

In order to change the limit open an elevated SharePoint 2013 Management Shell.  To get the current property value run the code below.

$p = Get-SPEnterpriseSearchMetadataManagedProperty -Identity body -SearchApplication (Get-SPEnterpriseSearchServiceApplication)
$p.MaxCharactersInPropertyStoreIndex

SMP0

 

To change the property value run the code below, substituting the value for your own requirements.

$prop1 = Get-SPEnterpriseSearchMetadataManagedProperty -Identity body -SearchApplication (Get-SPEnterpriseSearchServiceApplication)
$prop1.MaxCharactersInPropertyStoreIndex = “2048000”
$prop1.Update()

SMP1

 

This item was partially parsed. The item has been truncated in the index because it exceeds the maximum size.

This message  relates to the retrievable managed property size and according to the aforementioned documentation “This is the default maximum size of a retrievable managed property.”  The property limit can be configured between 0 and 2048KB.

In order to change the limit open an elevated SharePoint 2013 Management Shell.  To get the current property value run the code below.

$p = Get-SPEnterpriseSearchMetadataManagedProperty -Identity body -SearchApplication (Get-SPEnterpriseSearchServiceApplication)
$p.MaxCharactersInPropertyStoreForRetrieval

SMP2

 

To change the property value run the code below, substituting the value for your own requirements.

$prop2 = Get-SPEnterpriseSearchMetadataManagedProperty -Identity body -SearchApplication (Get-SPEnterpriseSearchServiceApplication)
$prop2.MaxCharactersInPropertyStoreForRetrieval = “2048000”
$prop2.Update()

SMP3

 

This item was truncated because the parsed output was greater than the maximum number of allowed characters.

This message relates to the parsed content size of the document.  This has a boundary limit of 2 million characters that can’t be increased.  Search stops parsing a document once the limit of 2 million characters has been reached and any content past this point isn’t included in the index.

Once you’ve configured the indexed managed property and retrievable managed property sizes you need to run a full crawl.