Reports not working after upgrade to SCCM 2012 R2 -

Question

I am having the same issue described in this post:
http://social.technet.microsoft.com/Forums/en-US/30f185ac-c34e-44ad-87eb-7d180a0d76b8/after-2012-r2-upgrade-some-sql-queries-wont-run?forum=configmanagergeneral
When running reports after upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2 I get the following error:
An
error has occurred during report processing. (rsProcessingAborted)
Cannot
read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
Conversion
failed when converting the nvarchar value
'S-1-5-21-1010966800-777871707-395339515-124623' to data type int.
I have removed the Reporting Services Point and reinstalled it with no effect.  All reports I try get the error listed above.
Any suggestions?

Answer 1

The issue has been resolved.  For anyone experiencing a similar issue I will post the fix that worked for us below:
I ended up opening a PSS case and in this instance the problem was the required SQL management provider was not properly registered in WMI, which ultimately meant the reporting point upgrade/install was not able to complete successfully after the upgrade. 
As a result the updated reports were not properly being redeployed to the Reporting Service Point.
To diagnose this on the Reporting Service Point look in the srsrp.log for entries indicating of an
Invalid Class, as seen in the example below:
Invalid class SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Could not retrieve the reporting service name for instance 'RPSERVER' SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Invalid class SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Could not stop the reporting service '' SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Next security configuration at [11/6/2013 5:52:12 PM] SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Root Folder exists SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Successfully checked that the SRS web service is healthy on server SERVERRP.AD.DOMAIN SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Registry change SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
SRSRP registry key change notification triggered. SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Registry change SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Timed Out... SMS_SRS_REPORTING_POINT 11/6/2013 5:48:13 PM 6096 (0x17D0)
The important part is the lines saying Invalid Class and then it timing out, so the RP installation was not completed.
As mentioned earlier the WMI class that was missing or corrupt was the SQL management Provider.  To re-register the class we need to compile the MOF file that is available in SQL.  In our instance the command to run was:
mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
Once that was done, monitoring the srsrp.log shows that it could properly detect the SSRS service, stop it and start coping the updated reports and such.  After a few minutes the deploy completed, and all the broken reports started working
correctly.
Hope that helps someone else.