Cannot Deploy Report Model

I'm going through the 2005 SSRS tutorial for creating a report model and I
cannot deploy the model. The message I get is:
The permissions granted to user 'DOMAIN\USER' are insufficient for
performing this operation.
Both the SQL Server 2005 and SSRS are deployed on my machine on which I am
an administrator (both within the windows environment and in SQL Server).
Can someone please help?
Thanks,
JimI would imagine you are part of the Content Manager role on the report
server? Make sure your role on the report server has permission to Manage
Models and View Models. I had this problem when I upgraded from SSRS 2000 to
2005. For some reason none of the report model permissions were set after
the upgrade.
"Jim" wrote:
> I'm going through the 2005 SSRS tutorial for creating a report model and I
> cannot deploy the model. The message I get is:
> The permissions granted to user 'DOMAIN\USER' are insufficient for
> performing this operation.
> Both the SQL Server 2005 and SSRS are deployed on my machine on which I am
> an administrator (both within the windows environment and in SQL Server).
> Can someone please help?
> Thanks,
> Jim

Cannot create models with data source views using the ReportingService2005 web service

Question: Using the ReportingService2005 web service, how do I create a report model with a "data source view"?

Background: We are planning on shipping SQL Server 2005 (Work Group Edition) with our Enterprise application to over 30 countries. We hope to leverage the functionality of Reporting Services from our application.

We will be referencing the ReportingService2005 web service for configuration and installation of our application reporting environment. We DO NOT have access to customer machines since this is a "shrink-wrap" application. Furthermore, the customer should NOT be required to use the Business Intellegence Studio to configure the application.

Problem: We are able to create shared data sources and reports without any problems using the ReportingService2005 web service. Furthermore, we are able to generate report models based on the share data sources without a problem. However, we are unable to generate report models with "Data Source Views" using the web service. I have tried to use the CreateModel method but when I examine the data model in Reporting Services, there is an an error stating: " The shared data source reference is no longer valid".

When you say, "I examine the data model in Reporting Services", do you mean that you download the report model file and try to open it as part of a Report Model project inside BI Development Studio?|||

No, I mean that I surf into the Reporting Services website, click on the newly created model, and then click on the link labled "Data Sources". It is there that I receive the message "The shared data source reference is no longer valid."

I am then forced to browse to the newly created data source and click "apply". If I don't go through this "manual" process, I received an error when I try to create a report (using Report Builder) based on the newly created model.

Cannot create a connection to data source 'dataSource1'.

I successfully created the a Report model and deployed it to the server. When i run the a simple report on the SQL Server where reporting Services is installed it runs fine. When I run the report from anywhere else, I get the error below. I don't have a datasource called 'dataSource1'.

*******************************************************************

For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Cannot create a connection to data source 'dataSource1'.
-
An error has occurred during report processing.

*******************************************************************

Thanks for any help!

Most likely, you configured the data source credentials to use "Windows Integrated Security".

If you turn on remote errors (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=230593&SiteID=1), you would actually see the inner exception message which is most likely about a failed logon.

