Report OK in local development, won't run on server

I am attempting to migrate a report I developed locally in my development
environment to the Reporting Services server in preparation for deployment.
The report gets its data from a stored procedure that requires no
parameters; it simply runs and returns data.
I am able to upload the RDL file to the server without incident and the
report is shown properly in the report listing on the reporting server web
page.
However when I try to render the report on the reporting server I receive
the following errors:
An error has occurred during report processing. (rsProcessingAborted)
Cannot set the command type for data set 'DataSet1'.
(rsErrorSettingCommandType)
Stored Procedure command type is not supported.
The report itself is very simple, only one matrix control exists on the page.
I did not install the server environment myself however I have been able to
determine that Reporting Services SP2 has been installed - as it has been in
my development environment.
Any help you could give would be appreciated, thanks.
-ChuckAlthough I haven't see this exact error I have seen an issue with the stored
procedure security rights not allowing the credentials your report is
running under to execute it.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ExNooYorka" <ExNooYorka@.discussions.microsoft.com> wrote in message
news:3447A77A-5DB5-4D1B-A067-3E576605F484@.microsoft.com...
>I am attempting to migrate a report I developed locally in my development
> environment to the Reporting Services server in preparation for
> deployment.
> The report gets its data from a stored procedure that requires no
> parameters; it simply runs and returns data.
> I am able to upload the RDL file to the server without incident and the
> report is shown properly in the report listing on the reporting server web
> page.
> However when I try to render the report on the reporting server I receive
> the following errors:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot set the command type for data set 'DataSet1'.
> (rsErrorSettingCommandType)
> Stored Procedure command type is not supported.
> The report itself is very simple, only one matrix control exists on the
> page.
> I did not install the server environment myself however I have been able
> to
> determine that Reporting Services SP2 has been installed - as it has been
> in
> my development environment.
> Any help you could give would be appreciated, thanks.
> -Chuck|||Bruce:
Thanks for the reply.
When I read your reply I thought you hit the nail right on the head
because on the remote SQL Server I had indeed not granted credentials
to anyone - only admins could run my stored procedure.
However even granting rights to the PUBLIC group did not resolve the
problem described below.
I have, however, resolved it.
The data source present on the reporting server was pointed to a custom
data provider that did not support the Stored Procedure command type.
I believe it was the custom data provider (or the layer that interacts
with the custom data provider) that was throwing the error described
below.
I created a new data source on the report server that points to the
native SQL Server data provider and that resolved the issue.
Thanks again for your help - a fresh pair of eyes is always most
helpful.
-Chuck
Bruce L-C [MVP] wrote:
> Although I haven't see this exact error I have seen an issue with the stored
> procedure security rights not allowing the credentials your report is
> running under to execute it.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ExNooYorka" <ExNooYorka@.discussions.microsoft.com> wrote in message
> news:3447A77A-5DB5-4D1B-A067-3E576605F484@.microsoft.com...
> >I am attempting to migrate a report I developed locally in my development
> > environment to the Reporting Services server in preparation for
> > deployment.
> >
> > The report gets its data from a stored procedure that requires no
> > parameters; it simply runs and returns data.
> >
> > I am able to upload the RDL file to the server without incident and the
> > report is shown properly in the report listing on the reporting server web
> > page.
> >
> > However when I try to render the report on the reporting server I receive
> > the following errors:
> >
> > An error has occurred during report processing. (rsProcessingAborted)
> > Cannot set the command type for data set 'DataSet1'.
> > (rsErrorSettingCommandType)
> > Stored Procedure command type is not supported.
> >
> > The report itself is very simple, only one matrix control exists on the
> > page.
> >
> > I did not install the server environment myself however I have been able
> > to
> > determine that Reporting Services SP2 has been installed - as it has been
> > in
> > my development environment.
> >
> > Any help you could give would be appreciated, thanks.
> >
> > -Chuck

Report Model in VM environment

What are the limitation when creating report models in VM environment?

Not certain what you mean by "VM environment" but if you are referring to Virtual Machine/Server, yes report models are supported.

