Nothing like trying to get a report out for your customer only to find your recent upgrade to R2 has broken all the reports! Time to investigate.

Reports were giving out the following error or similar when accessed:

‘An error has occurred during report processing. (rsProcessingAborted)
Cannot read the next data row for the dataset Parameter_DataSet_Baseline. (rsErrorReadingNextDataRow)
Conversion failed when converting the nvarchar value ‘**********’ to data type int.’

It’s suggested that a removal of the Reporting Point will resolve the problem. Remove the role, wait 15 minutes and then re-install.

Well that might just work for you, however in this instance the reports just displayed the same error post installation.

On inspection the reporting services log file, srsrp.log, was reporting the following:

Invalid class SMS_SRS_REPORTING_POINT
Could not retrieve the reporting service name for instance ‘MSSQLSERVER’ SMS_SRS_REPORTING_POINT
Invalid class SMS_SRS_REPORTING_POINT
Could not stop the reporting service ” SMS_SRS_REPORTING_POINT

The fix was to run the following command to re-register the SQL management Provider WMI class:

mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”

Bear in mind that the above command is for SQL Server 2008 and it assumes that SQL is installed in its default location.

The command for SQL Server 2012 is:

mofcomp.exe “C:\Program Files (x86)\Microsoft SQL Server\110\Shared\sqlmgmproviderxpsp2up.mof”

Watching the srsrp.log file in CMTrace, the reports re-deployed over the next 5 minutes and were available to view.

Problem solved!

Advertisements