Report Viewer Toolbar Style messed up

Hi All,
When I run a report from Report Manager or from a URL using the ReportViewer
the toolbar looses all styling - it runs down over several lines. I am using
RS 2005 and have also got a RS2000 set-up where we don't have this problem. I
have tried to put in the reference to the stylesheet in the URL access but it
hasn't done anything. Anyone know what the problem could be here? Everything
else in RS2005 works fine.
I also have a problem with Dundas Charts. When accessing the reports via a
URL the charts display if I put in &rc:Toolbar=True but if I put
&rc:Toolbar=False then the Charts don't display and I get a box with a red
cross in it. On the report there are also some tables of data and these
display in both cases.
Any answers to the above much appreciated!
Thanks
RichardHi Richard -
Did you ever get this sorted out? I'm having the same problem, too. I do
have a feeling this is a Win2K3 issue, but just want to guidance as to what
it could be.
Microsoft dudes -- any ideas here?
Thanks,
Brent
"Richard" wrote:
> Hi All,
> When I run a report from Report Manager or from a URL using the ReportViewer
> the toolbar looses all styling - it runs down over several lines. I am using
> RS 2005 and have also got a RS2000 set-up where we don't have this problem. I
> have tried to put in the reference to the stylesheet in the URL access but it
> hasn't done anything. Anyone know what the problem could be here? Everything
> else in RS2005 works fine.
> I also have a problem with Dundas Charts. When accessing the reports via a
> URL the charts display if I put in &rc:Toolbar=True but if I put
> &rc:Toolbar=False then the Charts don't display and I get a box with a red
> cross in it. On the report there are also some tables of data and these
> display in both cases.
> Any answers to the above much appreciated!
> Thanks
> Richardsql

Report Timeout problem ;Out of memory exception

I am having a problem with report rendering.
The MSSRS Report runs for around 15 minutes and then the report page times
out giving the error as
"Out of memory exception. Server application unavailable".
When i check the query execution time in query analyser, query returns
results in 10 minutes.
There are about 3 groups in the RDL design.
Please provide any suggestions to overcome this problem.
Thanks in advance.
Thanks and Cheers,
TruptiSounds like your report is just too big. RS renders reports in memory, thus
the 'Out of memory exception'. Try redesigning the report or adding more
memory to your machine/server.
Also, if you get the report to successfully run you can try to pin point
what's taking so long. Look in the ReportServer database; the ExecutionLog
table. It shows what report ran, when, the amount of time for data
retrieval, processing time, and rendering time. It also shows what render
format, render status (fail or success), query row count and byte size of
the rendered file.
--
Adrian M.
MCP
"Trupti" <gettrupti@.hotmail.com> wrote in message
news:e0Tt9bcNFHA.1392@.TK2MSFTNGP10.phx.gbl...
>I am having a problem with report rendering.
> The MSSRS Report runs for around 15 minutes and then the report page
> times out giving the error as
> "Out of memory exception. Server application unavailable".
> When i check the query execution time in query analyser, query returns
> results in 10 minutes.
> There are about 3 groups in the RDL design.
> Please provide any suggestions to overcome this problem.
> Thanks in advance.
> Thanks and Cheers,
> Trupti
>
>

Report Timeout

I have designed a report that hits a large table of over a million rows. The report runs in the development environment as a preview. When deployed, the report runs about 1.5 hours and then returns an error. The report is set not to timeout. What could be causing this behavior?What error is being returned?
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"DJP" <DJP@.discussions.microsoft.com> wrote in message
news:D8468C56-4D72-47FB-AA76-9A82D8A9CDAC@.microsoft.com...
> I have designed a report that hits a large table of over a million rows.
The report runs in the development environment as a preview. When deployed,
the report runs about 1.5 hours and then returns an error. The report is
set not to timeout. What could be causing this behavior?|||The page displayed is: The page cannot be displayed
"Bruce Johnson [MSFT]" wrote:
> What error is being returned?
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "DJP" <DJP@.discussions.microsoft.com> wrote in message
> news:D8468C56-4D72-47FB-AA76-9A82D8A9CDAC@.microsoft.com...
> > I have designed a report that hits a large table of over a million rows.
> The report runs in the development environment as a preview. When deployed,
> the report runs about 1.5 hours and then returns an error. The report is
> set not to timeout. What could be causing this behavior?
>
>

Report schedule re-starts itself

