New SSRS 2012 Service Application Fails to Upgrade ReportServer Database

Question

Hi - 
I am in the middle of an SSRS upgrade from 2008R2 to 2012, SP 2010 integrated, without upgrading the database engine. This is on my DEV environment. I am running into problems when I add the new SQL Server Reporting Services Service Application through Central
Administration.  I am keying in the previous db names, so they will be upgraded, "ReportServer". After clicking OK, a screen pops up notifying me that "ReportServer" and "ReportServerTempDB" will be upgraded. So far so good
right? Well as it is processing, it returns with the error found at the bottom:
 The correlationID is nowhere to be found in the ULS Logs. I turned on Verbose logging and still no luck. I have restored the ReportServer database from a backup from 3 days ago and tried again. Same error, different correlation ID, not found
in ULS logs. NOTE: I first encountered a specific permissions error for the service account I was using.  That was nice and descriptive :). Changed the permissions to db_owner and sys_admin (for overkill) and now this non-descriptive error appears.  I
have a few questions:
1. I have gone through the same process of adding a new service application and let a new set of the 3 SSRS db's be created with a different name. But that means I lose all previous subscriptions, data source connections
to the rdls, etc.  Is there a way to port/migrate over the previous ReportServer db contents to the newly created db's? I tried a simple SSIS transfer of each table, and as expected I immediately received FK contraint errors, ID Inserts and so forth.
2. Why wouldn't the correlation ID be showing up with verbose tracking?
3. Does anyone know common reasons why the previous RS databases would not be successfully upgraded???
Thank you for any and all help. I am in the position of being able to roll back to snapshots created Thursday morning of the entire SP farm, but we are now at the point of having consultant work being lost so I am really trying hard to get this upgrade to
be successful and done in our DEV environment.

Answer 1

I restored to a backup of the databases REportServer and ReportServerTempDB that I took last night before I tried to manually update them with writing out the SQL File via Powershell.  I tried to  have the Service Application upgrade the database
again, knowing it would fail, which it did, and am now reviewing the logs in the location you mentioned above.  For the 2 minutes that the failure could have happened during, all I see is OWSTIMER.EXE (0x07CC)   errors, which I'm fairly positive
are unrelated, mainly cause they keep occurring round the clock and a caching error? Again, I am trying to simply find out why the Service Application upgrade the db's and have reverted back to a previous state. I felt the collation errors i was troubleshooting
above were too far down the rabbit hole.
Batch Read on counter \servername\SharePoint Foundation\*\Process ID get 3 instances
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.91 OWSTIMER.EXE (0x07CC)                  
0x1204
SharePoint Foundation         General                      
84yj Medium  
Performance Counter OS (pdh) call failed with error code PDH_CSTATUS_BAD_COUNTERNAME.
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.91 OWSTIMER.EXE (0x07CC)                  
0x1204
SharePoint Foundation         General                      
ff69 Medium  
PDH failure on counter \servername\SharePoint Publishing Cache\\Publishing cache hit ratio with error Unknown error (0xc0000bc0)
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)                  
0x1204
SharePoint Foundation         General                      
563a Medium  
Unable to create system performance counter servername\SharePoint Publishing Cache\Publishing cache hit ratio\.  The following exception was thrown: System.ComponentModel.Win32Exception: Unknown error (0xc0000bc0)     at Microsoft.SharePoint.Win32.SPPdh.CheckReturnValue(PDH_STATUS
status, Boolean throwOnError)     at Microsoft.SharePoint.Utilities.SPPerformanceCounter.Initialize()     at Microsoft.SharePoint.Utilities.SPPerformanceCounter.NextValue(Int32 retry, Int32 retryInterval)     at Microsoft.SharePoint.Utilities.SPPerformanceCounterMonitorInternal.UpdateValue()
    at Microsoft.SharePoint.Utilities.SPPerformanceCounterMonitorInternal.Create(String computer, String category, String counter, String instance)
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)                  
0x1204
SharePoint Foundation         General                      
84yj Medium  
Performance Counter OS (pdh) call failed with error code PDH_CSTATUS_BAD_COUNTERNAME.
1fe34924-470c-42a8-af5d-f60509c31aff
02/08/2014 13:43:00.93 OWSTIMER.EXE (0x07CC)