I am in desperate need of help.
We have just set up SQL Server (2005, SP2) with RS on a Windows 2003 server.
None of us have ever deployed RS before. To make matters worse, all of our
network operations have been outsourced, so we do not have control of the
machine and the people who do don't know what they're doing either.
I can browse to <servername>\reports and to
<servername>\reportexecution2005.asmx. However when I try to browse to
<servername>\reportserver or try to deploy reports from VS2003, I get the
following error: The permissions granted to user 'ADSDOMAIN\ERichardson' are
insufficient for performing this operation. (rsAccessDenied) .
a)How should the permissions be set up so that I can deploy and manage the
reports?
b)How should the permissions be set up so that certain users can access the
Report Manager?
c)How should the permission be set up so that the majority of users can
access reports through links in the VS.Net application?
I know this is a lot of material to cover at once. We've got the blind
leading the blind here. Maybe we could start with how to grant me access to
deploy and manage the reports and then take it from there.
I would appreciate any help I can get. These outsourced people aren't going
to make the effort to figure this out. We're going to have to spoonfeed
them:-)
LizOn Sep 10, 12:40 pm, Liz <L...@.discussions.microsoft.com> wrote:
> I am in desperate need of help.
> We have just set up SQL Server (2005, SP2) with RS on a Windows 2003 server.
> None of us have ever deployed RS before. To make matters worse, all of our
> network operations have been outsourced, so we do not have control of the
> machine and the people who do don't know what they're doing either.
> I can browse to <servername>\reports and to
> <servername>\reportexecution2005.asmx. However when I try to browse to
> <servername>\reportserver or try to deploy reports from VS2003, I get the
> following error: The permissions granted to user 'ADSDOMAIN\ERichardson' are
> insufficient for performing this operation. (rsAccessDenied) .
> a)How should the permissions be set up so that I can deploy and manage the
> reports?
> b)How should the permissions be set up so that certain users can access the
> Report Manager?
> c)How should the permission be set up so that the majority of users can
> access reports through links in the VS.Net application?
> I know this is a lot of material to cover at once. We've got the blind
> leading the blind here. Maybe we could start with how to grant me access to
> deploy and manage the reports and then take it from there.
> I would appreciate any help I can get. These outsourced people aren't going
> to make the effort to figure this out. We're going to have to spoonfeed
> them:-)
> Liz
For Item (a), you may want to check the security on the Reports and
ReportServer Virtual Directories. You may want to change the Directory
Security (via right-clicking the virtual directories in IIS ->
Properties -> Directory Security tab -> Edit... button -> select
'Anonymous access' and 'Integrated Windows Authentication').
For Item (b), you set the user permissions in the Report Manager in
the second tab on the main page (I don't remember the name of it). You
can allow Browse, Publish, etc for various users that you add (note
that the standard windows format is: DOMAIN\User).
For Item (c), Browse permissions should be sufficient for most users
(refer to Item (b) response).
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant
Showing posts with label deployed. Show all posts
Showing posts with label deployed. Show all posts
Sunday, March 25, 2012
Thursday, March 8, 2012
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
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
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
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
Subscribe to:
Posts (Atom)