Connection problems: connecting

Showing posts with label connecting. Show all posts

Sunday, March 25, 2012

conntectionString Question Please

I'm having problems connecting Efficon's Advanced DataGrid to the database in DNN3.
Can someone help me with the syntax for the connection string?
Thanks in advance,
ScottTry http://www.connectionstrings.com for help on connection strings.
|||Resolution:
Connection Sting
Provder=SQLOLEDB
Trusted_Connection= yes (trusted_connection=true did not work)
sql sql

Thursday, March 22, 2012

Connectivity Issues

We’re having a problem with our web applications connecting to the SQL DB
virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
front-end web servers are Win2K, IIS 5. The web servers and the database
server reside on the same LAN and the front end can ping the backend using
either IP or SQL cluster name successfully.
The clustering is functioning properly and has passed all failover testing
scenarios including the SQL Server resources. The ASP code is using a
Globaldb include file to point to a production database. When I point any of
3 web servers to a single SQL server offering the same exact databases,
users, logins, etc., IE makes the connections with no problem. When
attempting to do the same to the clustered virtual server, we get either a
“500 Internal Server” error or a blank page that says “Done” on the IE status
bar at the bottom of the window. No connection to the database is completed
Is there something we are missing to make this connection work? What can I
look at?
Thank you very much.
Apply MDAC 2.8 to all your client machines. Early versions of MDAC were not
instance aware. Cluster names (VitrualServerName\InstanceName) use the same
syntax as multi-instance SQL servers and look the same on an network.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Fonkberry" <Fonkberry@.discussions.microsoft.com> wrote in message
news:296ABC73-4A0B-44BC-8221-F5498C903DDD@.microsoft.com...
> We're having a problem with our web applications connecting to the SQL DB
> virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
> front-end web servers are Win2K, IIS 5. The web servers and the database
> server reside on the same LAN and the front end can ping the backend using
> either IP or SQL cluster name successfully.
> The clustering is functioning properly and has passed all failover testing
> scenarios including the SQL Server resources. The ASP code is using a
> Globaldb include file to point to a production database. When I point any
of
> 3 web servers to a single SQL server offering the same exact databases,
> users, logins, etc., IE makes the connections with no problem. When
> attempting to do the same to the clustered virtual server, we get either a
> "500 Internal Server" error or a blank page that says "Done" on the IE
status
> bar at the bottom of the window. No connection to the database is
completed
> Is there something we are missing to make this connection work? What can I
> look at?
> Thank you very much.
>

Connectivity from Client to Server

Hai,

I am often getting the message

"SQL Server does not exist or access denied (Connection Open (Connect())"

when connecting from the client sql 2000 to the server and at sometimes it gets connected and it still exists/persists for some time.

though i checked the user rights, client server network utility where tcp/ip is the first protocol.

Give a (me) way to connect to the server, though the user iam trying to connect works in the Query Analyser in the Server

here,
vijayanand.gI know this a post from a previous post. I would try sql profiler and monitor the connections to see if the server is rejecting you or are you not getting there at all. You can use vnc or terminal services to connect to the server (for a good connection) and monitor your connection status.

Let me know.|||Hai,

Though i connect from the profiler the Server gives an error

here,
vijayanand.g|||Is the server behind any firewall?
Originally posted by g_vijayanand
Hai,

Though i connect from the profiler the Server gives an error

here,
vijayanand.g|||You need to execute the profiler either on the sql server or through a remote connection (using vnc or terminal services). Then try to connect on your machine and see what the profiler shows.|||Sorry - I just received your emails - I only have access to my email at home. Basically, you will need to find a machine that has access to the sql server (or login to the actual sql server) and run the profiler and see if at least the server sees that you are attempting to hit it.|||Hai,

The profiler does not connect and trace the required samples.

here,
vijayanand.g|||Hai,

I tried to connect from other machine in sql enterprise manager and query analyser for the specified user, it connects - but through my login in the domain it does not connect.

For the past 1 week iam trying to connect from a XP Machine , it does not connect, i tried to connect from a Windows 98 machine it connects, from a machine that has been logged as an administrator it connects, now i've changed my machines OS to Windows NT Server - now also not connecting .

here,
vijayanand.g|||Hai,

Connected to the Server. It was due to the entry that did not exist for the specified machine in the Hosts file or LmHosts file for the specified machine name.

The connectivity came when the connection was tested with the server by registering the Client by giving the ip address of the machine.

here,
vijayanand.g

