cannot establish a connection in sql server 2005 express

hi all

here is the following error, what should i do.

TITLE: Connect to Server

Cannot connect to KANGALERT\SQLEXPRESS.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

Hi,

Please make sure you've followed all of the steps at http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx in order to enable remote connectivity.

Thanks

Cannot drop Temporary Table linked to Connection

Hi there!

I have a Java-Servlet that opens a connection to a SQL-Server 2000
With this connection I create a temporary local table.
I can call the temporary table within this connection as often as I want ... it's there as long as the connection is open. It's not dropped automatically as long as the connection is open. But when want to drop that table MANUALLY, I get a

[Microsoft][SQLServer JDBC Driver][SQLServer]Cannot drop the table '#tablename', because it does not exist in the system catalog.

I don't use any stored procedures that could drop the table before I do.
The database is accessed only by "normal" sql-statements through the JDBC-Driver. I can read the content of the table 10 times but if I try to drop it just in the next line, I get the above error message.

Now I know that the table will be dropped as soon as I close the connection, but anyway it's safer to do it manually ... so has somebody an idea?

Thanks

LookDo you need repeated access to the temp table or is it used just once ? Also, can you send the code you are using ? Is it straight sql or are you using a stored procedure (it appears that you are doing straight sql)?|||Found this in MSDN. Look for the article "Coding T-SQL like an Expert"

IF (object_id('tempdb..#mytemp') IS not Null)
Drop Table #mytemp

