Rod,

Based on the above, my understanding is that you can access the reports via the ReportServer URL but not via the Reports URL... is this still the case?

Maybe a shot in the dark, but I had a similar issue not long ago... log into your server and navigate to C:\Windows\Temp and make sure that whatever account the SQL Reporting Services server is running under has full access to that TEMP directory. Basically, whenever you run the nice friendly interface it's building and modifying temporary files in that directory, and if it doesn't have full access it can't do that properly, and it fails.

Aside from that, if you can run the reports via ReportServer and not via Reports, it's almost certainly a web issue (IIS or something) and not an SSRS issue. Someone mentioned the encryption key, but all those really protect is the data sources. If that key was the issue, what you'd be seeing is that you'd be able to navigate the site okay but whenever you tried to actually RUN a report, it'd fail to connect to the data source.

When you try to go to Reports, are you only doing so from your own computer or have you also tried doing so from the server itself? On the server itself, by default, you get more verbose error messages on your screen when something fails.

Take a look in c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager and look for the following section:

<system.diagnostics>

<switches>

<!-- 1 = error, 2 = warning, 3 = info, 4 = verbose -->

<add name="DefaultTraceSwitch" value="3" />

</switches>

</system.diagnostics>

Set the DefaultTraceSwitch value to 4, save the file then restart SQL Reporting Services (best to do this via the SSRS Config Manager) and then try going to your Reports site. The log files should be at c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles