Saturday, February 25, 2012

Deployed reports not being overwriting existing reports

Hi,
I am trying to deploy a new set of report to the Reporting server, but these
new versions of the reports do not seem to appear in the Report Manager.
There is no errors reported within VS.Net when deploying. Will it help to
either restart the web server or restart the database server in order to get
the new versions available in the manager.Make sure you are not getting errors from the deployment in VS.NET...
Ensure the deployment target location is correct.
Refresh the IE page, and ensure no page caching is occuring
Try to deploy from the Reporting Services Manager, and see if that is
working for you...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"MicroMoth" <stephen.adams@.forvus.co.uk> wrote in message
news:0F7B9869-E10F-4C10-86A3-343EFDFA38A5@.microsoft.com...
> Hi,
> I am trying to deploy a new set of report to the Reporting server, but
these
> new versions of the reports do not seem to appear in the Report Manager.
> There is no errors reported within VS.Net when deploying. Will it help to
> either restart the web server or restart the database server in order to
get
> the new versions available in the manager.|||You can delete the reports in the Report Manager manually.
If you have the reports moved to subfolders in the report manager. They will
not be replaced. Instead they modified reports are published in the root
folder and the previous versions are remaining in the subfolder.
"Wayne Snyder" wrote:
> Make sure you are not getting errors from the deployment in VS.NET...
> Ensure the deployment target location is correct.
> Refresh the IE page, and ensure no page caching is occuring
> Try to deploy from the Reporting Services Manager, and see if that is
> working for you...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "MicroMoth" <stephen.adams@.forvus.co.uk> wrote in message
> news:0F7B9869-E10F-4C10-86A3-343EFDFA38A5@.microsoft.com...
> > Hi,
> > I am trying to deploy a new set of report to the Reporting server, but
> these
> > new versions of the reports do not seem to appear in the Report Manager.
> > There is no errors reported within VS.Net when deploying. Will it help to
> > either restart the web server or restart the database server in order to
> get
> > the new versions available in the manager.
>
>|||On Wed, 2 Feb 2005 02:41:03 -0800, MicroMoth
<stephen.adams@.forvus.co.uk> wrote:
>Hi,
>I am trying to deploy a new set of report to the Reporting server, but these
>new versions of the reports do not seem to appear in the Report Manager.
>There is no errors reported within VS.Net when deploying. Will it help to
>either restart the web server or restart the database server in order to get
>the new versions available in the manager.
I had this problem, too, when deploying from within VS.NET. Drove me
nuts, until I simply restarted VS.NET IDE.|||Be sure to close IE and reopen it. That has always resolved seeing the most
recent version of a report.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Usenet User" < @. . > wrote in message
news:bfo401tgdsaiobnseo7qt0mpuf4n24bade@.4ax.com...
> On Wed, 2 Feb 2005 02:41:03 -0800, MicroMoth
> <stephen.adams@.forvus.co.uk> wrote:
> >Hi,
> >I am trying to deploy a new set of report to the Reporting server, but
these
> >new versions of the reports do not seem to appear in the Report Manager.
> >There is no errors reported within VS.Net when deploying. Will it help to
> >either restart the web server or restart the database server in order to
get
> >the new versions available in the manager.
>
> I had this problem, too, when deploying from within VS.NET. Drove me
> nuts, until I simply restarted VS.NET IDE.

No comments:

Post a Comment