Hope that helps.

Thanks, Jon

|||

Jon - Correct, I was refering to "Virtual Machine/Server". When trying to create report models that sits on "Big" tables, it happens very often that I get "Timeout Error" which usually occurs after 5min. All the timeout parameters in Data Source are set to zero but it still happens.

Thanks

|||

I might suggest running with gather statistics=false. This should increase performance of model generation as it will not need to query the data.

Otherwise, in what context is the timeout error occuring. Does the error message denote a SQL or IIS timeout?

Thanks, Jon

|||

Jon - It's a SQL timeout and usually it occurs when column uniqueness is being calculated.

Thanks

Report looks different in browser than in development environment

I have a tabular report that has horizontal lines separating the rows. The
row heights are all the same in the development environment, but in the
browser there are many different heights and it looks like crap. Any
suggestions?The Dev environment previews as an Image, not as HTML. Try rendering to an
image format(tiff) from the browser and see how it looks.
--
| Thread-Topic: Report looks different in browser than in development
environment
| thread-index: AcUfSW1UwXSqLdOGS0q4ha3NKeZY/A==| X-WBNR-Posting-Host: 67.41.128.193
| From: "=?Utf-8?B?VGVkZHkgU2FsYWQ=?="
<TeddySalad@.discussions.microsoft.com>
| Subject: Report looks different in browser than in development environment
| Date: Wed, 2 Mar 2005 09:01:07 -0800
| Lines: 4
| Message-ID: <4587D354-7348-4541-B9F7-0D7FAA7B499D@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path:
TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA
03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.reportingsvcs:44343
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| I have a tabular report that has horizontal lines separating the rows.
The
| row heights are all the same in the development environment, but in the
| browser there are many different heights and it looks like crap. Any
| suggestions?
|

Report hangs on "Report is being generated" screen

