Report parameter metadata not updated during deployment

In 2005, I've experienced a problem when re-deploying reports to the report server. The parameter references don't get updated properly and I would either need to re-deploy several times, or delete the reports and deploy a fresh copy. The latter re-creates the report GUIDs and messes up usage statistics. I've not been able to reproduce this consistently but have aexperienced it on several projects.

Is this issue being adressed in RS 2008?

I've run into this one as well.

I think this also occurred in SSRS 2000 as well.

|||The behavior around parameter metadata has not changed in Katmai. If you have a specific scenario where things get messed up, post a bug over on the connect site and we will take a look.|||

This is raised and explained in this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=100960&SiteID=1

I can't envisage parameter defaults and prompts being maintaned by an administrator. Does an override mechanism exist in RS 2005? If not, then will it be added in 2008?

Report parameter metadata not updated during deployment

In 2005, I've experienced a problem when re-deploying reports to the report server. The parameter references don't get updated properly and I would either need to re-deploy several times, or delete the reports and deploy a fresh copy. The latter re-creates the report GUIDs and messes up usage statistics. I've not been able to reproduce this consistently but have aexperienced it on several projects.

Is this issue being adressed in RS 2008?

I've run into this one as well.

I think this also occurred in SSRS 2000 as well.

|||The behavior around parameter metadata has not changed in Katmai. If you have a specific scenario where things get messed up, post a bug over on the connect site and we will take a look.|||

This is raised and explained in this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=100960&SiteID=1

I can't envisage parameter defaults and prompts being maintaned by an administrator. Does an override mechanism exist in RS 2005? If not, then will it be added in 2008?

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 Deployment Problem (DataSource)

I created a new Report Model project and specified folders for both the model and the datasources. For some reason, every time I deploy the model I get an error stating the datasource cannot be found. I've tried changing the project properties to no end. Here's the specific output

Deploying to http://localhost/ReportServer?%2f

Deploying data source '/Data Sources/CRM Database Conection'.

Deploying model 'CRM Filtered View Model'.

The item '/Data Sources/CRM Database Connection' cannot be found.

This seems to happen a lot when creating logical joins from tables from different datasources.

Report Model Deployment Problem (DataSource)

I created a new Report Model project and specified folders for both the model and the datasources. For some reason, every time I deploy the model I get an error stating the datasource cannot be found. I've tried changing the project properties to no end. Here's the specific output

Deploying to http://localhost/ReportServer?%2f

Deploying data source '/Data Sources/CRM Database Conection'.

Deploying model 'CRM Filtered View Model'.

The item '/Data Sources/CRM Database Connection' cannot be found.This seems to happen a lot when creating logical joins from tables from different datasources.

Report Model Deployment Error

Hi All,
I created a report model and when I tried to deploy I got the following:

The model ID of the submitted model must match that of the current model

I have searched all over for the cause and solution but, have had no luck.

Can someone please help me?

Thanks,

Roy
The SemanticModel ID of the submitted model must match the semantic model id of the existing model, otherwise you'll get this error.

The solution is to delete model from server (using Report Manager or Management Studio)before deploying.|||Yes, I had the same problem. Surely a deploy would be able to deal with this automatically?|||Deploy tries not to override existing model with completely different model.

Report Model Deployment Error

Hi All,
I created a report model and when I tried to deploy I got the following:

The model ID of the submitted model must match that of the current model

I have searched all over for the cause and solution but, have had no luck.

Can someone please help me?

Thanks,

Roy
The SemanticModel ID of the submitted model must match the semantic model id of the existing model, otherwise you'll get this error.

The solution is to delete model from server (using Report Manager or Management Studio)before deploying.|||Yes, I had the same problem. Surely a deploy would be able to deal with this automatically?|||Deploy tries not to override existing model with completely different model.sql

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!
|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Model Deployment : The model ID of the submitted model must match that of the

Running 2005 Beta 3 Refresh. When I first deploy, it works fine. Subsequent deployments yield the following error:

Error 1 The model ID of the submitted model must match that of the
current model. C:\Source\********.smdl 0 0

When I change the name of the smdl, it works fine. (Properties of the .smdl file)

Any ideas?

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

|||

Yes, thanks.

The scenario arises when you try to deploy a model in a NEW report project which has the same name as a model designed in a previous report project.

Jean-Pierre

|||

Lev Semenets - MSFT wrote:

For existing models Deploy actually means Update

However if Model ID is different, this cannot be considered as Update - the model may be completely different. In this case user must remove model from server before re-deploying it.

How can i remove a model from the server.?

Thanks !!|||

Programmatically - by calling SOAP API method DeleteItem()

|||

Hi,

no need to do SOAP.

Just go to the reporting web site, go to the models folder and delete the report.

Re-deploy and it's updated version is back in the folder.

Report Manager error "scale-out deployment not supported in this edition of Reporting Servi

Hi,

I have been trying to get report services installed but another error came:

The feature: "Scale-out deployment" is not supported in this edition of Reporting Services. (rsOperationNotSupported) (rsRPCError)

This error comes when I try to view either http://localhost/Reports or http://localhost/reportserver

Any suggestions?

thank you.

Can you tell us a little more about what you are trying to accomplish? What version of REporting Services are you trying to install. ARe you trying to set up a webfarm?

Thanks,

|||

I have given up of setting the Reporting Services.

Seems that I am not running the correct SQL version to use reporting services. I have express edition with advanced settings.

Basically I just wanted to run everything on the same computer.