We have a server runs every week a schedule to generate 10 reports at the
same time. It usually runs in one hour (all reports).
But now the CPU hungs at 100% for two hours (ReportServer.exe) and none of
the reports are generated.
We stopped IIS and the ReportServer several times, but something keeps
re-scheduling all 10 reports and it gets hung up again.
Can somebody tell me how to delete the self-scheduled jobs?
Thanks.You are not alone... I got the same issue and had to uninstall then
re-install the SQL Reporting Services (oops! not the best way).
"Cesar Meza" wrote:
> We have a server runs every week a schedule to generate 10 reports at the
> same time. It usually runs in one hour (all reports).
> But now the CPU hungs at 100% for two hours (ReportServer.exe) and none of
> the reports are generated.
> We stopped IIS and the ReportServer several times, but something keeps
> re-scheduling all 10 reports and it gets hung up again.
> Can somebody tell me how to delete the self-scheduled jobs?
> Thanks.|||I gave up, so this is what I did:
1. Stop both IIS and ReportServer
2. Deleted manually all the entries from the table Schedules, RunningJobs
and Subscriptions.
3. Re-start all services, and delete any entries (if any) in the schedules
and subscriptions via the Report Manager.
4. Re-schedule the job.
Note of caution: I only had one schedule with 10 jobs on this server, so it
was a no brainer. I DO NOT RECOMEND doing this if you have several schedules.
If you have to, delete only the entries needed.
If somebody from the gurus have an explanation for this, or have better way
to do what I did, please share it with us.
Thank you.
"dontra" wrote:
> You are not alone... I got the same issue and had to uninstall then
> re-install the SQL Reporting Services (oops! not the best way).
>

Report runs in the frontend but not in designer!!??

The report gives me a blank screen when I refresh the data under the design mode, but when I run it with my access tool, the data comes out fine.
The report is running on a complex query in an access database.Open the report and do verify database

Report runs in preview in VS.net 2003, but not on Report server

