So when I run the report in the Report Manager, everything is all good. When
I run it in a webform using report viewer for vs.net 2005 the view reports
this error.
"The permissions granted to the user 'NT AUTHORITY\NETWORK SERVICE' are
insufficient for performing this operation(rsAccessDenied)"
What interesting when RS2005 install on XP Professional setting for
webservice identity shows ASPNET and reports work on that machine in report
viewer control. But when running on Windows 2003 Server, it uses default pool
and NETWORK SERVICE ACCOUNT by default which I think is the problem. Any idea
or anyone run into this.Curious if anyone now the bare minimum to run 2005 report in a webform.aspx
using report viewer. ASPNET was enough on XP Pro runnng RS2005 locally. But
it's different on a Server. This is obviously a good thing, wondered how I
can find the bare minimum without assigning Everyone as I discovered fixed
the problem below:
Well thought post the hack on this one. So what I ended testing and showed
success, in report manager I temporarily aded new role, "Everyone" with
browse only rights on the Home directory security roles in report manager,
now the report loads.
----
I would like to let people now, we where in a crunch to get it working, but
would love to hear how RS2005 has maybe been change to use forms
authentication or some solution for people that now danger running ASPNET
identity to access sensitive data, but have their surround website secured.
---
So my next step:
1) revert securty at Home level on report manager to only Administrator role.
2) add folder for reports and deploy the reports to the new folder on the
report server
3) use seperate permissions on folder then the home root. For newbie, you do
this by clicking on the folder in report manager, click properties and
security. Then use new role and choose yes to warning that you want these
roles seperate from home security. This allows the report to run in our
webform.aspx as the website is protect with form authentications.
"Rob G" wrote:
> So when I run the report in the Report Manager, everything is all good. When
> I run it in a webform using report viewer for vs.net 2005 the view reports
> this error.
> "The permissions granted to the user 'NT AUTHORITY\NETWORK SERVICE' are
> insufficient for performing this operation(rsAccessDenied)"
> What interesting when RS2005 install on XP Professional setting for
> webservice identity shows ASPNET and reports work on that machine in report
> viewer control. But when running on Windows 2003 Server, it uses default pool
> and NETWORK SERVICE ACCOUNT by default which I think is the problem. Any idea
> or anyone run into this.
>|||When you were developing before (everything on one machine) you were the
administrator on the machine and that is why everything worked. What I do is
have a local group, I add domain users and groups to that (for instance add
a group called Reports). Give them browse rights at home. The other folders
will inherit. In most cases all the users have rights to all the folders. If
not, change for the specific folder.
You definitely do not want to do anonymous.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rob G" <RobG@.discussions.microsoft.com> wrote in message
news:2C5D679B-E5CD-4ECF-8F44-00E47F5DAB3E@.microsoft.com...
> Curious if anyone now the bare minimum to run 2005 report in a
> webform.aspx
> using report viewer. ASPNET was enough on XP Pro runnng RS2005 locally.
> But
> it's different on a Server. This is obviously a good thing, wondered how I
> can find the bare minimum without assigning Everyone as I discovered fixed
> the problem below:
> Well thought post the hack on this one. So what I ended testing and showed
> success, in report manager I temporarily aded new role, "Everyone" with
> browse only rights on the Home directory security roles in report manager,
> now the report loads.
> ----
> I would like to let people now, we where in a crunch to get it working,
> but
> would love to hear how RS2005 has maybe been change to use forms
> authentication or some solution for people that now danger running ASPNET
> identity to access sensitive data, but have their surround website
> secured.
> ---
> So my next step:
> 1) revert securty at Home level on report manager to only Administrator
> role.
> 2) add folder for reports and deploy the reports to the new folder on the
> report server
> 3) use seperate permissions on folder then the home root. For newbie, you
> do
> this by clicking on the folder in report manager, click properties and
> security. Then use new role and choose yes to warning that you want these
> roles seperate from home security. This allows the report to run in our
> webform.aspx as the website is protect with form authentications.
>
>
> "Rob G" wrote:
>> So when I run the report in the Report Manager, everything is all good.
>> When
>> I run it in a webform using report viewer for vs.net 2005 the view
>> reports
>> this error.
>> "The permissions granted to the user 'NT AUTHORITY\NETWORK SERVICE' are
>> insufficient for performing this operation(rsAccessDenied)"
>> What interesting when RS2005 install on XP Professional setting for
>> webservice identity shows ASPNET and reports work on that machine in
>> report
>> viewer control. But when running on Windows 2003 Server, it uses default
>> pool
>> and NETWORK SERVICE ACCOUNT by default which I think is the problem. Any
>> idea
>> or anyone run into this.
>>
Showing posts with label view. Show all posts
Showing posts with label view. Show all posts
Wednesday, March 21, 2012
Tuesday, March 20, 2012
rs:SessionID= does not work
I want to render a PDF report and view the copy of the report in the HTML
viewer. What I did is to use rs.Render(...) to get the PDF report and the
SessionID, and then pass the SessionID to the URL string and run the URL.
But the rs:SessionID=xxxxx command does not work, it alway create a new
session for the report.
This part of the code works fine to generate a PDF file for me and save a
session id in m_SessionID:
byte[] results = null;
string historyID = null;
string devInfo = @."<DeviceInfo><Toolbar>False</Toolbar></DeviceInfo>";
SessionHeader sh = new SessionHeader();
rs.SessionHeaderValue = sh;
results = rs.Render(
this.ReportConfig.ReportName,
"PDF",
historyID,
devInfo,
parameters,
credentials,
showHideToggle, out encoding, out mimeType, out
reportHistoryParameters,
out warnings,
out streamIDs);
m_SessionID = rs.SessionHeaderValue.SessionId;
But when I use the generated sesionid for the URL access like this:
url = "http://guoxp.softbrandsamer.com/reportserver?%2fInvItmb&rs:Command=Render&r
s:SessionID=" + m_SessionID
it will create a new instance. And when I looked at the SessionData table in
the ReportServerTempDB, a new session is created.
How to make it work? Please help. Thanks,
LianghongDid you ever find a work around for this. It doesn't seem to be working for
me either.
"Guo, Lianghong" wrote:
> I want to render a PDF report and view the copy of the report in the HTML
> viewer. What I did is to use rs.Render(...) to get the PDF report and the
> SessionID, and then pass the SessionID to the URL string and run the URL.
> But the rs:SessionID=xxxxx command does not work, it alway create a new
> session for the report.
> This part of the code works fine to generate a PDF file for me and save a
> session id in m_SessionID:
> byte[] results = null;
> string historyID = null;
> string devInfo = @."<DeviceInfo><Toolbar>False</Toolbar></DeviceInfo>";
> SessionHeader sh = new SessionHeader();
> rs.SessionHeaderValue = sh;
> results = rs.Render(
> this.ReportConfig.ReportName,
> "PDF",
> historyID,
> devInfo,
> parameters,
> credentials,
> showHideToggle, out encoding, out mimeType, out
> reportHistoryParameters,
> out warnings,
> out streamIDs);
> m_SessionID = rs.SessionHeaderValue.SessionId;
> But when I use the generated sesionid for the URL access like this:
> url => "http://guoxp.softbrandsamer.com/reportserver?%2fInvItmb&rs:Command=Render&r
> s:SessionID=" + m_SessionID
> it will create a new instance. And when I looked at the SessionData table in
> the ReportServerTempDB, a new session is created.
> How to make it work? Please help. Thanks,
> Lianghong
>
>|||Hi
I've the same problem with the session an rs:SessionId, anyone knwo a
solution'
Thanks
"debra doty" wrote:
> Did you ever find a work around for this. It doesn't seem to be working for
> me either.
> "Guo, Lianghong" wrote:
> > I want to render a PDF report and view the copy of the report in the HTML
> > viewer. What I did is to use rs.Render(...) to get the PDF report and the
> > SessionID, and then pass the SessionID to the URL string and run the URL.
> > But the rs:SessionID=xxxxx command does not work, it alway create a new
> > session for the report.
> >
> > This part of the code works fine to generate a PDF file for me and save a
> > session id in m_SessionID:
> >
> > byte[] results = null;
> > string historyID = null;
> > string devInfo = @."<DeviceInfo><Toolbar>False</Toolbar></DeviceInfo>";
> >
> > SessionHeader sh = new SessionHeader();
> > rs.SessionHeaderValue = sh;
> > results = rs.Render(
> > this.ReportConfig.ReportName,
> > "PDF",
> > historyID,
> > devInfo,
> > parameters,
> > credentials,
> > showHideToggle, out encoding, out mimeType, out
> > reportHistoryParameters,
> > out warnings,
> > out streamIDs);
> > m_SessionID = rs.SessionHeaderValue.SessionId;
> >
> > But when I use the generated sesionid for the URL access like this:
> > url => > "http://guoxp.softbrandsamer.com/reportserver?%2fInvItmb&rs:Command=Render&r
> > s:SessionID=" + m_SessionID
> >
> > it will create a new instance. And when I looked at the SessionData table in
> > the ReportServerTempDB, a new session is created.
> >
> > How to make it work? Please help. Thanks,
> >
> > Lianghong
> >
> >
> >
viewer. What I did is to use rs.Render(...) to get the PDF report and the
SessionID, and then pass the SessionID to the URL string and run the URL.
But the rs:SessionID=xxxxx command does not work, it alway create a new
session for the report.
This part of the code works fine to generate a PDF file for me and save a
session id in m_SessionID:
byte[] results = null;
string historyID = null;
string devInfo = @."<DeviceInfo><Toolbar>False</Toolbar></DeviceInfo>";
SessionHeader sh = new SessionHeader();
rs.SessionHeaderValue = sh;
results = rs.Render(
this.ReportConfig.ReportName,
"PDF",
historyID,
devInfo,
parameters,
credentials,
showHideToggle, out encoding, out mimeType, out
reportHistoryParameters,
out warnings,
out streamIDs);
m_SessionID = rs.SessionHeaderValue.SessionId;
But when I use the generated sesionid for the URL access like this:
url = "http://guoxp.softbrandsamer.com/reportserver?%2fInvItmb&rs:Command=Render&r
s:SessionID=" + m_SessionID
it will create a new instance. And when I looked at the SessionData table in
the ReportServerTempDB, a new session is created.
How to make it work? Please help. Thanks,
LianghongDid you ever find a work around for this. It doesn't seem to be working for
me either.
"Guo, Lianghong" wrote:
> I want to render a PDF report and view the copy of the report in the HTML
> viewer. What I did is to use rs.Render(...) to get the PDF report and the
> SessionID, and then pass the SessionID to the URL string and run the URL.
> But the rs:SessionID=xxxxx command does not work, it alway create a new
> session for the report.
> This part of the code works fine to generate a PDF file for me and save a
> session id in m_SessionID:
> byte[] results = null;
> string historyID = null;
> string devInfo = @."<DeviceInfo><Toolbar>False</Toolbar></DeviceInfo>";
> SessionHeader sh = new SessionHeader();
> rs.SessionHeaderValue = sh;
> results = rs.Render(
> this.ReportConfig.ReportName,
> "PDF",
> historyID,
> devInfo,
> parameters,
> credentials,
> showHideToggle, out encoding, out mimeType, out
> reportHistoryParameters,
> out warnings,
> out streamIDs);
> m_SessionID = rs.SessionHeaderValue.SessionId;
> But when I use the generated sesionid for the URL access like this:
> url => "http://guoxp.softbrandsamer.com/reportserver?%2fInvItmb&rs:Command=Render&r
> s:SessionID=" + m_SessionID
> it will create a new instance. And when I looked at the SessionData table in
> the ReportServerTempDB, a new session is created.
> How to make it work? Please help. Thanks,
> Lianghong
>
>|||Hi
I've the same problem with the session an rs:SessionId, anyone knwo a
solution'
Thanks
"debra doty" wrote:
> Did you ever find a work around for this. It doesn't seem to be working for
> me either.
> "Guo, Lianghong" wrote:
> > I want to render a PDF report and view the copy of the report in the HTML
> > viewer. What I did is to use rs.Render(...) to get the PDF report and the
> > SessionID, and then pass the SessionID to the URL string and run the URL.
> > But the rs:SessionID=xxxxx command does not work, it alway create a new
> > session for the report.
> >
> > This part of the code works fine to generate a PDF file for me and save a
> > session id in m_SessionID:
> >
> > byte[] results = null;
> > string historyID = null;
> > string devInfo = @."<DeviceInfo><Toolbar>False</Toolbar></DeviceInfo>";
> >
> > SessionHeader sh = new SessionHeader();
> > rs.SessionHeaderValue = sh;
> > results = rs.Render(
> > this.ReportConfig.ReportName,
> > "PDF",
> > historyID,
> > devInfo,
> > parameters,
> > credentials,
> > showHideToggle, out encoding, out mimeType, out
> > reportHistoryParameters,
> > out warnings,
> > out streamIDs);
> > m_SessionID = rs.SessionHeaderValue.SessionId;
> >
> > But when I use the generated sesionid for the URL access like this:
> > url => > "http://guoxp.softbrandsamer.com/reportserver?%2fInvItmb&rs:Command=Render&r
> > s:SessionID=" + m_SessionID
> >
> > it will create a new instance. And when I looked at the SessionData table in
> > the ReportServerTempDB, a new session is created.
> >
> > How to make it work? Please help. Thanks,
> >
> > Lianghong
> >
> >
> >
Wednesday, March 7, 2012
RS Integration with SharePoint 3.0 - Query with userid parameter
When integrating SQL Reporting Services 2005 with Sharepoint Services 3.0, and you have a SRS report that runs over a view with the UserID as a parameter (to filter the records the user has access to), will the SharePoint ReportViewer passover the UserID to RS and RS to SQL?
Sharepoint security with Reporting Services stops at Item level or does it impersontate down to SQL? Should authenticating be Integrated or SQL ? Should the userid in SQL be exact match with Sharepoint? Or are they mapped somewhere?
Thank You!!
Hi,
actually these are two different questions:
it depends how you implemented the authentication. If reports are called by Sharepoint, it is possible to use the information of the Windows Identity to authenticate against the SQL Server. As you are using a UserId approach and not the actual identity at the SQL Server level you could also use SQL Server authentication to run the query of the report. So the following options could be available:
[Report (UserId) -- IIS (Windows Integrated Authentication)] -- SQL Server (SQL Server Authentication with static credentials)
[Report (UserId) -- IIS (Windows Integrated Authentication)] -- SQL Server (Windows Authentication)
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
RS fails to render a report with changes just made
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!"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!|||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!|||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!
>
>|||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!
>|||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.
"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.
"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!
> >
> >
>
>|||You don't have to delete the report. Try just 2 and 3.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"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!
>> >
>> >
>>|||As well as checking your I.E. settings for caching, you should also check if
the results are being cached at your proxy server.
"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!
> >
> >
> >
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!"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!|||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!|||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!
>
>|||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!
>|||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.
"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.
"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!
> >
> >
>
>|||You don't have to delete the report. Try just 2 and 3.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"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!
>> >
>> >
>>|||As well as checking your I.E. settings for caching, you should also check if
the results are being cached at your proxy server.
"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!
> >
> >
> >
Subscribe to:
Posts (Atom)