connectivity

I trying to connect to a SQL DB SP 3 using cisco client
VPN v.4.01. The VPN is connecting to a cisco PIX515 with
MS IAS as its AAA. On a remote PC running Win XP SP1
logging in with the local builtin administrator account,
I can connect to the SQL after I VPN in. With everything
remaining the same, I logon with a user account I created
belonging to the Administrators group, I get an error
trying to connect to SQL. The only account that is able
to connect to the SQL is the local Administrator
account. All other accounts are getting error of no "not
associated with a trusted SQL Server connection." All
the other account are in the Administrators group. The
security is set to "With Windows NT authenication using
network login ID."If the builtin\administrators group has been removed from SQL Server, then
the other accounts would have to be explicitly added as allowed accounts in
SQL Server. The "with Windows authentication using network..." sounds like
a linked server setting, where are you checking that?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

connectivity

dears,
I've installed one sql server instance .
It is connecting through Named pipes only
Through TCP/IP its not connecting.
Only the default instance in the machine is connecting through all
protocols
Why is it like that ?
Please help me...chaluvadi specialists (sanujss@.gmail.com) writes:
> dears,
> I've installed one sql server instance .
> It is connecting through Named pipes only
> Through TCP/IP its not connecting.
> Only the default instance in the machine is connecting through all
> protocols
> Why is it like that ?
> Please help me...
Which versions of SQL Server are the two instances running?
How do you conclude that you cannot connect to the named instance
through TCP/IP?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||> I've installed one sql server instance .
> It is connecting through Named pipes only
> Through TCP/IP its not connecting.
> Only the default instance in the machine is connecting through all
> protocols
Let's get the obvious out of the way:
What is the possibility that there is a firewall between your client and
your server that is blocking TCP:1433?
--
Peace & happy computing,
Mike Labosh, MCSD MCT
Owner, vbSensei.Com
"Escriba coda ergo sum." -- vbSensei

connectivity

I trying to connect to a SQL DB SP 3 using cisco client
VPN v.4.01. The VPN is connecting to a Cisco PIX515 with
MS IAS as its AAA. On a remote PC running Win XP SP1
logging in with the local builtin administrator account,
I can connect to the SQL after I VPN in. With everything
remaining the same, I logon with a user account I created
belonging to the Administrators group, I get an error
trying to connect to SQL. The only account that is able
to connect to the SQL is the local Administrator
account. All other accounts are getting error of no "not
associated with a trusted SQL Server connection." All
the other account are in the Administrators group. The
security is set to "With Windows NT authenication using
network login ID."
If the builtin\administrators group has been removed from SQL Server, then
the other accounts would have to be explicitly added as allowed accounts in
SQL Server. The "with Windows authentication using network..." sounds like
a linked server setting, where are you checking that?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Tuesday, March 20, 2012

Connections Timing Out

I am running an application on MS SQL2000 SP4. I have 5 clients connecting to
the SQL server. Almost every night between 5

pm and 6:30pm, I lose the
connection to the server from the clients and I get a message about my
database possibly being compromised. Everything locks up and I must reboot
the client.
Has any one experienced this?
Fini2549
Check to see if there are any scheduled jobs running at that time. Sounds
like someone is running a DBCC CHECKDB and placing the db in single user
mode.
Andrew J. Kelly SQL MVP
"Fini2549" <Fini2549@.discussions.microsoft.com> wrote in message
news:9990B03B-CE13-4CEB-9EF8-E4FFB68E0A10@.microsoft.com...
>I am running an application on MS SQL2000 SP4. I have 5 clients connecting
>to
> the SQL server. Almost every night between 5

pm and 6:30pm, I lose the
> connection to the server from the clients and I get a message about my
> database possibly being compromised. Everything locks up and I must reboot
> the client.
> Has any one experienced this?
> Fini2549

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>sql sql

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
....
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
......
...
thanks
You need to run the Surface Area Configuration tool and enable Remote
connections.
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>
|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>

connections remote SQLExpress

