SharePoint Products Configuration Wizard Fails

Trying to run config wizard after installing CU or SP updates and get failure in SharePoint Products Configuration Wizard:

Make sure the DefaultAppPool is running v2.0 .NET Framework in IIS Manager.

Schedule Powershell Script

1. Write your PowerShell Script (Myscript.ps1)
2. Save it to a location
3. Go into Windows Sheduler and shedule your script

In Task Scheduler put in program/script: powershell (C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe)
And in arguments -Command "<path to .ps1 script>"
(-Command "C:\Powershell\Testing.ps1")
If you don't want change current execution policy permanently then use -ExecutionPolicy Bypass
All will look like this: powershell -Command "<path to .ps1 script>" -ExecutionPolicy Bypass

SharePoint 2010: Usage files are not deleted, causing timer service problems

The .usage logs are never deleted. There should typically be no more than 6 .usage files at any given time, but when you have this problem, you may find hundreds or thousands of usage logs in the logging directory.

You'll see errors like this in the SharePoint ULS logs when the Usage Import timer job runs:


OWSTIMER.EXE (0x51A0) 0x59E4 SharePoint Foundation Usage Infrastructure a5rv High Failed to delete usage log file 'E:\Logs\ServerName-20130701-2117.usage' after data import. Exception: System.IO.IOException: The process cannot access the file because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileInfo.MoveTo(String destFileName) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.MoveFileOrDirectory(FileSystemInfo fi, String newPath) at Microsoft.SharePoint.Administration.SPProvisioningAssistant.DeleteFileOrDirectory(FileSystemInfo fi) at Microsoft.SharePoint.Administration.SPUsageLogImporter.ImportUsageLogFiles(List`1 usageLogFileList)

This happens when Windows updates KB 2775511 or KB 2682011 or KB 2882822 are applied to the SharePoint servers.

The fix is in the December 2013 Cumulative Update for SharePoint 2010.  

If you look at the description for the Foundation package (which is included in the SharePoint server package) here: http://support.microsoft.com/kb/2849981, you will see this description for one of the issues that are fixed:

"After you install hotfix 2775511 or hotfix 2682011 on a SharePoint Server 2010 server, the Usage Provider (.usage) files are not deleted from the file system. Additionally, the .usage files keep growing."

This is a somewhat generic summarization of the problem that does not include all the known symptoms, but it does fix the issues described in this KB.

Here is the link to the KB and download:
http://support.microsoft.com/kb/2849971

In case you cannot quickly install the December 2013 Cumulative Update, there are two independent workarounds that should get you by until you can:
Set up a scheduled task to manually recycle the timer service (at least) once a day -- every 6 hours would be better.  You can use a PowerShell command like this to recycle the service:  

restart-service -Name SPTimerV4

Then you just need to set up a scheduled task to run it every 6 hours on every SharePoint server in the farm.  When the timer service is manually recycled, the open handles to the .usage files are released, and they will be automatically deleted when the next instance of the Usage Data Import timer job runs (by default every 30 minutes).  There should be no need to manually delete the files. 

Datasheet View in IE not working

Datasheet View "disabled" or not working in SharePoint 2010.

Resolution: IE was running 64 bit version.  You must be running the 32 bit version.

User Profile Pictures in SharePoint

-Pictures being synced from Active Directory can’t be bigger than 10 KB in size.

-If they come in with just a GUI as the name (in the Profile Picture library of the mysites site collection) from the sync and won’t match up to users correctly run this powershell cmd:

Update-SPProfilePhotoStore -CreateThumbnailsForImportedPhotos 1 -MySiteHostLocation http://mysites/

SharePoint 2013 New Install Missing Server Side Dependencies

I recently performed a clean installation of SharePoint 2013 and immediately noticed the Health Analyzer had detected an error stating:

Missing server side dependencies.
[MissingWebPart] WebPart class [28c23aec-2537-68b3-43b6-845b13cea19f] is referenced [5] times in the database [SharePoint_AdminContent_<GUID>], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [SharePoint_AdminContent_<GUID>], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
SPTimerService (SPTimerV4)

To determine which pages rely upon this suspect Web Part, execute the below query in SQL Server Management Studio while logged into your SharePoint database server.

use [SharePoint_AdminContent_(guid)]

select DirName, LeafName

from dbo.AllDocs

where id in

(select tp_PageUrlID

from dbo.AllWebParts

where lower(tp_WebPartTypeId) = '28c23aec-2537-68b3-43b6-845b13cea19f')

Here we use the database SharePoint_AdminContent_<GUID> since it is the one referenced in the error. Nevertheless, two pages should be returned:

1. SearchAdministration.aspx
2. SearchFarmDashBoard.aspx

Given the results, navigate to both pages by concatenating them with the Central Administration URL.  You can ignore any error you may received since they may not be configured yet.
 1.http://[centraladmin:port]/SearchAdministration.aspx
 2.http://[centraladmin:port]/SearchFarmDashBoard.aspx

Now, return to the Central Administration Site main page and again click ‘View these issues’ produced by SharePoint Health Analyzer.  There open the error once more and click ‘Reanalyze Now’ from the ribbon.  When it is complete, return to the Central Administration Site main page, re-open the issues and this error should no longer exist.  If it does, wait momentarily and it should be removed.
Reference Article

GetWorkflowConstants expects parameter @IsWebAdmin

Email notifications in Nintex workflow were erroring out with this comment:
Failed to send notification. Procedure or function 'GetWorkflowConstants' expects parameter '@IsWebAdmin', which was not supplied.

These errors started happening out of no where (at least that we knew of), workflow hadn't changed and no modifications to system that we knew of.  This article mentioned after a new version was installed this happened.  Restarted SharePoint Timer server and workflows started working again.

SharePoint 2010 Search Error

In ULS Viewer getting error:
Illegal operation attempted on a registry key that has been marked for deletion.

Can't search in Web App get this error:

Resolve by:
1. Stopped/Started the SecurityTokenService application pool in IIS on all servers in the farm
2. Stopped/Started the Search Query and Site Settings Service on all the servers in the farm that query happens on (in Central Admin, Manage Services on Server)
That fixed it for me

Related Article