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 Manager Web Client Security Error

I am attempting to access an Access database file located on one of our
servers on the network through Reporting Services Report Manager and am
receiving the error below. I have already setup our Report Server
Service account to a domain account that has full Access to the file. I
am able to run the report from Visual Studio.Net on my local machine. I
have setup and successfully deployed numerous SQL Server based reports
and am able to run an Access based report as long as it's located on my
report server. Any help anyone could provide is extremely appreciated.
============================================== Reporting Services Error
----
An error has occurred during report processing. (rsProcessingAborted)
Get Online Help
Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) Get Online Help
The Microsoft Jet database engine cannot open the file
'\\Server02\PhoneBook\PhoneBook.mdb'. It is already opened exclusively
by another user, or you need permission to view its data.
----
Microsoft Reporting Services
==============================================Have you tried running it with Vis Studio closed?
I have not done this with RS, but I did have many problems connecting
asp pages to access using a DSN.
I ended up using a DSN-Less connection and it worked. I am not sure if
that is an option in RS though.
"Leo" <leo_olden@.yahoo.com> wrote in message news:leo_olden@.yahoo.com:
> I am attempting to access an Access database file located on one of our
> servers on the network through Reporting Services Report Manager and am
> receiving the error below. I have already setup our Report Server
> Service account to a domain account that has full Access to the file. I
> am able to run the report from Visual Studio.Net on my local machine. I
> have setup and successfully deployed numerous SQL Server based reports
> and am able to run an Access based report as long as it's located on my
> report server. Any help anyone could provide is extremely appreciated.
> ==============================================> Reporting Services Error
> ----
> --
> An error has occurred during report processing. (rsProcessingAborted)
> Get Online Help
> Cannot create a connection to data source 'DataSource1'.
> (rsErrorOpeningConnection) Get Online Help
> The Microsoft Jet database engine cannot open the file
> '\\Server02\PhoneBook\PhoneBook.mdb'. It is already opened exclusively
> by another user, or you need permission to view its data.
> ----
> --
> Microsoft Reporting Services
> ==============================================|||Thanks for your reply John. I actually did some further research and
found that the problem I'm experiencing is a known problem with Access
and the Microsoft Jet database engine. My workaround was to create a
batch file on my report server that copies in the original Access
database file to the report server every hour. My datasource now
resides on my report server and is therefore accessible.