how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
does not work.
error:
...
When connecting to SQL server 2005m this failure may be caused by the fact
the under the default settings SQL server does not allow remote
connections (provider SQL Network Interfaces, error 26 error, locating
server/instance specified).
.....
...
thanksYou need to run the Surface Area Configuration tool and enable Remote
connections.
--
Andrew J. Kelly SQL MVP
"EWAT" <eabarca@.medinet-igd.com> wrote in message
news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but it
> does not work.
>
> error:
> ...
> When connecting to SQL server 2005m this failure may be caused by the
> fact the under the default settings SQL server does not allow remote
> connections (provider SQL Network Interfaces, error 26 error, locating
> server/instance specified).
> .....
> ...
> thanks
>|||Since SQL Express installs with a named instance, you also need to enable
and start the SQLBROWSER service.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23j1qbavBGHA.1180@.TK2MSFTNGP09.phx.gbl...
> You need to run the Surface Area Configuration tool and enable Remote
> connections.
> --
> Andrew J. Kelly SQL MVP
>
> "EWAT" <eabarca@.medinet-igd.com> wrote in message
> news:OM3KqItBGHA.2920@.tk2msftngp13.phx.gbl...
>> how I can connect remotely to SQLExpress?.. I have enabled TCP/IP, but
>> it does not work.
>>
>> error:
>> ...
>> When connecting to SQL server 2005m this failure may be caused by the
>> fact the under the default settings SQL server does not allow remote
>> connections (provider SQL Network Interfaces, error 26 error, locating
>> server/instance specified).
>> .....
>> ...
>> thanks
>

connections not closed by app

we inherited this java web app that uses a jdbc-odbc bridge for connecting
to 2 sql server 2000 instances. there are probably hundreds of places in
the application where connections are not being closed (resultsets and
statements not being closed as well).
my question:
1) i assume that as DBAs you would all frown on this? do you have
suggestions about doing something on the db side to address this?
2) what i though was something like: does sql server automatically (or can
i make it) close connections after a peroid of time? would that work?Dont know that I would actually do this, but if all else fails:
1; sp_who2 into a temp table
2; have a cursor loop through the LastBatch column, using dynamic sql, and
KILL everything > 5 minutes. (Or whatever time you decide on.)
I would really try to exhaust all other resources before using this method,
just an idea to keep in mind in case you get this deperate.
--
TIA,
ChrisR
"usenetjb" wrote:
> we inherited this java web app that uses a jdbc-odbc bridge for connecting
> to 2 sql server 2000 instances. there are probably hundreds of places in
> the application where connections are not being closed (resultsets and
> statements not being closed as well).
> my question:
> 1) i assume that as DBAs you would all frown on this? do you have
> suggestions about doing something on the db side to address this?
> 2) what i though was something like: does sql server automatically (or can
> i make it) close connections after a peroid of time? would that work?
>|||Wow. The program must be fixed but for now, I would consider setting up a
schedule to reboot the server at night.
"usenetjb" <usenet.20.jimbo-black@.antichef.net> wrote in message
news:Xns97335385B8126usenetjb@.207.115.17.102...
> we inherited this java web app that uses a jdbc-odbc bridge for connecting
> to 2 sql server 2000 instances. there are probably hundreds of places in
> the application where connections are not being closed (resultsets and
> statements not being closed as well).
> my question:
> 1) i assume that as DBAs you would all frown on this? do you have
> suggestions about doing something on the db side to address this?
> 2) what i though was something like: does sql server automatically (or can
> i make it) close connections after a peroid of time? would that work?|||"Grant" <email@.nowhere.com> wrote in
news:uUcMfmzBGHA.3572@.TK2MSFTNGP14.phx.gbl:
> Wow. The program must be fixed but for now, I would consider setting
> up a schedule to reboot the server at night.
>
>
wow is not what i said, but then again ... believe it or not the app has
to be up 24/7. so we generally reboot the box after a week to make the app
speed up, sigh. it is leaking resources all over the place on the java app
side.
anyway, can sql server reboot itself? do you have any suggestions in terms
of tools to automate this sql server reboot?
thx

Sunday, March 11, 2012

connection with sql server 2000

i am getting error while connecting to sql server in c# 2005. error is :

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I don't why this error occured?? Anybody's help would be highly appreciated

Tushar

Hi Tushar,

try to see this forums and maybe get the answer to your question.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=258082&SiteID=1

Connection Using Gobal ASP

