SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Thursday, October 30, 2014

Search Host Controller Stuck on Starting

This can occur during the setting of the new topology for search. In most cases, this can be corrected though it may require deleting the service and starting over. When the Search Host Controller service gets stuck (indicated by 'Starting' under Central Administration > Services on server), it indicates that there's a permissions problem.

Unfortunately, the events in the Event Log are not very telling. As it turns out, it can be a simple fix
First, make sure that the WSS_WPG and WSS_ADMIN_WPG have FULL CONTROL to the drive/folder where the Search indexes will be stored (this means all search servers) and see if that allows it to complete.

If that doesn't work, forcing the provisioning process will work (sometimes) :

$shc = Get-SPServiceInstance | Where {$_.Status -like "Provisioning"}

Note that the above may indicate that the command needs to be run on a different server; simply run the commands on the server indicated by the message.

If neither of the above work, double check permissions (including database permissions) to make sure that the WSS_WPG and WSS_ADMIN_WPG groups have the proper drive/folder access, delete the service that failed (including the DBs!) and try again.

Service Pack 1 update: This can be due to permissions and if the above does not correct it, it may be necessary to delete the service application, stop all search services and start over. First, add the Search Service account to the Local Administrators group on all farm servers and try again. If that does not work, believe it or not, granting the Search Service account "sysadmin" rights in SQL Server may be needed. In both cases, the account permssions can be reduced AFTER search installs properly.

Wednesday, October 29, 2014

Error 1406: Setup cannot write the value to the registry key

When installing a Microsoft Product, for example, Microsoft Office 2013, just about when the install has completed, it pops up an error:

            Error 1406: Setup cannot write the value to the registry key
This as it turns out is quite simple. While the error text tells you to grant permissions to the Registry key, that won't work. Instead, it means setup was started without using "Run as administrator".

To correct, uninstall the package (reboot if necessary) then when starting up Setup.exe, right click and choose 'Run as administrator' - issue solved!

Tuesday, October 28, 2014

Error when starting SharePoint 2013 Management Shell - Method 'Upgrade' in type

Error Starting Management Shell – Method ‘Upgrade’ in type

On opening the SharePoint 2013 Management Shell, an error occurs even though using a Shell Administrator with proper permissions in the database:

Method ‘Upgrade’ in type ‘Microsoft.SharePoint.WorkflowServices.WorkflowServiceApplicationProxy’ from assembly ‘Microsoft.SharePoint.WorkflowService, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ does not have implementation.

This looks something like this:

This error is generated by a missing update, specifically KB2880963. Two methods to fix this is to run Windows Update (making sure you are getting all product updates) or simply download the hotfix from Microsoft:

I suggest simply doing the download - repeated runs of Windows Update still didn't pick it up every time.