|
|
You're in the
sql server reporting services
group:RS fails to render a report with changes just made
sql server reporting services:
Scenario: Using VS, I deploy a new version of a report (e.g., change some
text) to ReportServer. When I view the report from the web server using a browser, the report does not show the change. I tried deleting the report from the server, and re-deploying. The new report appears in Reports, with the new datatime stamp, but when it renders, it still renders the OLD version! Eventually, the new report shows up (e.g., hours later). I also tried using a new session of the browser; it makes no difference. I tried using both server\Reports and server\ReportServer. Same behavior on both. I tried setting "report history" on "Site Settings" and on the properties page of the report to 1 (the lowest permitted number). Same behavior. I assume some kind of caching at the server level is the cause, requiring a new setting in the Web.Config or rssrvpolicy.config, but I don't know what those settings might be. I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, and using both IIS5 and IIS6.
"JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... [quoted text, click to view] > Scenario: Using VS, I deploy a new version of a report (e.g., change some > text) to ReportServer. When I view the report from the web server using a > browser, the report does not show the change. > > I tried deleting the report from the server, and re-deploying. The new > report appears in Reports, with the new datatime stamp, but when it > renders, > it still renders the OLD version! Eventually, the new report shows up > (e.g., > hours later). > > I also tried using a new session of the browser; it makes no difference. > > I tried using both server\Reports and server\ReportServer. Same behavior > on > both. > > I tried setting "report history" on "Site Settings" and on the properties > page of the report to 1 (the lowest permitted number). Same behavior. > > I assume some kind of caching at the server level is the cause, requiring > a > new setting in the Web.Config or rssrvpolicy.config, but I don't know what > those settings might be. > > I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, > and using both IIS5 and IIS6. > > Any help will be very much appreciated!
Try reloading the site with STRG+F5 in the browser, if this resolves your
issues, this should be a client side vaching problem. HTH, Jens SUessmeyer. --- http://www.sqlserver2005.de --- "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... [quoted text, click to view] > Scenario: Using VS, I deploy a new version of a report (e.g., change some > text) to ReportServer. When I view the report from the web server using a > browser, the report does not show the change. > > I tried deleting the report from the server, and re-deploying. The new > report appears in Reports, with the new datatime stamp, but when it > renders, > it still renders the OLD version! Eventually, the new report shows up > (e.g., > hours later). > > I also tried using a new session of the browser; it makes no difference. > > I tried using both server\Reports and server\ReportServer. Same behavior > on > both. > > I tried setting "report history" on "Site Settings" and on the properties > page of the report to 1 (the lowest permitted number). Same behavior. > > I assume some kind of caching at the server level is the cause, requiring > a > new setting in the Web.Config or rssrvpolicy.config, but I don't know what > those settings might be. > > I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, > and using both IIS5 and IIS6. > > Any help will be very much appreciated!
When you say you tried to use a new session of the browser what do you mean?
If you close IE and re-open it you should see the new report. I have never not seen a new report (however I have not specified any caching). If you have just taken the defaults when creating a report and have not set any caching option in Report Manager then if you shut IE and re-open it you should see the new report. Also, usually if you change the parameters and run the report you should get the new report. Usually if I click on the refresh of the report (not the IE refresh, you will also get the new report). -- Bruce Loehle-Conger MVP SQL Server Reporting Services "Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote in message news:OrAqjykTFHA.3544@TK2MSFTNGP12.phx.gbl... [quoted text, click to view] > > "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... >> Scenario: Using VS, I deploy a new version of a report (e.g., change some >> text) to ReportServer. When I view the report from the web server using a >> browser, the report does not show the change. >> >> I tried deleting the report from the server, and re-deploying. The new >> report appears in Reports, with the new datatime stamp, but when it >> renders, >> it still renders the OLD version! Eventually, the new report shows up >> (e.g., >> hours later). >> >> I also tried using a new session of the browser; it makes no difference. >> >> I tried using both server\Reports and server\ReportServer. Same behavior >> on >> both. >> >> I tried setting "report history" on "Site Settings" and on the properties >> page of the report to 1 (the lowest permitted number). Same behavior. >> >> I assume some kind of caching at the server level is the cause, requiring >> a >> new setting in the Web.Config or rssrvpolicy.config, but I don't know >> what >> those settings might be. >> >> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, >> and using both IIS5 and IIS6. >> >> Any help will be very much appreciated! > >
You don't have to delete the report. Try just 2 and 3.
-- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "JohnWoll" <JohnWoll@discussions.microsoft.com> wrote in message news:81A637BD-D409-4AD6-9C0E-C55E8334A867@microsoft.com... >I confirmed that only if I do ALL of the following will the change to the > report appear consistently: > 1. Delete the report from Report Server. > 2. Redploy. > 3. Change a parameter. > I can live with that. > > Thanks, Bruce, for the suggestion of changing the parameter! I had tried > that, but not WITH deleting and redeploying. > > "Bruce L-C [MVP]" wrote: > >> When you say you tried to use a new session of the browser what do you >> mean? >> If you close IE and re-open it you should see the new report. I have >> never >> not seen a new report (however I have not specified any caching). If you >> have just taken the defaults when creating a report and have not set any >> caching option in Report Manager then if you shut IE and re-open it you >> should see the new report. Also, usually if you change the parameters and >> run the report you should get the new report. Usually if I click on the >> refresh of the report (not the IE refresh, you will also get the new >> report). >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote >> in >> message news:OrAqjykTFHA.3544@TK2MSFTNGP12.phx.gbl... >> > >> > "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag >> > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... >> >> Scenario: Using VS, I deploy a new version of a report (e.g., change >> >> some >> >> text) to ReportServer. When I view the report from the web server >> >> using a >> >> browser, the report does not show the change. >> >> >> >> I tried deleting the report from the server, and re-deploying. The new >> >> report appears in Reports, with the new datatime stamp, but when it >> >> renders, >> >> it still renders the OLD version! Eventually, the new report shows up >> >> (e.g., >> >> hours later). >> >> >> >> I also tried using a new session of the browser; it makes no >> >> difference. >> >> >> >> I tried using both server\Reports and server\ReportServer. Same >> >> behavior >> >> on >> >> both. >> >> >> >> I tried setting "report history" on "Site Settings" and on the >> >> properties >> >> page of the report to 1 (the lowest permitted number). Same behavior. >> >> >> >> I assume some kind of caching at the server level is the cause, >> >> requiring >> >> a >> >> new setting in the Web.Config or rssrvpolicy.config, but I don't know >> >> what >> >> those settings might be. >> >> >> >> I am using RS SP2, and have duplicated the behavior on both W2K3, and >> >> XP, >> >> and using both IIS5 and IIS6. >> >> >> >> Any help will be very much appreciated! >> > >> > >> >> >>
I think I have eliminated client side issues as the reason.
Please explain what you mean by "Try reloading the site with STRG+F5 in the browser", maybe an example. Thanks for the helping! [quoted text, click to view] "Jens Süßmeyer" wrote:
> Try reloading the site with STRG+F5 in the browser, if this resolves your > issues, this should be a client side vaching problem. > > HTH, Jens SUessmeyer. > > --- > http://www.sqlserver2005.de > --- > > > "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... > > Scenario: Using VS, I deploy a new version of a report (e.g., change some > > text) to ReportServer. When I view the report from the web server using a > > browser, the report does not show the change. > > > > I tried deleting the report from the server, and re-deploying. The new > > report appears in Reports, with the new datatime stamp, but when it > > renders, > > it still renders the OLD version! Eventually, the new report shows up > > (e.g., > > hours later). > > > > I also tried using a new session of the browser; it makes no difference. > > > > I tried using both server\Reports and server\ReportServer. Same behavior > > on > > both. > > > > I tried setting "report history" on "Site Settings" and on the properties > > page of the report to 1 (the lowest permitted number). Same behavior. > > > > I assume some kind of caching at the server level is the cause, requiring > > a > > new setting in the Web.Config or rssrvpolicy.config, but I don't know what > > those settings might be. > > > > I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, > > and using both IIS5 and IIS6. > > > > Any help will be very much appreciated! > >
In answer to what I mean by using a "new session of the browser": I close MS
Internet Explorer, open it, enter the address for Reports, navigate to the report and run it. Here is the exact sequence I use: -Make a change to a report using VS, e.g., change the value of a text box. -Rebuild and redploy to ReportServer -Launch IE, enter the url for Reports, navigate to the report, and the change I made to the textbox value is not there. -I delete the report completely, using Reports web interface. -I rebuild and redploy the report. I close IE, open it again, enter the URL, navigate to the report (which has a new datetime stamp), and run it. The change is still missing! - Changing parameters makes no difference. - I am not using any caching, that I am aware of. I appreciate the help. Let me know what you suggest I do next. [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> When you say you tried to use a new session of the browser what do you mean? > If you close IE and re-open it you should see the new report. I have never > not seen a new report (however I have not specified any caching). If you > have just taken the defaults when creating a report and have not set any > caching option in Report Manager then if you shut IE and re-open it you > should see the new report. Also, usually if you change the parameters and > run the report you should get the new report. Usually if I click on the > refresh of the report (not the IE refresh, you will also get the new > report). > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote in > message news:OrAqjykTFHA.3544@TK2MSFTNGP12.phx.gbl... > > > > "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag > > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... > >> Scenario: Using VS, I deploy a new version of a report (e.g., change some > >> text) to ReportServer. When I view the report from the web server using a > >> browser, the report does not show the change. > >> > >> I tried deleting the report from the server, and re-deploying. The new > >> report appears in Reports, with the new datatime stamp, but when it > >> renders, > >> it still renders the OLD version! Eventually, the new report shows up > >> (e.g., > >> hours later). > >> > >> I also tried using a new session of the browser; it makes no difference. > >> > >> I tried using both server\Reports and server\ReportServer. Same behavior > >> on > >> both. > >> > >> I tried setting "report history" on "Site Settings" and on the properties > >> page of the report to 1 (the lowest permitted number). Same behavior. > >> > >> I assume some kind of caching at the server level is the cause, requiring > >> a > >> new setting in the Web.Config or rssrvpolicy.config, but I don't know > >> what > >> those settings might be. > >> > >> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, > >> and using both IIS5 and IIS6. > >> > >> Any help will be very much appreciated! > > > > > >
I confirmed that only if I do ALL of the following will the change to the
report appear consistently: 1. Delete the report from Report Server. 2. Redploy. 3. Change a parameter. I can live with that. Thanks, Bruce, for the suggestion of changing the parameter! I had tried that, but not WITH deleting and redeploying. [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> When you say you tried to use a new session of the browser what do you mean? > If you close IE and re-open it you should see the new report. I have never > not seen a new report (however I have not specified any caching). If you > have just taken the defaults when creating a report and have not set any > caching option in Report Manager then if you shut IE and re-open it you > should see the new report. Also, usually if you change the parameters and > run the report you should get the new report. Usually if I click on the > refresh of the report (not the IE refresh, you will also get the new > report). > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Jens Süßmeyer" <Jens@Remove_this_For_Contacting.sqlserver2005.de> wrote in > message news:OrAqjykTFHA.3544@TK2MSFTNGP12.phx.gbl... > > > > "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag > > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... > >> Scenario: Using VS, I deploy a new version of a report (e.g., change some > >> text) to ReportServer. When I view the report from the web server using a > >> browser, the report does not show the change. > >> > >> I tried deleting the report from the server, and re-deploying. The new > >> report appears in Reports, with the new datatime stamp, but when it > >> renders, > >> it still renders the OLD version! Eventually, the new report shows up > >> (e.g., > >> hours later). > >> > >> I also tried using a new session of the browser; it makes no difference. > >> > >> I tried using both server\Reports and server\ReportServer. Same behavior > >> on > >> both. > >> > >> I tried setting "report history" on "Site Settings" and on the properties > >> page of the report to 1 (the lowest permitted number). Same behavior. > >> > >> I assume some kind of caching at the server level is the cause, requiring > >> a > >> new setting in the Web.Config or rssrvpolicy.config, but I don't know > >> what > >> those settings might be. > >> > >> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, > >> and using both IIS5 and IIS6. > >> > >> Any help will be very much appreciated! > > > > > >
As well as checking your I.E. settings for caching, you should also check if
the results are being cached at your proxy server. [quoted text, click to view] "JohnWoll" <JohnWoll@discussions.microsoft.com> wrote in message news:045033C0-C950-411C-84B9-934D9FC92F4A@microsoft.com... > I think I have eliminated client side issues as the reason. > > Please explain what you mean by "Try reloading the site with STRG+F5 in the > browser", maybe an example. > > Thanks for the helping! > > "Jens Süßmeyer" wrote: > > > Try reloading the site with STRG+F5 in the browser, if this resolves your > > issues, this should be a client side vaching problem. > > > > HTH, Jens SUessmeyer. > > > > --- > > http://www.sqlserver2005.de > > --- > > > > > > "JohnWoll" <JohnWoll@discussions.microsoft.com> schrieb im Newsbeitrag > > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@microsoft.com... > > > Scenario: Using VS, I deploy a new version of a report (e.g., change some > > > text) to ReportServer. When I view the report from the web server using a > > > browser, the report does not show the change. > > > > > > I tried deleting the report from the server, and re-deploying. The new > > > report appears in Reports, with the new datatime stamp, but when it > > > renders, > > > it still renders the OLD version! Eventually, the new report shows up > > > (e.g., > > > hours later). > > > > > > I also tried using a new session of the browser; it makes no difference. > > > > > > I tried using both server\Reports and server\ReportServer. Same behavior > > > on > > > both. > > > > > > I tried setting "report history" on "Site Settings" and on the properties > > > page of the report to 1 (the lowest permitted number). Same behavior. > > > > > > I assume some kind of caching at the server level is the cause, requiring > > > a > > > new setting in the Web.Config or rssrvpolicy.config, but I don't know what > > > those settings might be. > > > > > > I am using RS SP2, and have duplicated the behavior on both W2K3, and XP, > > > and using both IIS5 and IIS6. > > > > > > Any help will be very much appreciated! > > > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |