Report Manager in SQL Exprtess

I cannot get report manager to load in IE 7 after installing on SQL Express,
advanced edition. The error message is "The ReportServerVirtualDirectory
element is missing". When I check the reporting services configuration file,
there is no XML tag for this (Should there be?). In the reporting services
configuration manager, it shows as not being installed, but when I try to
install, it says it is. It is a little confusing, but basically on the
right-hand side it display a red "X" by report manager, but a green checkmark
on the left-hand side. Note that the report server loads fine in IE 7.On Sep 4, 2:14 pm, Craig Plank, SBS
<CraigPlank...@.discussions.microsoft.com> wrote:
> I cannot get report manager to load in IE 7 after installing on SQL Express,
> advanced edition. The error message is "The ReportServerVirtualDirectory
> element is missing". When I check the reporting services configuration file,
> there is no XML tag for this (Should there be?). In the reporting services
> configuration manager, it shows as not being installed, but when I try to
> install, it says it is. It is a little confusing, but basically on the
> right-hand side it display a red "X" by report manager, but a green checkmark
> on the left-hand side. Note that the report server loads fine in IE 7.
This article might help.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1532003&SiteID=17
Regards,
Enrique Martinez
Sr. Software Consultant

Report Manager error "scale-out deployment not supported in this edition of Reporting Servi

Hi,

I have been trying to get report services installed but another error came:

The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported) (rsRPCError)

This error comes when I try to view either http://localhost/Reports or http://localhost/reportserver

Any suggestions?

thank you.

Can you tell us a little more about what you are trying to accomplish? What version of REporting Services are you trying to install. ARe you trying to set up a webfarm?

Thanks,

|||

I have given up of setting the Reporting Services.

Seems that I am not running the correct SQL version to use reporting services. I have express edition with advanced settings.

Basically I just wanted to run everything on the same computer.

Report in Report Manager (server) does not look the same way that it looks in the Visual Studio

I am using SSRS 2005 and my server is a Microsoft Windows Server 2003 Enterprise Edition Service Pack 1.

Most of the differences between VS and Report Manager are formatting differences. Borders won't show up, scrolling does not work etc. Is there something i need to upgrade on the server.

Last thing but not the least. Everytime i change something in regards to the parameters i need to delete the report from the report manager and deploy in order for the change to appear on the Report Manager. Is there a fix for this?

Could somebody please help me with these?

1. differences in rendering between design-time and run-time -- the renderer used in Report Designer is quite different than the renderer used in Report Manager. The Designer renderer is GDI-based, whereas the Report Manager renderer is HTML-based. There are many differences between these renderers, including handling of overlapping items, borders, and pagination.

2. changes to parameters made at design-time require deletion and republishing -- this is an artifact of our "server wins" philosophy. Since you can change parameter characteristics in the Report Server after a report has been published 9and therefore which may conflict with the characteristics stored in the RDL), it is indeterminate which version of the parameters a user expects to be persisted -- do you expect customizations made after publishing to dominate, or does republishing dominate? We chose to go with the server's version of parameters. Note that if we chose the other way, you would lose server-based parameter customizations everytime you republished an RDL. Admittedly it it would be nice to give users control over this, like with an RDL-based design-time option to choose which parameter collection dominates, or a publish-time option so you could choose one or the other at publish time.

|||You mean there is no way i can reproduce my params changes in the report manager with out deleting the report itself. Everytime i do that it deletes all the subscriptions on my report. Isn't there any work around?|||

Go ahead and republish the RDL, but don't bother making changes to the parameter properties in Report Designer -- just make them directly in the Report Manager or Management Studio UI.

If you need to change the # or name of the parameters, that will have to be done in Report Designer.

Report in Report Manager (server) does not look the same way that it looks in the Visual Stu

I am using SSRS 2005 and my server is a Microsoft Windows Server 2003 Enterprise Edition Service Pack 1.

Most of the differences between VS and Report Manager are formatting differences. Borders won't show up, scrolling does not work etc. Is there something i need to upgrade on the server.

Last thing but not the least. Everytime i change something in regards to the parameters i need to delete the report from the report manager and deploy in order for the change to appear on the Report Manager. Is there a fix for this?

Could somebody please help me with these?

1. differences in rendering between design-time and run-time -- the renderer used in Report Designer is quite different than the renderer used in Report Manager. The Designer renderer is GDI-based, whereas the Report Manager renderer is HTML-based. There are many differences between these renderers, including handling of overlapping items, borders, and pagination.

2. changes to parameters made at design-time require deletion and republishing -- this is an artifact of our "server wins" philosophy. Since you can change parameter characteristics in the Report Server after a report has been published 9and therefore which may conflict with the characteristics stored in the RDL), it is indeterminate which version of the parameters a user expects to be persisted -- do you expect customizations made after publishing to dominate, or does republishing dominate? We chose to go with the server's version of parameters. Note that if we chose the other way, you would lose server-based parameter customizations everytime you republished an RDL. Admittedly it it would be nice to give users control over this, like with an RDL-based design-time option to choose which parameter collection dominates, or a publish-time option so you could choose one or the other at publish time.

|||You mean there is no way i can reproduce my params changes in the report manager with out deleting the report itself. Everytime i do that it deletes all the subscriptions on my report. Isn't there any work around?|||

Go ahead and republish the RDL, but don't bother making changes to the parameter properties in Report Designer -- just make them directly in the Report Manager or Management Studio UI.

If you need to change the # or name of the parameters, that will have to be done in Report Designer.