I have a report which I have published to my Report server (sql 2000 on
windows 2003). This report runs from my VS.net developers edition preview
page, but once I publish it to my Sql reporting services report server, it
will not run - there is a long delay, then I recieve repeated prompts for
username and password, and then failure.
I am logged in as the same user as on my vs.net.
I have a number of other reports that run correctly on both my development
system and on the report server. I just can not figure out what I have
different in this report or datasource that is causing this issue.
If anyone can help me figure out what permissions I have messed up. I would
appreciate it.
Fred ZilzWhen you run Report as preview in VS.NET, the Report Server is not involved.
So, the preview running fine means you do not have problem to get data (if
the database reeqires logging in).
Therefore, your problem could be that your account cannot log into report
server (do not confuse it with database server, although both may use the
same SQL Server). You could use Report Manager to go to the folder where the
report is deployed, click Properties->Security to see who is allowsed to
browse reports in that folder.
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:uaypGQvPFHA.2584@.TK2MSFTNGP15.phx.gbl...
> I have a report which I have published to my Report server (sql 2000 on
> windows 2003). This report runs from my VS.net developers edition preview
> page, but once I publish it to my Sql reporting services report server, it
> will not run - there is a long delay, then I recieve repeated prompts for
> username and password, and then failure.
> I am logged in as the same user as on my vs.net.
> I have a number of other reports that run correctly on both my development
> system and on the report server. I just can not figure out what I have
> different in this report or datasource that is causing this issue.
> If anyone can help me figure out what permissions I have messed up. I
would
> appreciate it.
> Fred Zilz
>|||I have found that the designer and the server handle credentials differently,
are you storing your credentials in the connection string by any chance?
"Fredrick A. Zilz" wrote:
> I have a report which I have published to my Report server (sql 2000 on
> windows 2003). This report runs from my VS.net developers edition preview
> page, but once I publish it to my Sql reporting services report server, it
> will not run - there is a long delay, then I recieve repeated prompts for
> username and password, and then failure.
> I am logged in as the same user as on my vs.net.
> I have a number of other reports that run correctly on both my development
> system and on the report server. I just can not figure out what I have
> different in this report or datasource that is causing this issue.
> If anyone can help me figure out what permissions I have messed up. I would
> appreciate it.
> Fred Zilz
>
>|||Yes, I am storing credentials in the connection string.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>I have found that the designer and the server handle credentials
>differently,
> are you storing your credentials in the connection string by any chance?
> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000 on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report server,
>> it
>> will not run - there is a long delay, then I recieve repeated prompts for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>|||For security reasons, the report designer will remove credentials from the
connection string (and therefore not store in the RDL connection string on
disk). Consequently, the published report on the server has no credentials
specified and you need to add them e.g. through report manager by updating
the data source information. Credentials specified there are stored
encrypted in the report server metadata database.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:ur1lQEGQFHA.1884@.TK2MSFTNGP15.phx.gbl...
> Yes, I am storing credentials in the connection string.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>>I have found that the designer and the server handle credentials
>>differently,
>> are you storing your credentials in the connection string by any chance?
>> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000 on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report server,
>> it
>> will not run - there is a long delay, then I recieve repeated prompts
>> for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>
>|||I have looked at the datasources of a report that works and one that does
not, both have the credentials stored in the metadata database both are
shared data sources, both use the same SQL credentials and both databases
are set with the credentials authorizing database permit and read
permissions. I double checked the security settings on the report server
and both shared data sources and both reports are set with the same security
settings (domain users with browser permissions)
I have tried deleting the reports and redeploying with the same results. I
just can not seem to find what is different between the reports that work
and the ones that don't. They are in fact both in the same report Solution
on my VS.net development station.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:ePJBfILQFHA.4020@.tk2msftngp13.phx.gbl...
> For security reasons, the report designer will remove credentials from the
> connection string (and therefore not store in the RDL connection string on
> disk). Consequently, the published report on the server has no credentials
> specified and you need to add them e.g. through report manager by updating
> the data source information. Credentials specified there are stored
> encrypted in the report server metadata database.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
> news:ur1lQEGQFHA.1884@.TK2MSFTNGP15.phx.gbl...
>> Yes, I am storing credentials in the connection string.
>> "Dan" <Dan@.discussions.microsoft.com> wrote in message
>> news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>>I have found that the designer and the server handle credentials
>>differently,
>> are you storing your credentials in the connection string by any chance?
>> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000 on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report server,
>> it
>> will not run - there is a long delay, then I recieve repeated prompts
>> for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>
>>
>|||As a way of trouble shooting I created a new datasource in the same project
as the malfunctioning report. I created a simple report based on that data
source, but used the same connection credentials (SQL) and the same query
string. Deployed this and it works. I then set my malfunctioning report to
the new datasource redeployed and ran - same problem - long pause and then
request for credentials.
"Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
news:uKFtr1QQFHA.1096@.tk2msftngp13.phx.gbl...
>I have looked at the datasources of a report that works and one that does
>not, both have the credentials stored in the metadata database both are
>shared data sources, both use the same SQL credentials and both databases
>are set with the credentials authorizing database permit and read
>permissions. I double checked the security settings on the report server
>and both shared data sources and both reports are set with the same
>security settings (domain users with browser permissions)
> I have tried deleting the reports and redeploying with the same results.
> I just can not seem to find what is different between the reports that
> work and the ones that don't. They are in fact both in the same report
> Solution on my VS.net development station.
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:ePJBfILQFHA.4020@.tk2msftngp13.phx.gbl...
>> For security reasons, the report designer will remove credentials from
>> the connection string (and therefore not store in the RDL connection
>> string on disk). Consequently, the published report on the server has no
>> credentials specified and you need to add them e.g. through report
>> manager by updating the data source information. Credentials specified
>> there are stored encrypted in the report server metadata database.
>>
>> -- Robert
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Fredrick A. Zilz" <fzilz@.NOSPAM.interhealthusa.com> wrote in message
>> news:ur1lQEGQFHA.1884@.TK2MSFTNGP15.phx.gbl...
>> Yes, I am storing credentials in the connection string.
>> "Dan" <Dan@.discussions.microsoft.com> wrote in message
>> news:D2F58AB1-CB8D-4A6F-BCB2-1D5BF664D58F@.microsoft.com...
>>I have found that the designer and the server handle credentials
>>differently,
>> are you storing your credentials in the connection string by any
>> chance?
>> "Fredrick A. Zilz" wrote:
>> I have a report which I have published to my Report server (sql 2000
>> on
>> windows 2003). This report runs from my VS.net developers edition
>> preview
>> page, but once I publish it to my Sql reporting services report
>> server, it
>> will not run - there is a long delay, then I recieve repeated prompts
>> for
>> username and password, and then failure.
>> I am logged in as the same user as on my vs.net.
>> I have a number of other reports that run correctly on both my
>> development
>> system and on the report server. I just can not figure out what I
>> have
>> different in this report or datasource that is causing this issue.
>> If anyone can help me figure out what permissions I have messed up. I
>> would
>> appreciate it.
>> Fred Zilz
>>
>>
>>
>