Report Startup Options

Is there a way to stop a report from loading on open?

When we have reports with defaults set, the report loads on open. We would like it to wait until the "View Report" button is pressed.

I had thought I could set a hidden parameter that would be set to false originally and then to true once the View Report button is pressed. I cannot see where I could custom code an event to update this parameter.

SQL Server 2005

Thanks!

Brian

Not with the Report Manager viewer. If this is a custom application, you can supress the parameter prompt area and control loading of the report programatically.

Report Server Configuration Issues!

I am attemping to configure Reporting Services on my fresh SQL Server 2005 install. I am literally setting all the defaults for the virtual dirs, identities etc. But when I get to Database Setup, I again pick the defaults, and click New.

It creates the DBs fine, but then asks me whether I want to upgrade the DB, which I find amazing seeing as this is a fresh install.

If I click No and move onto Initialization, then the app tells me there was an error switching panels, and says:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the report server database and verify access rights. (rsInvalidReportServerDatabase).

If I click Yes, it attempts to update the database (that it just created!), and bombs out with the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: The version does not match a supported version.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseUpgradeScript(String databaseName, String serverVersion, String& script)

Does anybody have any ideas on this one? It seems like a authentication issue, but surely if it created the database, it should then have given itself some rights to use it!

This has been driving me up the wall, so all help is very much appreciated :)

I get the same behaviour!? (Upgrade from SQLServer 2000 -> 2005, then installed ReportServer)

Any fixes/solutions yet?