I am having trouble connecting to my SQL Server. I am using InterDev and mod
ifing the gobal.asp.
This is the code I am using
application("DBConn")="Provider=SQLOLEDB;User ID=sa;Initial Catalog=northwin
d;Data Source=192.168.20.17;PASSWORD=;"
Is this correct? If not what should I modify?What errors do you receive? That might help us provide an answer.
First off, I would not use the 'sa' account for a web app.
Create a separate SQL Server login (with limited permissions) and use =
that.
Secondly, you should probably have a password on the account that you =
are using. I am guessing that you may have left that piece out of your =
post because you did not want to tell us your sa password.
Thirdly, do you want the initial database to be northwind?
--=20
Keith
"Jack Temple" <anonymous@.discussions.microsoft.com> wrote in message =
news:9A428A01-1348-4F81-B46B-511CC98ACF0B@.microsoft.com...
> I am having trouble connecting to my SQL Server. I am using InterDev =
and modifing the gobal.asp.
>=20
> This is the code I am using=20
>=20
> application("DBConn")=3D"Provider=3DSQLOLEDB;User ID=3Dsa;Initial =
Catalog=3Dnorthwind;Data Source=3D192.168.20.17;PASSWORD=3D;"
>=20
> Is this correct? If not what should I modify?
>=20
>

Connection to the SSAS Cubes

I have some users connecting to the cubes using excel, is there any way i can track which users aere connected to the cubes without using the Profiler/running a trace.

You can do an XMLA discover command to discover the current sessions/connections

<RequestType>DISCOVER_SESSIONS</RequestType>

</Restrictions>

</Properties>

</Discover>

<RequestType>DISCOVER_CONNECTIONS</RequestType>

</Restrictions>

</Properties>

</Discover>

But I think that the easiest way to run these commands is to use the Analysis Services Stored Procedure Project www.codeplex.com/asstoredprocedures where you can do the equivalent and get the results in an easy to read table form by doing

CALL ASSP.DiscoverSessions();

CALL ASSP.DiscoverConnections();

There was also an AMO Activity sample (or something like that) in the Analysis Services product samples that could show this sort of information.

Wednesday, March 7, 2012

Connection Timeout

In one of my applications I want to set a connection timeout to 1 second when connecting to the SQL Server. .NET's SqlConnection already has connectiontimeout property as readonly and set to 15 seconds. So I cant use it. And if I use adodb.dll and its ADODB.Connection, this time I can set the objects connectiontimeout property. However, it just doesn't work. It still waits along time even though I set the connectiontimeout to 1 second. The same goes when you try the same thing in Delphi.

Anyone has any idea about this problem?

Do you want to change the timeout on the command or the connection ? Normally people want to specify the timeout on the command rather than on the connection.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

How do you check and find "SqlConnection already has connectiontimeout property as readonly and set to 15 seconds"? From what I see in VS 2005, I can edit connectiontimeout property for sqlclient.

Regarding why it still take a long time even if you set the timeout to 1 second, that's because the timeout property is enforced in different layer, specifically higer layer. If a connection is blocked or waiting in a API in lower level, it won't stop the connection until it returns from lower level. If there is still time left, higher level may try to connect again. So, the timeout is not always enforced, you should not use it for precise timing.

Saturday, February 25, 2012

Connection Timed Out Error

hello all,
can any one explain sql State HYT00
im getting this as a part of the connection timed out message, while connecting from my node to sql server 2000 instance running on windows 2000 server.
thanks in advancepresume the connection is there and you can ping the other server?

How are you attempting to connect?

Has it just stopped? Have you ever had connection? have you checked that the correct protocols are enabled on the target server?

Jim|||YES JIM

I CAN PING THE MACHINE

IVE CONFIGURED THE CLIENT NETWORK UTILITY TO USE TCP

PROTOCOL TO LISTEN TO THE DEFAULT PORT 1433. THE SERVER

NETWORK UTILITY IS ALSO CONFIGURED

I COULD CONNECT TO THE SERVER BEFORE, BUT IT DROPS ALL OF A
SUDDEN,AND DISPLAYS THE 'CONNECTION TIMED OUT' MESSAGE

IM GETTING THIS MESSAGE WHILE ATTEMTPTING AN ODBC CREATION.|||http://vyaskn.tripod.com/sql_odbc_timeout_expired.htm to resolve the issue.

HTH

Connection Strings

I have created a SSIS package, and got it to perform as I want.

I am having a problem though with connecting to my data source (OLE DB Source) using SQL Server Authentication.

If I use Integrated security, I have no problems. If I use SQL Server Authentication, I get errors.

Here is the connection string that works:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Integrated Security=SSPI;Initial Catalog=MyDataBase

Here is the connection string that fails:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Persist Security Info=True;Password=**********;User ID=myUserid;Initial Catalog=MyDataBase

The strange thing is that when I use the Connection Manager dialog screen and click on "Test Connection", I get the response that the connection succeeded. It is only when I try to run the task that I get an error.

