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.

Cannot connect to SQL2005

Hi,

This is the error I am getting - HELP

A connection was successfully established with the server, but an error occured during the login process(provider: TCP Provider - error 0 an existing connection was forcibily closed by the remote host. (Microsoft SQL server error: 10054).

I have checked the error code 10054 - at this link

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303120

it says it applies to SQL2000
Regards
SahilFor a faster response I suggest you post this to the SQL Server Data Access forum.

Dan

Cannot connect to SQL Servrer 2005 remotely using another account than sa

Hi there,
I set up an SQL Server 2005 Enterprise Edition, so it is listening on
the network.
I can login successfully from a remote machine using osql:
osql -H sqlhost -U sa
Password: XXX
1>
However I created another user "test" (SQL Auth.) and also a database
which test should be allowed to access but test cannot login remotely
(test _can_ login locally, for example in the management studio)
osql -H sqlhost -U test -d db_test
Password: XXX
Login failed for user 'test'.
What is strange about it, is that it doesn't even show up in the logs
that it did not work. There is no mention of the user "test" in the
logs when the remote login fails.
Any idea what to check? What am I doing wrong? :-(
Regards,
marcNote that you should use -S server_name\instance_name.
Perhaps you are connecting to a local instance.
Ben Nevarez, MCDBA, OCP
Database Administrator
"Marc" wrote:
> Hi there,
> I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> the network.
> I can login successfully from a remote machine using osql:
> osql -H sqlhost -U sa
> Password: XXX
> 1>
> However I created another user "test" (SQL Auth.) and also a database
> which test should be allowed to access but test cannot login remotely
> (test _can_ login locally, for example in the management studio)
> osql -H sqlhost -U test -d db_test
> Password: XXX
> Login failed for user 'test'.
> What is strange about it, is that it doesn't even show up in the logs
> that it did not work. There is no mention of the user "test" in the
> logs when the remote login fails.
> Any idea what to check? What am I doing wrong? :-(
> Regards,
> marc
>|||When you are using 'osql -H sqlhost -U sa' without -S you are connecting to
the default instance on the local computer. Try it and run this to verify
select @.@.servername
go
Ben Nevarez, MCDBA, OCP
Database Administrator
"Ben Nevarez" wrote:
> Note that you should use -S server_name\instance_name.
> Perhaps you are connecting to a local instance.
> Ben Nevarez, MCDBA, OCP
> Database Administrator
>
> "Marc" wrote:
> > Hi there,
> > I set up an SQL Server 2005 Enterprise Edition, so it is listening on
> > the network.
> > I can login successfully from a remote machine using osql:
> >
> > osql -H sqlhost -U sa
> > Password: XXX
> > 1>
> >
> > However I created another user "test" (SQL Auth.) and also a database
> > which test should be allowed to access but test cannot login remotely
> > (test _can_ login locally, for example in the management studio)
> >
> > osql -H sqlhost -U test -d db_test
> > Password: XXX
> > Login failed for user 'test'.
> >
> > What is strange about it, is that it doesn't even show up in the logs
> > that it did not work. There is no mention of the user "test" in the
> > logs when the remote login fails.
> >
> > Any idea what to check? What am I doing wrong? :-(
> >
> > Regards,
> > marc
> >
> >|||Yes you are right! Thanks!!