Although `tempdb..#authors_temp' is a truncation of the actual physical name of the object as held in tempdb..sysobjects, somehow OBJECT_ID() recognizes that you mean "your" temporary table called #mytemp.

Cannot Debug SQL 2005 Stored Procedures in VS 2005

I am having trouble in consistently debugging T-SQL stored procedures in SQL
2005 using VS 2005 Pro. I have enabled debugging on the connection in the
Server Explorer and enable CLR Integration in the Surface Area Configuration
tool. At one point I could step into the sproc but now I cannot. What has
gone wrong. How can I be able to consistently debug T-SQL sprocs?
Any input would be appreciated."=?Utf-8?B? RWFnbGVSZWRASGlnaEZseWluZ0JpcmRzLmNvbQ==
?="
<EagleRedHighFlyingBirdscom@.discussions.microsoft.com> wrote in
news:2EC86A08-79A4-44CC-ABDF-72DAE46D1BF0@.microsoft.com:

> I am having trouble in consistently debugging T-SQL stored procedures
> in SQL 2005 using VS 2005 Pro. I have enabled debugging on the
> connection in the Server Explorer and enable CLR Integration in the
> Surface Area Configuration tool. At one point I could step into the
> sproc but now I cannot. What has gone wrong. How can I be able to
> consistently debug T-SQL sprocs?
>
Hmm, in order to debug T-SQL proc's you should not have to do any
enabling at all.
1. Open VS 2005
2. Open Server Explorer
3. Create a connection to the database the proc is in
4. Expand the database and drill down to Stored Procedures, expand.
5. Right click on the proc and choose "Step Into Stored Procedure".
6. Debug
What happens for you when you try the above?
Niels
****************************************
**********
* Niels Berglund
* http://staff.develop.com/nielsb
* nielsb@.no-spam.develop.com
* "A First Look at SQL Server 2005 for Developers"
* http://www.awprofessional.com/title/0321180593
****************************************
**********|||The debugger starts but when I either step into or step to the next statemen
t
in the proc the proc runs to completion. I have set a breakpoint in the pro
c
only to have it disabled when debugging starts.
"EagleRed@.HighFlyingBirds.com" wrote:

> I am having trouble in consistently debugging T-SQL stored procedures in S
QL
> 2005 using VS 2005 Pro. I have enabled debugging on the connection in the
> Server Explorer and enable CLR Integration in the Surface Area Configurati
on
> tool. At one point I could step into the sproc but now I cannot. What ha
s
> gone wrong. How can I be able to consistently debug T-SQL sprocs?
> Any input would be appreciated.|||Here's some additional information. The disabled breakpoint displays a
tooltip that says the breakpoint will not be hit because the object
containing the breakpoint has not been loaded. What's going on? I have bee
n
able to debug and hit breakpoints, but I cannot do it consistently and right
now it simply isn't working.
"Niels Berglund" wrote:

> "=?Utf-8?B? RWFnbGVSZWRASGlnaEZseWluZ0JpcmRzLmNvbQ==
?="
> <EagleRedHighFlyingBirdscom@.discussions.microsoft.com> wrote in
> news:2EC86A08-79A4-44CC-ABDF-72DAE46D1BF0@.microsoft.com:
>
> Hmm, in order to debug T-SQL proc's you should not have to do any
> enabling at all.
> 1. Open VS 2005
> 2. Open Server Explorer
> 3. Create a connection to the database the proc is in
> 4. Expand the database and drill down to Stored Procedures, expand.
> 5. Right click on the proc and choose "Step Into Stored Procedure".
> 6. Debug
> What happens for you when you try the above?
> Niels
> --
> ****************************************
**********
> * Niels Berglund
> * http://staff.develop.com/nielsb
> * nielsb@.no-spam.develop.com
> * "A First Look at SQL Server 2005 for Developers"
> * http://www.awprofessional.com/title/0321180593
> ****************************************
**********
>

cannot create connection

I created a report using Report Designer. The Dataset is working fine. In
fact, the Data tab shows me the expected query result. But...
when going to the Preview tab, I get "Cannot create a connection to data
source <name> . Login failed for user 'sa'.
Further info:
1) if I go to Tools / Connect to database and enter the info in "Datalink
properties" (server name / specific user name passw / database name) and hit
Test connection, I get "Connection succeeded"
2) During creation of data source for a SQL Server machine on the network
when connecting with winNT security I get an error while trying to access the
database list.
What am I doing wrong ' THnksHi,
Go to your "Shared Data Sources" click on the datasource you use for your
reports, open the properties by double clicking on the "credientials" tab
enter your password again and save it.
It should work.
Amarnath
"julio" wrote:
> I created a report using Report Designer. The Dataset is working fine. In
> fact, the Data tab shows me the expected query result. But...
> when going to the Preview tab, I get "Cannot create a connection to data
> source <name> . Login failed for user 'sa'.
> Further info:
> 1) if I go to Tools / Connect to database and enter the info in "Datalink
> properties" (server name / specific user name passw / database name) and hit
> Test connection, I get "Connection succeeded"
> 2) During creation of data source for a SQL Server machine on the network
> when connecting with winNT security I get an error while trying to access the
> database list.
> What am I doing wrong ' THnks
>|||Amarnath,
thanks a lot. It works like a charm.
Julio
"Amarnath" wrote:
> Hi,
> Go to your "Shared Data Sources" click on the datasource you use for your
> reports, open the properties by double clicking on the "credientials" tab
> enter your password again and save it.
> It should work.
> Amarnath
>
> "julio" wrote:
> > I created a report using Report Designer. The Dataset is working fine. In
> > fact, the Data tab shows me the expected query result. But...
> >
> > when going to the Preview tab, I get "Cannot create a connection to data
> > source <name> . Login failed for user 'sa'.
> >
> > Further info:
> >
> > 1) if I go to Tools / Connect to database and enter the info in "Datalink
> > properties" (server name / specific user name passw / database name) and hit
> > Test connection, I get "Connection succeeded"
> >
> > 2) During creation of data source for a SQL Server machine on the network
> > when connecting with winNT security I get an error while trying to access the
> > database list.
> >
> > What am I doing wrong ' THnks
> >
> >

Cannot create an ODBC connection to SQl 2000.

Hi all,

I have SQL 2000 enterprise edition(no service pack) installed on a Windows Server 2003 machine. I can remote access into the server and run SQL but I cannot create an ODBC connection to this from my desktop. From some research it looks like installing service packs might correct this but here is the error:

--connection failed

--sqlstate '01000'

--sql server error 10061

--connection failed

--sqlstate 08001

--sql server error 17

--SQL server does not exist or access denied

Any help would be appreciated.

Verify whether the SQL Server is listening on a TCP port. If it's a default instance it is by default 1433, so you can use

netstat -an | findstr 1433

If not but the TCP protocol is turned on for the server (and set to port 1433) then upgrading to the latest service pack will most likely solve your problem.

|||

It'd better for you to upgrade SQL Server 2000 to latest service pack 4 from here:

http://support.microsoft.com/kb/290211#EOADAA

then make sure following things before you make connection:

1) SQL Service is running

2) If make remote connection, make sure named pipe or TCP was enabled and try Peter's suggestion if you want to connect through tcp.

HTH.

Cannot create ADO connection to DB anymore...

I rebuilt my machine a few weeks back - re-installed the developer version...

The app in question can see all it's tables in the SQL back end via ODBC and
everything looks normal via Enterprise Manager, but I can no longer create
an ADO Connection.

Source code is unchanged, what's changed is the PC rebuild and consequent
re-installatin of SQL Server developer version.

I suspect it's something to do with the provider (at least that's the only thing
I can see in the .Connect string that's not verifiably correct...)

The error looks like this after I trap and format it:

--------------------
12/30/03 21:34:30v0.71 Userid: UPQC on SAG
Proc: basADO: ADO_ConnectionCreate
-2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Errors encountered when trying to connect:
'''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.

----Connect String:
Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID= Trets;PWD=trets
--------------------

Can anybody see anything obvious to look for?

I'm thinking I need to know how to verify/validate the presence of provider
"SQLOLEDB.1"... But how?
--
PeteCresswellHi

Maybe it's a SID type problem! Have you tried a trusted connection?

John

"(Pete Cresswell)" <x@.y.z> wrote in message
news:lkd4vv89m3cdb5fnlt4rt661c47sb56jdv@.4ax.com...
> I rebuilt my machine a few weeks back - re-installed the developer
version...
> The app in question can see all it's tables in the SQL back end via ODBC
and
> everything looks normal via Enterprise Manager, but I can no longer create
> an ADO Connection.
> Source code is unchanged, what's changed is the PC rebuild and consequent
> re-installatin of SQL Server developer version.
> I suspect it's something to do with the provider (at least that's the only
thing
> I can see in the .Connect string that's not verifiably correct...)
> The error looks like this after I trap and format it:
> --------------------
> 12/30/03 21:34:30v0.71 Userid: UPQC on SAG
> Proc: basADO: ADO_ConnectionCreate
> -2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL
Server does
> not exist or access denied.
> Errors encountered when trying to connect:
> '''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
or
> access denied.
> ----Connect String:
> Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID= Trets;PWD=trets
> --------------------
>
> Can anybody see anything obvious to look for?
> I'm thinking I need to know how to verify/validate the presence of
provider
> "SQLOLEDB.1"... But how?
> --
> PeteCresswell

Cannot create ADO connection to DB anymore.

This is a semi-crosspost - tried it on comp.databases.ms-sqlserver, but haven't
made any progress. Meanwhile, I'm getting desperate...Client wants some
changes to an app and I can't get the thing running.
I guess my primary quesion has become: "How do I confirm that
Provider=SQLOLEDB.1 us installed and functioning on my system?"
--
I rebuilt my machine a few weeks back - re-installed the developer version...
The app in question can see all it's tables in the SQL back end via ODBC and
everything looks normal via Enterprise Manager, but I can no longer create
an ADO Connection.
Source code is unchanged, what's changed is the PC rebuild and consequent
re-installatin of SQL Server developer version.
I suspect it's something to do with the provider (at least that's the only thing
I can see in the .Connect string that's not verifiably correct...)
The error looks like this after I trap and format it:
---
12/30/03 21:34:30v0.71 Userid: UPQC on SAG
Proc: basADO: ADO_ConnectionCreate
-2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does
not exist or access denied.
Errors encountered when trying to connect:
'''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied.
--Connect String:
Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID=Trets;PWD=trets
---
Can anybody see anything obvious to look for?
I'm thinking I need to know how to verify/validate the presence of provider
"SQLOLEDB.1"... But how?
--
PeteCresswell
--
PeteCresswellPete,
Yes, it looks like SQLOLEDB version 1 is no longer installed on that box.
Is there a particular reason why you need version 1?
If not, use what's known as the "VersionIndependentProgID",
simply: SQLOLEDB and this will use the latest version installed on the
machine.
James Hokes
"(Pete Cresswell)" <x@.y.z> wrote in message
news:dum6vv4e67q257m22kemdttda3h7pjmub2@.4ax.com...
> This is a semi-crosspost - tried it on comp.databases.ms-sqlserver, but
haven't
> made any progress. Meanwhile, I'm getting desperate...Client wants some
> changes to an app and I can't get the thing running.
> I guess my primary quesion has become: "How do I confirm that
> Provider=SQLOLEDB.1 us installed and functioning on my system?"
>
> --
> I rebuilt my machine a few weeks back - re-installed the developer
version...
> The app in question can see all it's tables in the SQL back end via ODBC
and
> everything looks normal via Enterprise Manager, but I can no longer create
> an ADO Connection.
> Source code is unchanged, what's changed is the PC rebuild and consequent
> re-installatin of SQL Server developer version.
> I suspect it's something to do with the provider (at least that's the only
thing
> I can see in the .Connect string that's not verifiably correct...)
> The error looks like this after I trap and format it:
> ---
> 12/30/03 21:34:30v0.71 Userid: UPQC on SAG
> Proc: basADO: ADO_ConnectionCreate
> -2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL
Server does
> not exist or access denied.
> Errors encountered when trying to connect:
> '''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
or
> access denied.
> --Connect String:
> Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID=Trets;PWD=trets
> ---
>
> Can anybody see anything obvious to look for?
> I'm thinking I need to know how to verify/validate the presence of
provider
> "SQLOLEDB.1"... But how?
> --
> PeteCresswell
> --
> PeteCresswell|||RE/
>Yes, it looks like SQLOLEDB version 1 is no longer installed on that box.
>Is there a particular reason why you need version 1?
>If not, use what's known as the "VersionIndependentProgID",
>simply: SQLOLEDB and this will use the latest version installed on the
>machine.
Excellant suggestin in it's own right - I've been doing a lot of this stuff by
rote and didn't think about versioning...
Removed the version, same error - which suggests to me that there's no provider
of that name on the box.
Any idea how to install one? I'm guessing it's a download from the MS Web site
or my MSDN DVD set...but am a little leery of just "try this...try that..." for
fear of hosing the installation completely.
--
PeteCresswell|||Pete,
You might want to download microsoft's MDAC Checker. It does sound like
something's hosed - most likely just need to install the latest MDAC. That
will tell you if you have any mis-matched or missing files.
Here's a URL that tells what to do:
http://support.microsoft.com/default.aspx?kbid=301202&product=mdac
James Hokes
"(Pete Cresswell)" <x@.y.z> wrote in message
news:sl79vvo56du1nhspao0uoasmqdohfvcjna@.4ax.com...
> RE/
> >Yes, it looks like SQLOLEDB version 1 is no longer installed on that box.
> >
> >Is there a particular reason why you need version 1?
> >If not, use what's known as the "VersionIndependentProgID",
> >simply: SQLOLEDB and this will use the latest version installed on the
> >machine.
> Excellant suggestin in it's own right - I've been doing a lot of this
stuff by
> rote and didn't think about versioning...
> Removed the version, same error - which suggests to me that there's no
provider
> of that name on the box.
> Any idea how to install one? I'm guessing it's a download from the MS Web
site
> or my MSDN DVD set...but am a little leery of just "try this...try
that..." for
> fear of hosing the installation completely.
> --
> PeteCresswell|||(Pete Cresswell) (x@.y.z) writes:
> The app in question can see all it's tables in the SQL back end via ODBC
> and everything looks normal via Enterprise Manager, but I can no longer
> create an ADO Connection.
> Source code is unchanged, what's changed is the PC rebuild and consequent
> re-installatin of SQL Server developer version.
> I suspect it's something to do with the provider (at least that's the
> only thing I can see in the .Connect string that's not verifiably
> correct...)
> The error looks like this after I trap and format it:
> ---
> 12/30/03 21:34:30v0.71 Userid: UPQC on SAG
> Proc: basADO: ADO_ConnectionCreate
> -2147467259: [DBNETLIB][ConnectionOpen (Connect()).]SQL
> Server does not exist or access denied.
> Errors encountered when trying to connect:
> '''[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
> or access denied.
> --Connect String:
> Provider=SQLOLEDB.1;SERVER=SAG;DATABASE=TRETS;UID=Trets;PWD=trets
> ---
The idea that SQLOLEDB should be missing seems to be an incorrect path
to me. In that case you would get a different message. To see what,
try Provider=NISSE.
No, the problem is that the SQL Server SAG cannot be be found. What happens
if you try connect to SAG from Query Analyzer or OSQL?
You may have to add SAG as an alias in the Client Network Utility.
Another possibility is that you have not enabled the network library
that SAG is listening to. Again, this can be checked in the Client
Network Utility. And in the Server Netowrk Utility on SAG, if you have
access to that machine.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||RE/
>The idea that SQLOLEDB should be missing seems to be an incorrect path
>to me. In that case you would get a different message. To see what,
>try Provider=NISSE.
" Error# 3706: Provider cannot be found. It may not be properly installed."
Sounds like you're correct.
>No, the problem is that the SQL Server SAG cannot be be found. What happens
>if you try connect to SAG from Query Analyzer or OSQL?
Dunno what OSQL is, but no problems at all using Query Analyser to do a SELECT *
FROM tlkpVendor... or using Enterprise Manager to open the same table,
returning all records
>You may have to add SAG as an alias in the Client Network Utility.
*Seems* to already be there.
>Another possibility is that you have not enabled the network library
>that SAG is listening to. Again, this can be checked in the Client
>Network Utility. And in the Server Netowrk Utility on SAG, if you have
>access to that machine.
Could you elaborate on that one - seems like the last possibility.
The only enabled protocols I've got are Named Pipes and TCP/IP - but that's what
I'd expect. Both utilities you've mentioned show these two protocols.
--
PeteCresswell|||(Pete Cresswell) (x@.y.z) writes:
> Dunno what OSQL is, but no problems at all using Query Analyser to do a
> SELECT * FROM tlkpVendor... or using Enterprise Manager to open the
> same table, returning all records
Don't know what OSQL is? Hey, Pete, how long have you been working with
SQL Server? It must be over year by now, isn't it?
Sorry, couldn't resist. OSQL is a command-line utility for queries, a more
primitive Query Analyzer if you like. Mainly useful if you want run
prepared SQL scripts from batch files.
Anyway, it is mysterious that you can access the server from the tools,
but not from the application code. This means that we can forget about
the network protocols that I discussed in my previous posting.
Connectivity problems are not my best game, so I'm fairly clueless
myself. The one difference with regards to the tools is that the
tools connect through ODBC and not OLE DB. But I cannot see that it
should matter. You could try to replace "Provider=SQLOLEDB" with
"Driver={SQL Server}", this will change provider to MSDASQL, OLE DB
over ODBC. But this is a poorer alternative, so we don't want to use
that.
Hm, you could also try changing SERVER= into Data Source=, which I
believe is the proper name for OLE DB.
No fantastic tips - I'm just clutching at straws.
--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||RE/
>No fantastic tips - I'm just clutching at straws.
Thanks for trying - I need anything I can get.
Tried the various Provider/Driver combinations, still no luck.
Changed my connect string to use the SA id/pw and no change.
I'm starting to grasp at my own straw: ADO...maybe there's something amiss
with my ADO. If ODBC works and Enterprise Manager can connect, what's left?
--
PeteCresswell|||RE/
>straws
Oh yeah...I re-installed the MDAC. Put 2.8 over top of 2.6.
Everything else still works: ODBC, Enterprise Manager...
--
PeteCresswell

Cannot create a valid ODBC DSN to SQL Server Express

Hello All,

I've just spent the better part of a day trying to configure SQL Express to allow me to create an ODBC connection. When I do create one via Control Panel/Admin/ODBC it tells me that its timing out on the connection (localhost) and the problem is probably that SQL Server Express comes configured NOT to allow remote connections. I've enabled TCP/IP and named pipes, allowed remote connections, enabled the SQL Browser, and just about everything I;ve read in the docs and forums.

Am I missing the obvious?

Kind Regards,

Pat.

Pat,

I guess you are using (localhost) as the target server which is invalid. Either you can use (local)\sqlexpress or localhost\sqlexpress to connect to local sql express instance, a name instance.

Thanks,

Nan

|||

Nan,

You are bang on! Thank you very much.

I've created a test user database, but when i attempt to "get external data/link tables" in access, I can't see my database, only all the system tables.

Any thoughts?

Kind Regards,

Pat.

|||

Did you specify your database name while creating DSN?

It's under 'Change the default dabase to' checkbox.

|||

Thank you, gavrilenko_s - that did it.

To both you and Nan, if in Dublin, send me an email - there are pints of guinness woith your names on them.

appreciatively,

Pat Backowski

Consider this thread closed and solved - well done, lads!

|||Holy Telemundo, Batman! If I hadn't found this thread, I was seriously considering just using MySQL for my app. I've talked to a few guys who have had this problem too. You may want to include a hint about this solution in the next revision of the connectivity tools so people don't go wasting so much time on what could have been a simple solution.

Cannot create a valid ODBC DSN to SQL Server Express

Hello All,

I've just spent the better part of a day trying to configure SQL Express to allow me to create an ODBC connection. When I do create one via Control Panel/Admin/ODBC it tells me that its timing out on the connection (localhost) and the problem is probably that SQL Server Express comes configured NOT to allow remote connections. I've enabled TCP/IP and named pipes, allowed remote connections, enabled the SQL Browser, and just about everything I;ve read in the docs and forums.

Am I missing the obvious?

Kind Regards,

Pat.

Pat,

I guess you are using (localhost) as the target server which is invalid. Either you can use (local)\sqlexpress or localhost\sqlexpress to connect to local sql express instance, a name instance.

Thanks,

Nan

|||

Nan,

You are bang on! Thank you very much.

I've created a test user database, but when i attempt to "get external data/link tables" in access, I can't see my database, only all the system tables.

Any thoughts?

Kind Regards,

Pat.

|||

Did you specify your database name while creating DSN?

It's under 'Change the default dabase to' checkbox.

|||

Thank you, gavrilenko_s - that did it.

To both you and Nan, if in Dublin, send me an email - there are pints of guinness woith your names on them.

appreciatively,

Pat Backowski

Consider this thread closed and solved - well done, lads!

|||Holy Telemundo, Batman! If I hadn't found this thread, I was seriously considering just using MySQL for my app. I've talked to a few guys who have had this problem too. You may want to include a hint about this solution in the next revision of the connectivity tools so people don't go wasting so much time on what could have been a simple solution.

Cannot create a connection to the datasource 'DataSource1'

Hello, I Created a report with reportbuilder, after clicking on Run Report I got this message, Its very strange it seems that its trying to generate or create a datasource.

Para obtener más información acerca de este error, vaya al servidor de informes en el equipo del servidor local o habilite los errores remotos
-
No se puede crear una conexión al origen de datos 'dataSource1'.
-
Error al procesar el informe.

Hello,

This error means that the connection could not be established with the information provided in the data source element, named 'dataSource1', which is in the RDL that report builder creates.

There should be more information regarding why this error occurred in the log files. See the following link on how to locate the log files.

http://msdn2.microsoft.com/en-us/library/ms157403.aspx

Ian

Cannot create a connection to data source 'myservername'.

No matter how many times I redeploy my report and data sources from my
project to Report Manager, I keep getting this error when trying to run
the report from Reprt manager. It runs fine in VS 2005 though. I
don't know what else to do. I see no way to delete the report from
Report Manager in attempts to try to redeploy it from scratch either.
"An error has occurred during report processing.
Cannot create a connection to data source 'myservername'.
For more information about this error navigate to the report server on
the local server machine, or enable remote errors "In report manager on the datasource properties, credentials tab and set the
credentials to be used. Then when deploying do not overwirte the datasource
(this is the default behavior, to not overwrite the source).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"dba123" <d_schinkel@.hotmail.com> wrote in message
news:1141683199.061931.270510@.u72g2000cwu.googlegroups.com...
> No matter how many times I redeploy my report and data sources from my
> project to Report Manager, I keep getting this error when trying to run
> the report from Reprt manager. It runs fine in VS 2005 though. I
> don't know what else to do. I see no way to delete the report from
> Report Manager in attempts to try to redeploy it from scratch either.
>
> "An error has occurred during report processing.
> Cannot create a connection to data source 'myservername'.
> 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 'mydatasourcename'.

No matter how many times I redeploy my report and data sources from my project to Report Manager, I keep getting this error when trying to run the report from Reprt manager. It runs fine in VS 2005 though. I don't know what else to do. I see no way to delete the report from Report Manager in attempts to try to redeploy it from scratch either.

An error has occurred during report processing.

Cannot create a connection to data source 'myservername'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Report manager has an icon in the toolbar to toggle between list view (default view) and detail view. In the detail view, you can select a report and delete it.

One reason why the connection could fail is that you are using Windows Integrated Security, but Kerberos is not set up for delegation.

-- Robert

|||I'm having the same problem. But how do I fix it without deleting my reports?|||

If your report server and the database used to get report data are not on the same machine,

1. Enable Kerberos protocol so that credentials can be delegated to other computers without limit.

2. If enabling Kerberos is not an option, consider using either stored credentials or a combination of Windows Authentication and database authentication. For example, you can use Windows Authentication to connect a client to a report server, and then configure the report to use database authentication to access an external data source. For this use a specific username and password in the credentials tab of data source designer. The report server will use the specific credential to access the database server.

Another option is to locate the report data sources on the same computer that hosts the report server.

Cannot create a connection to data source 'mydatasourcename'.

No matter how many times I redeploy my report and data sources from my project to Report Manager, I keep getting this error when trying to run the report from Reprt manager. It runs fine in VS 2005 though. I don't know what else to do. I see no way to delete the report from Report Manager in attempts to try to redeploy it from scratch either.

An error has occurred during report processing.

Cannot create a connection to data source 'myservername'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Report manager has an icon in the toolbar to toggle between list view (default view) and detail view. In the detail view, you can select a report and delete it.

One reason why the connection could fail is that you are using Windows Integrated Security, but Kerberos is not set up for delegation.

-- Robert

|||I'm having the same problem. But how do I fix it without deleting my reports?|||

If your report server and the database used to get report data are not on the same machine,

1. Enable Kerberos protocol so that credentials can be delegated to other computers without limit.

2. If enabling Kerberos is not an option, consider using either stored credentials or a combination of Windows Authentication and database authentication. For example, you can use Windows Authentication to connect a client to a report server, and then configure the report to use database authentication to access an external data source. For this use a specific username and password in the credentials tab of data source designer. The report server will use the specific credential to access the database server.

Another option is to locate the report data sources on the same computer that hosts the report server.

Cannot create a connection to data source 'dsInvent'

I get this error message when connecting through IE to a report. We have a
sepererate Report Server and the database to which we are reporting from.
When I go to the report server logged on using the same account as my
workstation I can access the report. I have tried making it a shared data
source with the same problem.
The report does work if I enter my credentials and select use Integrated
Security in Report Manager/Properties/Data Sources. Is this required and the
only way to make it work? This would seem to be a pain cause every time a
user changes thier password you would need to change it there as well.
TIA,
SteveAre you trying to connect to SQL Server 2000 database, and are you in an
Active Directory domain?
You should be able to
- Create a AD usergroup with all the users that are supposed to view the
reports
- Add this group as a login to SQL Server, and give it Read access to the
datasource
- Set up your datasource in Report Manager as Windows NT Integrated Security
This way it should pick up the user name of the user logged in on the
machine, check the AD properties of this user, and use them against the SQL
Server, which will give the users the data they are entitled to see in the
database.
Alternatively, set up your datasource using "Credentials stored securely..."
and use a SQL Server login that have the right access rights in your SQL
Server database.
Kaisa
"Steve Wofford" <IntraRELY@.yahoo.com> wrote in message
news:%23zjMHQpBGHA.3936@.TK2MSFTNGP12.phx.gbl...
>I get this error message when connecting through IE to a report. We have a
>sepererate Report Server and the database to which we are reporting from.
> When I go to the report server logged on using the same account as my
> workstation I can access the report. I have tried making it a shared data
> source with the same problem.
> The report does work if I enter my credentials and select use Integrated
> Security in Report Manager/Properties/Data Sources. Is this required and
> the only way to make it work? This would seem to be a pain cause every
> time a user changes thier password you would need to change it there as
> well.
> TIA,
> Steve
>|||We are using:
Reporting Server 2005 (Seperate Server)
Reporting Database - 2000
Reporting Data Database - 2000 (This is where the report data will be
pulled from)
My account is a domain admin and all system belong to this same domain. I
can execute the query the report uses w/in Query Analyzer and can run the
report from VS. When I logon locally to the report server, I can run the
report as well.
However, when I run the report from the same sysetm I dev the report using
VS, I cannot view the report data in IE, however the report is displayed w/o
data. The report runs when I enter my credentials and select use Integrated
Security in Report Manager/Properties/Data Sources.
the problem is that I didnt think this should be the case. why isnt my
security information persisting to the report data.
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> wrote in message
news:emdy%2325BGHA.1092@.TK2MSFTNGP09.phx.gbl...
> Are you trying to connect to SQL Server 2000 database, and are you in an
> Active Directory domain?
> You should be able to
> - Create a AD usergroup with all the users that are supposed to view the
> reports
> - Add this group as a login to SQL Server, and give it Read access to the
> datasource
> - Set up your datasource in Report Manager as Windows NT Integrated
> Security
> This way it should pick up the user name of the user logged in on the
> machine, check the AD properties of this user, and use them against the
> SQL Server, which will give the users the data they are entitled to see in
> the database.
> Alternatively, set up your datasource using "Credentials stored
> securely..." and use a SQL Server login that have the right access rights
> in your SQL Server database.
> Kaisa
>
> "Steve Wofford" <IntraRELY@.yahoo.com> wrote in message
> news:%23zjMHQpBGHA.3936@.TK2MSFTNGP12.phx.gbl...
>>I get this error message when connecting through IE to a report. We have a
>>sepererate Report Server and the database to which we are reporting from.
>> When I go to the report server logged on using the same account as my
>> workstation I can access the report. I have tried making it a shared data
>> source with the same problem.
>> The report does work if I enter my credentials and select use Integrated
>> Security in Report Manager/Properties/Data Sources. Is this required and
>> the only way to make it work? This would seem to be a pain cause every
>> time a user changes thier password you would need to change it there as
>> well.
>> TIA,
>> Steve
>

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 am getting this error from Report Builder
Cannot create a connection to data source 'dataSource1'.
Back end SQL 2000
Credentials stored securely in the report server
Login and password of the SQL login
The weird thing is pointing to another db on the same server works fine
--
Peter
Peter.freeborn@.halliburton.comHope you have created Report model, If not use report model to access reports
from builder.
If you have already created it check the datasource "test connection" in the
report model project.
If you are accessing directly from builder using "open report server file",
dont do it cause it will ask for datasource which you cannt include. So
create a model and then access.
Amarnath
"Peter" wrote:
> I am getting this error from Report Builder
> Cannot create a connection to data source 'dataSource1'.
> Back end SQL 2000
> Credentials stored securely in the report server
> Login and password of the SQL login
> The weird thing is pointing to another db on the same server works fine
>
> --
> Peter
> Peter.freeborn@.halliburton.com|||I've struck this problem, I did some digging around and it seems that this is
a problem with kerberos security. Basically if you store the credentials in
the report server then the report server can pass the credentials fine,
however on a remote server it can't unless you've set up kerberos and use
windows security.
Thats my understanding of the problem, however the error message doesn't
really lead you in that direction.
HTH
"Peter" wrote:
> I am getting this error from Report Builder
> Cannot create a connection to data source 'dataSource1'.
> Back end SQL 2000
> Credentials stored securely in the report server
> Login and password of the SQL login
> The weird thing is pointing to another db on the same server works fine
>
> --
> Peter
> Peter.freeborn@.halliburton.com

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 !!!!!!!

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

no it usues whatever account iis is running under.

IUSR_something I think.

if you want use integrated auth you need to use impersonation.

|||ok....then how do incorporate personalization in Reporting Services! I don't see anything on that...I think you're referring to .NET, I'm talking about Reporting Services 2005|||I posted this in the wrong forum by accident..I'll move it to Reporting Services..sorry