Here is the error I am getting:

[OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "MyDataBase" failed with error code 0xC0202009.

[DTS.Pipeline] Error: component "MyDataBase" (1) failed validation and returned error code 0xC020801C.

I have eliminated the obvious errors (incorrect Userid or password). Also, I am unable to use Integrated Security as this package needs to be distributed to various systems that may or may not be on our company's primary domain.

It seems I am missing something really basic here, but am not seeing it.

Any thoughts?

Has this ever worked for you? Are you able to create a brand new package and it still fails? Are you using package configurations?|||

Has this ever worked for you? Yes, using integrated security

Are you able to create a brand new package and it still fails? No, actually I tried a new simple package, and it works.

Are you using package configurations? No

I think the key here is your second point. I created a new package, and the connection now works. So, the question is how do I fix my original package? I'm not really thrilled about creating a brand new package being that this one is quite complicated.

Suggestions?

|||Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.|||

WRBehning,

Welcome to the new world of SSIS! I have had similar problems, especially when you copy and paste items. Basically I think the internal Ids in SSIS get messed up somehow. Alot of times if you delete and re-add an item it fixes the problem. Doesn't give me great confidence when an "enterprise solution" has so many strange problems. Good Luck! (to us all)

|||

WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.

If you have a RFE (Request for Enhancement) then file it at http://connect.microsoft.com with a detailed write-up.

Only thru doing this will SSIS get closer to being the product that people want it to be.

-Jamie

|||

WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.

Can you explain exactly what the problem was in the original. Its not clear from this?

If its something that people need to know then I'd like to add it here: http://blogs.conchango.com/jamiethomson/archive/2006/10/18/SSIS_3A00_-Random-information-for-beginners.aspx

Thanks

-Jamie

|||The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.|||

WRBehning wrote:
The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.

That's worrying if it didn't work. However I have previously had no problems with changing connection strings (for that is what we're talking about here).

One thing that can cause problems is if (for example) the ServerName property doesn't marry up with the server name that you are setting in the ConenctioNString property although in your case the only difference is in authentication mode so I shouldn't expect it to be a problem.

I've also tried your repro steps as above and didn't experience any problems.

What version/service pack are you on?

-Jmie

|||

Here you go...

A couple of things I should mention.

I tried deleting and re-creating the connections and this did not solve the problem.

The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.

SQLExpress (SQL Server 9.0.2047)

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

|||

WRBehning wrote:

Here you go...
A couple of things I should mention.
I tried deleting and re-creating the connections and this did not solve the problem.
The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.
SQLExpress (SQL Server 9.0.2047)
Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727
Installed Edition: Professional
Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005
Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005
Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00
SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Seems we're on the same. Strange.

Oh well. Let's chalk it up to experience. If it happens again, let us know.

Thanks

Jamie

|||

I am experiencing the same behaviour.

The package was first created using EncryptWithUserKey setting, and the connection credentials was for a trusted connection to a SQL Server.

We changed the package security to use EncryptWithPassword, and the connection credentials stayed the same and continued to work properly.

When we changed the connection credentials to use a Standard SQL login, I would set the login and password and check the "Remember password" option. The Test Connection button was successful. Then after closing the connection manager properties, I would immediately reopen the properties and the password was gone, but the checkbox was still there, and the Test Connection would fail.

Mike

Connection Strings

I have created a SSIS package, and got it to perform as I want.

I am having a problem though with connecting to my data source (OLE DB Source) using SQL Server Authentication.

If I use Integrated security, I have no problems. If I use SQL Server Authentication, I get errors.

Here is the connection string that works:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Integrated Security=SSPI;Initial Catalog=MyDataBase

Here is the connection string that fails:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Persist Security Info=True;Password=**********;User ID=myUserid;Initial Catalog=MyDataBase

Here is the error I am getting:

[OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "MyDataBase" failed with error code 0xC0202009.

[DTS.Pipeline] Error: component "MyDataBase" (1) failed validation and returned error code 0xC020801C.

It seems I am missing something really basic here, but am not seeing it.

Any thoughts?

Has this ever worked for you? Are you able to create a brand new package and it still fails? Are you using package configurations?|||

Has this ever worked for you? Yes, using integrated security

Are you able to create a brand new package and it still fails? No, actually I tried a new simple package, and it works.

Are you using package configurations? No

Suggestions?

WRBehning,

|||

WRBehning wrote:
Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.