I am having issues trying to use a deployed report on our live server.
The report works fine in the development environment - yet when posted to
the live server it seems to work fine but hangs on the "Report is being
generated" screen.
We are still in an evaluation stage of Reporting Services and such are using
the trial version, this is installed on Windows 2003 Server. The report was
developed using Visual Studio 2003 and will be instantiated by an ASP.Net
application. The report is being fired using a
Response.redirect("/ReportServer?%2fReport+Project1%2fReportName&session=" +
Session.SessionID.ToString() + "&rs%3aCommand=Render");
Any suggestions would be greatly appreciated.
Regards
StevenA few questions for you.
- Are you going against the same database when you deploy or a different
one. I.e. could it be a difference is the size of the data you are reporting
against.
- Does this happen when you run the report from Report Manager? If so then
we can disregard the fact it is coming from your app. If it works fine from
the report manager then that tells us a lot too.
- Is your asp.net application on the same server and is it in the same
domain?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"StvPl" <StvPl@.discussions.microsoft.com> wrote in message
news:6290C7CB-C600-41F6-ACE4-ED20D8AD7E45@.microsoft.com...
> I am having issues trying to use a deployed report on our live server.
> The report works fine in the development environment - yet when posted to
> the live server it seems to work fine but hangs on the "Report is being
> generated" screen.
> We are still in an evaluation stage of Reporting Services and such are
using
> the trial version, this is installed on Windows 2003 Server. The report
was
> developed using Visual Studio 2003 and will be instantiated by an ASP.Net
> application. The report is being fired using a
> Response.redirect("/ReportServer?%2fReport+Project1%2fReportName&session="
+
> Session.SessionID.ToString() + "&rs%3aCommand=Render");
> Any suggestions would be greatly appreciated.
> Regards
> Steven
>|||Thanks for your response Bruce.
I've answered your questions below...
> - Are you going against the same database when you deploy or a different
> one. I.e. could it be a difference is the size of the data you are reporting
> against.
It is against the same database and the subset of data retrieved is very
small - perhaps 50 rows.
> - Does this happen when you run the report from Report Manager? If so then
> we can disregard the fact it is coming from your app. If it works fine from
> the report manager then that tells us a lot too.
Works fine from Report Manager.
> - Is your asp.net application on the same server and is it in the same
> domain?
yes.
Thanks for your help
Steven
"Bruce L-C [MVP]" wrote:
> A few questions for you.
> - Are you going against the same database when you deploy or a different
> one. I.e. could it be a difference is the size of the data you are reporting
> against.
> - Does this happen when you run the report from Report Manager? If so then
> we can disregard the fact it is coming from your app. If it works fine from
> the report manager then that tells us a lot too.
> - Is your asp.net application on the same server and is it in the same
> domain?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "StvPl" <StvPl@.discussions.microsoft.com> wrote in message
> news:6290C7CB-C600-41F6-ACE4-ED20D8AD7E45@.microsoft.com...
> > I am having issues trying to use a deployed report on our live server.
> >
> > The report works fine in the development environment - yet when posted to
> > the live server it seems to work fine but hangs on the "Report is being
> > generated" screen.
> >
> > We are still in an evaluation stage of Reporting Services and such are
> using
> > the trial version, this is installed on Windows 2003 Server. The report
> was
> > developed using Visual Studio 2003 and will be instantiated by an ASP.Net
> > application. The report is being fired using a
> > Response.redirect("/ReportServer?%2fReport+Project1%2fReportName&session="
> +
> > Session.SessionID.ToString() + "&rs%3aCommand=Render");
> >
> > Any suggestions would be greatly appreciated.
> >
> > Regards
> > Steven
> >
> >
>
>|||This may be a dumb question, but are you sure that the login you are using
has read permission from the database?
I had a similar symptom when I was testing a deployment. I was using
different login info and forgot to provide access to the database. The
Reporting Services page would come up and I could select a report to run,
but the report would just hang at the generating report stage. Dumb, I know!
Ken
"StvPl" <StvPl@.discussions.microsoft.com> wrote in message
news:6290C7CB-C600-41F6-ACE4-ED20D8AD7E45@.microsoft.com...
> I am having issues trying to use a deployed report on our live server.
> The report works fine in the development environment - yet when posted to
> the live server it seems to work fine but hangs on the "Report is being
> generated" screen.
> We are still in an evaluation stage of Reporting Services and such are
using
> the trial version, this is installed on Windows 2003 Server. The report
was
> developed using Visual Studio 2003 and will be instantiated by an ASP.Net
> application. The report is being fired using a
> Response.redirect("/ReportServer?%2fReport+Project1%2fReportName&session="
+
> Session.SessionID.ToString() + "&rs%3aCommand=Render");
> Any suggestions would be greatly appreciated.
> Regards
> Steven
>|||Thanks for the suggestion Ken.
I've checked the database access and the account specified in the
credentials of the shared data component of the report has full access.
Regards
Steven
"Ken" wrote:
> This may be a dumb question, but are you sure that the login you are using
> has read permission from the database?
> I had a similar symptom when I was testing a deployment. I was using
> different login info and forgot to provide access to the database. The
> Reporting Services page would come up and I could select a report to run,
> but the report would just hang at the generating report stage. Dumb, I know!
> Ken
> "StvPl" <StvPl@.discussions.microsoft.com> wrote in message
> news:6290C7CB-C600-41F6-ACE4-ED20D8AD7E45@.microsoft.com...
> > I am having issues trying to use a deployed report on our live server.
> >
> > The report works fine in the development environment - yet when posted to
> > the live server it seems to work fine but hangs on the "Report is being
> > generated" screen.
> >
> > We are still in an evaluation stage of Reporting Services and such are
> using
> > the trial version, this is installed on Windows 2003 Server. The report
> was
> > developed using Visual Studio 2003 and will be instantiated by an ASP.Net
> > application. The report is being fired using a
> > Response.redirect("/ReportServer?%2fReport+Project1%2fReportName&session="
> +
> > Session.SessionID.ToString() + "&rs%3aCommand=Render");
> >
> > Any suggestions would be greatly appreciated.
> >
> > Regards
> > Steven
> >
> >
>
>