Does this look familiar? If so, check out this blog post. If not, move along, nothing to see here….


Kevin Holman blogged on this topic at:

The following is a subset from Kevin’s blog post:

“When you try and run the report ‘Performance By Utilization’ you get an error:

An error has occurred during Report Processing.

Query execution failed for dataset ‘PerfDS’.

Procedure or function Microsoft_SystemCenter_Report_Performance_By_Utilization has too many arguments specified.

On a reporting server without remote errors enabled – you might only see the top two lines in the error above.  I recommend enabling remote errors on you reporting server so the report output will show you the full details of the error:   How to Enable Remote errors on SQL reporting server

If you are getting the “too many arguments specified” error, this is caused by the Windows 2003 MP.  It also contains the stored procedure definition for Microsoft_SystemCenter_Report_Performace_By_Utilization, however the definition in the Windows 2003 MP is missing the “@DataAggregation INT,” variable.  Depending on the MP import process, it is possible that the stored procedure from the will not be deployed, which does contain this variable.  In order to resolve this issue – we need to modify the existing stored procedure, and add the “@DataAggregation INT,” line just below the “Alter procedure” line.  Ensure you back up your Data Warehouse database FIRST, and if you are not comfortable editing stored procedures, open a case with Microsoft on this issue.  An alternative, is to use the SCOM Authoring console, open the file, go to reporting, Data Warehouse Scripts, Microsoft.Windows.Server.Reports.PerformancebyUtilization.Script properties, Install tab, and copy the actual script.  You can run this script in a SQL query window targeting your DW database, and it will create/modify your sproc.

The above instructions ONLY cover the SPECIFIC “Too many arguments” error.  If you are getting ANY OTHER error, the above method will not resolve your issue and you should open a case for resolution.”

Marnix Wolf also has an article on this topic (including specific steps to change the stored procedure) at: