Thursday, August 22, 2013

Could not find stored procedure dbo.Search_GetRecentStats


In the Event Viewer you will see error messages like;



The SharePoint logs will show:

5586 Critical Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below. Could not find stored procedure 'dbo.Search_GetRecentStats

This error was related to the Search Service Application not being able to write to the usage and health database. Most likely because the usage and health service does not have Health Data collection enabled. Go to central admin and under monitoring select Configure usage and health data collection. Select both the Enable usage data collection and the Enable health data collection


Do an IISRESET and restart the SPTimerV4 service

If these are already on, you need to disable them first then enable them again. Make sure to perform an IISReset and restart the SPTimerV4 service in between.

If you have problems disabling the “ Enable health data collection”, you have to stop some timer jobs.

Open the monitoring – Configure usage and health data collection again and select Health Logging Schedule


Disable the following timer jobs (Diagnostics Data Provider: Performance Counters – Database Servers and UserProfileServices- User Profile to SharePoint Quick Synchronization):


Go to “monitoring” and  “Review job definitions”

Disable this timer job (Health Statistics Updating):


Now you should be able to disable the  “Enable health data collection”



WSS Usage Application proxy stopped on SharePoint 2013



To fix the issue and be able to Start the Usage and Health Data Collection Proxy, run the SharePoint 2013 Management Shell


Check and copy the ID for:


And paste it onto the following command:

$UsageApp = Get-SPServiceApplicationProxy | Where {$_.ID -eq "6fea0336-ad14-4b1e-8e48-df7101c9be0c"}



Check the status in Central Admin – Manage Service Application and the status should be Started now




Saturday, August 10, 2013

Maximum Excel Workbook size when using Office Web Apps 2013

When trying to open a workbook in the browser I got the following error message:


By default, Office Web Apps maximum Excel workbook size = 10 MB

imageTo change the value, you will have to use the following command and define a custom new value for the maximum excel workbook size;


You will have to do an IISRESET on all SP servers to make this change effective

Be aware that if you would like to use Excel Services for rendering your Excel files instead of using Office Web Apps, you would have to suppress the WOPI Binding that is responsible for viewing of Excel files. This is done through PowerShell on a per SharePoint farm basis, it’s not a WAC setting.

PS C:\Users\adm_jgremmen> New-SPWOPISuppressionSetting -extension XLSX -Action View

This command will suppress the WOPI Binding for the extension XLSX (Excel files) and for the WOPI Action View. If we now have Excel Services running in our SharePoint farm then Excel Services will be responsible for viewing Excel (XLSX) files. But Office Web Apps 2013 will be responsible for previews (in search and document libraries) and editing of the files.

You don’t have to do anything else, no IISRESET (this must be the only time you don’t need this for a SharePoint config change!) or anything else.


Verify if Excel files are rendered by Office Web Apps

If you are unsure if Excel files are rendered using WAC or Excel Calc you can easily take a look at the URL. When Office Web Apps is responsible for the rendering the URL will look something like this:
And when Excel Calc is rendering the document it should look like the following:

You can also check the WOPI suppression settings using the Get-SPWOPISuppressionSetting cmdlet if you have shell access to the SharePoint farm.



How to switch back to Office Web Apps rendering the Excel files

Of course you can revert back to using the Office Web Apps for rendering of the Excel files. This is done using the Remove-SPWOPISuppressionSetting cmdlet