Windows Integrated Security only works if your domain has Kerberos-delegation enabled - otherwise you will need to store credentials on the report server (more details: http://msdn2.microsoft.com/en-us/library/ms160330(SQL.90).aspx)

-- Robert

|||

This is what I did to solve the error (just kept Windows Integrated Security enabled):

Changed the connection string.

From: SQLNCLI.1;Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True
To: Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True

This solved the 'Cannot find dataSource1 datasource' error.

|||

My heart goes out to anyone that has to deal with this message: Cannot create a connection to data source 'dataSource1'. Hopefully, this will help fix your issue. My configuration consists of 2 servers, both Win2003, no domain, one has the production database, the other has all reporting services including the report builder. I would get the message when I hit the "Run Report" button in Report builder. The problem has to do with passing credentials from the server that launches report builder to the server that hosts the data. The datasource1 is an internal datasource so don't bother looking for it. If you look in the trace logs it's passing ANONYMOUS LOGON, which has no permissions. So, to fix first create a user with Admin privileges with the same credentials on both servers. In IIS of the Reports server, go to Directory Security, Edit, and Enable Anonymous Access, place your user in the username/password boxes. Do not check integrated Windows authentication. Go into your report manager to configure your data sources. I have 2, one for report builder and one for report execution, but doesn't matter because they are both the same. For the data source(s), enter your connection string like this: Data Source=DBSERVER;Initial Catalog=DB;Integrated Security=True
Then click on Credentials stored securely in the report server, enter your user name and password of the same user as above. (I gave this user admin priviliges on both boxes, and added this user as a login to the SQL Server database for the database server.)
Below the username/password there are two checkboxes: Check the "Use as Windows Credentials when Connecting to the Data source" and leave the "Impersonate" unchecked. Think of it this way, you're creating the same user all the way through, IIS uses it, then Reporting Services uses it, then your DB server uses it, and finally SQL Server (where data is stored) uses it. This way there are no credential storing/passing problems, good luck!! jwf

|||...one more thing from above, when launching the Report builder, enter the same credentials as your special user that was created and be sure to check the "Remember Me" checkbox for good measure.

Cannot create a connection to data source 'dataSource1'.

I successfully created the a Report model and deployed it to the server. When i run the a simple report on the SQL Server where reporting Services is installed it runs fine. When I run the report from anywhere else, I get the error below. I don't have a datasource called 'dataSource1'.

*******************************************************************

For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Cannot create a connection to data source 'dataSource1'.
-
An error has occurred during report processing.

*******************************************************************

Thanks for any help!

Most likely, you configured the data source credentials to use "Windows Integrated Security".

If you turn on remote errors (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=230593&SiteID=1), you would actually see the inner exception message which is most likely about a failed logon.

Windows Integrated Security only works if your domain has Kerberos-delegation enabled - otherwise you will need to store credentials on the report server (more details: http://msdn2.microsoft.com/en-us/library/ms160330(SQL.90).aspx)

-- Robert

|||

This is what I did to solve the error (just kept Windows Integrated Security enabled):

Changed the connection string.

From: SQLNCLI.1;Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True
To: Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True

This solved the 'Cannot find dataSource1 datasource' error.

|||

My heart goes out to anyone that has to deal with this message: Cannot create a connection to data source 'dataSource1'. Hopefully, this will help fix your issue. My configuration consists of 2 servers, both Win2003, no domain, one has the production database, the other has all reporting services including the report builder. I would get the message when I hit the "Run Report" button in Report builder. The problem has to do with passing credentials from the server that launches report builder to the server that hosts the data. The datasource1 is an internal datasource so don't bother looking for it. If you look in the trace logs it's passing ANONYMOUS LOGON, which has no permissions. So, to fix first create a user with Admin privileges with the same credentials on both servers. In IIS of the Reports server, go to Directory Security, Edit, and Enable Anonymous Access, place your user in the username/password boxes. Do not check integrated Windows authentication. Go into your report manager to configure your data sources. I have 2, one for report builder and one for report execution, but doesn't matter because they are both the same. For the data source(s), enter your connection string like this: Data Source=DBSERVER;Initial Catalog=DB;Integrated Security=True
Then click on Credentials stored securely in the report server, enter your user name and password of the same user as above. (I gave this user admin priviliges on both boxes, and added this user as a login to the SQL Server database for the database server.)
Below the username/password there are two checkboxes: Check the "Use as Windows Credentials when Connecting to the Data source" and leave the "Impersonate" unchecked. Think of it this way, you're creating the same user all the way through, IIS uses it, then Reporting Services uses it, then your DB server uses it, and finally SQL Server (where data is stored) uses it. This way there are no credential storing/passing problems, good luck!! jwf

|||...one more thing from above, when launching the Report builder, enter the same credentials as your special user that was created and be sure to check the "Remember Me" checkbox for good measure.

Cannot create a connection to data source ''dataSource1''.

I successfully created the a Report model and deployed it to the server. When i run the a simple report on the SQL Server where reporting Services is installed it runs fine. When I run the report from anywhere else, I get the error below. I don't have a datasource called 'dataSource1'.

*******************************************************************

For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Cannot create a connection to data source 'dataSource1'.
-
An error has occurred during report processing.

*******************************************************************

Thanks for any help!

Most likely, you configured the data source credentials to use "Windows Integrated Security".

If you turn on remote errors (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=230593&SiteID=1), you would actually see the inner exception message which is most likely about a failed logon.

Windows Integrated Security only works if your domain has Kerberos-delegation enabled - otherwise you will need to store credentials on the report server (more details: http://msdn2.microsoft.com/en-us/library/ms160330(SQL.90).aspx)

-- Robert

|||

This is what I did to solve the error (just kept Windows Integrated Security enabled):

Changed the connection string.

From: SQLNCLI.1;Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True
To: Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True

This solved the 'Cannot find dataSource1 datasource' error.

|||

My heart goes out to anyone that has to deal with this message: Cannot create a connection to data source 'dataSource1'. Hopefully, this will help fix your issue. My configuration consists of 2 servers, both Win2003, no domain, one has the production database, the other has all reporting services including the report builder. I would get the message when I hit the "Run Report" button in Report builder. The problem has to do with passing credentials from the server that launches report builder to the server that hosts the data. The datasource1 is an internal datasource so don't bother looking for it. If you look in the trace logs it's passing ANONYMOUS LOGON, which has no permissions. So, to fix first create a user with Admin privileges with the same credentials on both servers. In IIS of the Reports server, go to Directory Security, Edit, and Enable Anonymous Access, place your user in the username/password boxes. Do not check integrated Windows authentication. Go into your report manager to configure your data sources. I have 2, one for report builder and one for report execution, but doesn't matter because they are both the same. For the data source(s), enter your connection string like this: Data Source=DBSERVER;Initial Catalog=DB;Integrated Security=True
Then click on Credentials stored securely in the report server, enter your user name and password of the same user as above. (I gave this user admin priviliges on both boxes, and added this user as a login to the SQL Server database for the database server.)
Below the username/password there are two checkboxes: Check the "Use as Windows Credentials when Connecting to the Data source" and leave the "Impersonate" unchecked. Think of it this way, you're creating the same user all the way through, IIS uses it, then Reporting Services uses it, then your DB server uses it, and finally SQL Server (where data is stored) uses it. This way there are no credential storing/passing problems, good luck!! jwf

|||...one more thing from above, when launching the Report builder, enter the same credentials as your special user that was created and be sure to check the "Remember Me" checkbox for good measure.

Cannot create a connection to data source ''dataSource1''.

I successfully created the a Report model and deployed it to the server. When i run the a simple report on the SQL Server where reporting Services is installed it runs fine. When I run the report from anywhere else, I get the error below. I don't have a datasource called 'dataSource1'.

*******************************************************************

For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Cannot create a connection to data source 'dataSource1'.
-
An error has occurred during report processing.

*******************************************************************

Thanks for any help!

Most likely, you configured the data source credentials to use "Windows Integrated Security".

If you turn on remote errors (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=230593&SiteID=1), you would actually see the inner exception message which is most likely about a failed logon.

Windows Integrated Security only works if your domain has Kerberos-delegation enabled - otherwise you will need to store credentials on the report server (more details: http://msdn2.microsoft.com/en-us/library/ms160330(SQL.90).aspx)

-- Robert

|||

This is what I did to solve the error (just kept Windows Integrated Security enabled):

Changed the connection string.

From: SQLNCLI.1;Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True
To: Data Source=SERVER;Initial Catalog=DATABASE;Integrated Security=True

This solved the 'Cannot find dataSource1 datasource' error.

|||

My heart goes out to anyone that has to deal with this message: Cannot create a connection to data source 'dataSource1'. Hopefully, this will help fix your issue. My configuration consists of 2 servers, both Win2003, no domain, one has the production database, the other has all reporting services including the report builder. I would get the message when I hit the "Run Report" button in Report builder. The problem has to do with passing credentials from the server that launches report builder to the server that hosts the data. The datasource1 is an internal datasource so don't bother looking for it. If you look in the trace logs it's passing ANONYMOUS LOGON, which has no permissions. So, to fix first create a user with Admin privileges with the same credentials on both servers. In IIS of the Reports server, go to Directory Security, Edit, and Enable Anonymous Access, place your user in the username/password boxes. Do not check integrated Windows authentication. Go into your report manager to configure your data sources. I have 2, one for report builder and one for report execution, but doesn't matter because they are both the same. For the data source(s), enter your connection string like this: Data Source=DBSERVER;Initial Catalog=DB;Integrated Security=True
Then click on Credentials stored securely in the report server, enter your user name and password of the same user as above. (I gave this user admin priviliges on both boxes, and added this user as a login to the SQL Server database for the database server.)
Below the username/password there are two checkboxes: Check the "Use as Windows Credentials when Connecting to the Data source" and leave the "Impersonate" unchecked. Think of it this way, you're creating the same user all the way through, IIS uses it, then Reporting Services uses it, then your DB server uses it, and finally SQL Server (where data is stored) uses it. This way there are no credential storing/passing problems, good luck!! jwf

|||...one more thing from above, when launching the Report builder, enter the same credentials as your special user that was created and be sure to check the "Remember Me" checkbox for good measure.