SSRS content not appearing in SharePoint 2013

Question

We have a multi-sever installation of SharePoint 2013 SP1 we are trying to get working for BI environment.
We have most features working, including Kerberos delegation of user credentials in PerformancePoint and Excel Services.  However, we are having issues getting SSRS (SharePoint Integrated) working in our multi-server solution.  These reports work
fine in our single-server Development environment, but when we deploy them to the scaled-out SharePoint farm, the reports become non-functional. 
We can see the breadcrumb header for the current report folder, and also see the control pane that gives us a list of available actions, and the navigation controls, but everything else is empty.  The navigation controls are never populated with information,
and the entire screen below remains blank white.  No error is visible.
Our configuration uses 4 servers.  Server (A) is the front-end SharePoint server; Server (B) is the back-end application server [which also hosts the Central Admin site]; Server (C) hosts all the SQL databases; and Server (D) is
dedicated to SQL Analysis Services.  We have installed SQL Reporting Services (SharePoint Integrated) on Server (B), and have also installed the Reporting Services Add-In for SharePoint on server (A).  We are using SQL 2012 for all SQL functions,
and SP 2013 SP1. 
Can anyone provide any assistance on where else I can look, or what I may be missing to get this configuration working?
Thanks in advance,
Elohir

Answer 1

Hi Trevor,
I hope you are still monitoring this thread, as I had a bit of an epiphany overnight, and think I know what the core of my issue is, but still have no idea how to resolve or work-around it.
So it occurred to me, that since Reporting Services was installed with the CA site on the SharePoint Application server (Server B, which we'll call ca.mysite.com), and the BI Web Application itself is installed on the WFE (Server A, or bi.mysite.com), any
call to a constructed URL would have one of two issues:
A constructed URL of http://bi.mysite.com/reports would be sent to Server A, where only the RS Add-In is installed, not SSRS itself, so no response would be expected, since there is no SSRS service to respond.
A constructed URL of http://ca.mysite.com/reports would be sent to Server B.  However, since that is where the CA site, and service applications live, the SPN for Kerberos is mapped to the CA Web Application
Account, and not the AD account used for the SharePoint services.  Now calls to port 32843 on this box should map to the correct SPN, but without that port in the URL, it is going to fail Kerberos authentication.
So this also raises an interesting question about configuring SharePoint services with Kerberos.  Fortunately, our design plan called for a single AD account to be used for all service application pools.  So no matter which service is being called
on the application server via the 32483 default service port, they all map to the same service account, and thus the same SPN (since they all use the same root URL).  So my question becomes, if we had decided to use DIFFERENT accounts for the service
applications, how would we configure everything so that each service could support a unique SPN?  Is there a way to tell/force SharePoint to use a specific URL for the Reporting Services connections?
So if Trevor, or anyone else has made it this far, does it sound like I am on the right track here?  Any suggestions or recommendations would be appreciated... I feel like I am beating my head against a wall.
Thanks in advance,
Elohir