Spurious errors when using SQL Server 2005 Performance Dashboard Reports

You might have observed errors when using Performance Dashboard reports that is available (recently) for SQL Server 2005, the error below is mostly ocurred:

Difference of two datetime columns caused overflow at runtime.

Based on the forums & other blogs on the web suggests that 

The fix for that error is to update setup.sql file residing into Performance Dashboard folder: C:\Program Files\Microsoft SQL Server\90\Tools\PerformanceDashboard by editing search in script "procedure MS_PerfDashboard.usp_Main_GetSessionInfo" then replace the code "datediff(mm, login_time, getdate())))" to "datediff(ss, login_time, getdate())))".

If you have got this error during or after the setup then perform above correction then run setup.sql again or if it is during any report viewer then after correcting simply refresh performance_dashboard_main.rdl file too in order to make it work perfectly. To be precise for better explanation ArtfulBlog suggests more detailed correction.

Not only above error there are few others such as:

"The 'version_string' jparameter is missing a value"

"The "Report parameter 'sql_handle' was not found"

"Report parameter 'include_system_processes' was not found

Arithmetic overflow error conferting expression to data type datetime.

Make sure you have applied the service pack 2 for SQL 2005 for the client tools, then you can open the performance_dashboard_main.rdl file with the Custom Reports functionality new to Management Studio in Service Pack 2.  For that Arthimetic overflow error  ensure you have got installed the recent_cpu.rdl & performance_dashboard_main.rdl to call relevant stored procedures.

Recently I was swamped with the following error:

---------------------------------

An error has occurred during report processing.

Cannot read the next data row for the data set SESSION_REQUEST_ACTIVITY.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

---------------------------------

To dig out further I have found that the above error only occurs on a particular client's machine where the language settings are different to the web server. So that means ensure the locale settings matches to the webserver & SQL Server and in this case check that the user you're using to browse the reports has british english as a language.

Lastly don't forget to refer through MakeMostoutofIt post.